Tuning reviews

Cost and budgets

inline has two ceilings you can set: one for the reviews it runs on pull requests, and one for the reviews your developers request from their coding agents. Both are monthly, and both are optional.

Setting a budget is an admin task, and so is seeing the figures behind it. Developers can see their own usage on the coding agents page.

#The ceiling for pull request reviews

/settings/reviewOpen in app

Review configuration

Defaults every repository inherits. Repos can override most settings on their own page or in .inline.yml unless a setting is locked under Enforced policy.

Defaults

Severity threshold

LowMediumHigh

Reviews post as

inline botYour account

Merge gate

Default mode

OffReportBlock highBlock med+Block all

Check fails while high-severity findings are open — resolve the thread or push a fix to clear.

Sandbox tests

AutoOffReportBlock

Monthly AI budget

Cap (USD)

No cap

Monthly AI budget, on Review config below the merge gate.

Monthly AI budget on Review config sets a ceiling for the whole workspace over a calendar month. The field shows No cap until you set one, which is where every workspace starts.

inline emails an alert as the workspace approaches the ceiling, so you hear about it while there is still room to act.

#What happens at the ceiling

You choose what reaching the ceiling means, with Degrade to triage-only past the cap.

Setting	What happens at the ceiling
Off	Reviews pause for the rest of the calendar month, and resume on their own when it turns over.
On	Reviews keep running, but stop after triage. Every pull request still gets looked at and gets a verdict; none gets the full pass until the month turns over.

Turning it on is the safer choice for a team that would rather have a light review than none. A pull request handled this way comes back Incomplete, and the next push after the month turns over reviews it in full. See How a review works.

#The ceiling for coding agent reviews

Reviews your developers request from their own coding agents are counted separately, and capped separately, on the Settings tab of Coding agents.

Setting	What it does
Enable ad-hoc review	Whether developers can request reviews from a coding agent at all. See Coding agents.
Monthly budget cap (USD)	A ceiling for the whole workspace's coding agent reviews in a calendar month.
Per-developer monthly cap (USD)	A ceiling for one person, inside that workspace total, so one developer cannot use the month's allowance alone.

#Seeing where it went

The dashboard carries the workspace totals for whichever window you pick, alongside the review counts, so you can see the two move together. The Spend tile shows the cost per pull request review and how much of this month's budget is used. The Spend card splits the total by module, coding agent reviews among them, and adds Per kept finding.

For a single review, the detail page breaks the figure down by the job each part did, so a review, its walkthrough and its test run are separable. Cached reads counts input inline read from cache rather than fresh, which is why a second pass over the same pull request re-reads less than the first.

The Usage tab on Coding agents does the same for coding-agent reviews, broken down by developer and by repository.

#Choosing a number

Most teams leave both ceilings at No cap for a month, watch the dashboard, then set a ceiling comfortably above what that month actually used. A ceiling set that way catches something going wrong and stays out of the way the rest of the time.