Budgets

Each review has a run budget, shared through stage allocations. Pipeline limits separately control trailing spend.

Set a run budget

ellipsis:
  kind: code_review
  name: bounded-review

budget:
  run: 10
  day: 50
  week: 200

Values are US dollars. run applies to one review iteration. A later push starts a new iteration with a new allocation.

day and week measure this pipeline's trailing spend over one and seven days. They are checked before another review starts.

Reserve a stage allocation

ellipsis:
  kind: code_review
  name: allocated-review

description: []

review:
  - name: correctness
    harness:
      type: claude_code
      model: claude-opus-5
    instructions: |
      Find concrete bugs in the changed code and verify them.
    budget: 6

filter:
  name: verification
  harness:
    type: claude_code
    model: claude-opus-5
  instructions: |
    Keep only findings supported by a reproducible failure.
  budget: 4

budget:
  run: 10

The reviewer receives $6 and the gatekeeper $4. Without an explicit stage budget, agents divide the remaining allocation.

Keep explicit stage allocations within the run budget and leave room for any stages that inherit an allocation.

When limits are reached

A stage can stop before finishing. Ellipsis may post findings already produced with an incomplete-review warning. A posted review can advance coverage, so inspect that warning and rerun the full range when needed.

A trailing pipeline limit prevents another run until spend falls below the limit. Account and developer spend limits also apply.

Budget values constrain new paid requests. In-flight requests and compute charges can exceed the configured amount.

Inspect cost

Open the review in the dashboard for total cost and per-stage usage. Review usage draws from the same credit balance as other sessions.