> ## Documentation Index
> Fetch the complete documentation index at: https://docs.macroscope.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Spend controls

> Defaults, scope, and overrides for workspace, review, agent, and CLI spend caps.

Workspace admins manage limits in **Settings → Billing**. Repository review filters and run-count limits live in **Settings → Repos**.

## Limits at a glance

| Limit | Default | What it counts | Bypass |
| - | - | - | - |
| Monthly workspace limit | Configured by the workspace | All usage in the billing period | None. |
| Correctness per-review cap | \$10 | One GitHub correctness review | Manual review request. |
| Correctness per-PR cap | \$50 | Correctness spend on one PR | Manual review request. |
| Check Run Agents per-PR limit | \$100 | Combined agent spend on one PR | Explicit agent invocation. |
| CLI workspace / per-user limits | Unset | CLI review spend in the billing period | None. |

Correctness caps and the Check Run Agents per-PR limit always have a value; blank fields retain the saved limit. Per-PR limits have a \$0.50 minimum. Monthly and CLI limits can be cleared.

## Workspace balance and monthly limit

An exhausted balance or reached monthly limit pauses processing. Auto-refill replenishes the balance but does not override the monthly limit. No manual review request bypasses either condition.

Processing resumes after a refill, a limit increase, or the next billing period as applicable. Commits and PR events skipped during the pause are not automatically processed afterward.

<a id="per-pr-cap" />

## Correctness caps

Correctness estimates cost before running and skips when the proposed review plus recorded spend would exceed the cap. A per-PR skip reports "Per-PR cost limit exceeded (workspace setting)". The per-PR total includes only GitHub correctness reviews: not Check Run Agents, Approvability, CLI, or other agent usage.

The correctness per-PR cap also stops **Approvability** on that PR, even though Approvability's own spend does not count toward it. Check Run Agents have their own limit and keep running if their budget permits.

Comment `@macroscope-app review this PR` to bypass correctness per-review and per-PR caps. The workspace monthly limit still applies. See [Approvability when reviews are missing](/approvability#limit-stops-correctness).

<a id="cra-per-pr-limit" />

<a id="the-check-run-agents-per-pr-limit" />

## Check Run Agents per-PR limit

The **\$100 default** is shared by every Check Run Agent on the PR. Once recorded spend reaches it, later automatic runs are created as skipped checks. An explicit mention can bypass it; a GitHub rerun does not.

This limit is **best effort**: no budget is reserved before dispatch. Concurrent agents can all start below the limit and collectively exceed it. Work already running is billed.

Per-agent front matter provides narrower controls:

| Field | Scope | Enforcement |
| - | - | - |
| `maxBudgetPerRun` | One run | Checked after each turn; stops with a neutral “Budget reached” result. |
| `maxBudgetPerPR` | One agent across a PR | Checked before dispatch against recorded spend. |
| `maxRuns` | One agent across a PR | Skips later automatic runs after the count. |

These are separate from the workspace limit. Raising one does not clear another. See [configuration and overrides](/check-run-agents/configuration#run-and-spend-limits).

## CLI review limits

Under **CLI Spend Controls**, set:

| Control | Effect when unset |
| - | - |
| Monthly CLI review spend limit | No additional workspace-wide CLI cap. |
| Default per-user monthly limit | No additional per-user CLI cap. |
| Per-user override | The user follows the default. |

The two workspace fields accept positive amounts. A per-user override of **\$0 blocks that user**; remove it to restore the default.

CLI limits count only CLI reviews, reset each billing period, and apply alongside the workspace balance and monthly limit. The workspace CLI cap blocks everyone once reached, regardless of their personal allowance.

Limits are checked before a review starts. Already-running reviews are not stopped, so concurrent usage can exceed a cap. A declined review costs nothing. Raise the named limit in the CLI error and rerun the review.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.