# Spend limits and stops for coding agents | Oxagen

Source: https://oxagen.sh/product/mandates/budgets

# Budgets and stops

A release breaks at 2 a.m. and three agents are still working, each spending on the team's model key. Oxagen refuses metered calls past a spend ceiling you set, holds a run to the limits in its mandate, pauses live runs when a person asks, and ends an agent's authority at the scope that fits.

[Follow work from its source to its outcome](https://oxagen.sh/#demo)[Read the product overview](https://oxagen.sh/product)

The Spend report with illustrative data for Oct 10 to Nov 8: $31,240.55 over 412 runs and 96 merged changes, with $3,436.46 of it wasted.

Recorded spend on the Spend report

01

## How spend ceilings work

Set spending boundaries on supported calls through Oxagen. A spend ceiling covers one organization or one workspace. It counts spend over the calendar month to date, or over a trailing window of days you choose. You decide whether it is enforced or only watched.

When an enforced ceiling is reached, Oxagen refuses the next metered Oxagen call before any model provider is paid, and the run's people are told why it is waiting. Raising the ceiling clears the refusal. An organization Owner or a Compliance and Billing member sets either ceiling, a workspace Admin sets that workspace's own, and each change is audited.

An enrolled machine stops too. Within a minute of an enforced ceiling running out, the recorder's local proxy refuses the agents' model calls, and the hook refuses their prompts and tool calls. The per-run and daily limits in the agent's mandate hold there as well, for Claude Code, Codex, and Stella.

If Oxagen cannot read the spend store, the ceiling decides with the spend and the limits it read in the last 5 minutes, and the audit log records that it did. With nothing read that recently, it refuses the call until the store answers.

The Budgets card on the Guardrails page, with illustrative data. The organization has spent $9,000.00 of its $10,000.00 limit, past 80 percent. This workspace has spent $1,357.59 of $5,000.00, under its ceiling.

Spend ceilings on the Guardrails page

02

## Agent budgets

Each agent can also carry a budget in cents. The agent budget is not a ceiling by itself. Your policy rules read what is left of it, so a rule can stop a call once a run has spent most of the budget. An agent with no budget has no limit of its own.

03

## Spend controls

Each spend control with its scope and how it stops work
| Control | Scope | Stops work by itself |
| --- | --- | --- |
| Spend ceiling | Organization or workspace | YesWhen enforced. The next metered call is refused. |
| Agent budget | One agent | PartialA policy rule must read it. |
| No-progress limit | Workspace | PartialPauses a run after a set number of identical calls in a row when enforced. The default only records it. |

04

## Pause and revoke controls

Pause a live wrapped run, or end authority for an agent, a tool, a connection, or a workspace. Oxagen records each stop with its reason.

A pause holds work and keeps authority. `oxagen run pause-all --reason` pauses every live wrapped run in a workspace as one recorded decision. Each run stops at its next stopping point after its host collects the command, and the answer lists each run it skipped, such as one whose host is offline.

A kill switch denies the next governed call at its scope: a tool, a tool server, a connection, an agent, an operator, a workspace, the organization, or a class of consequence. A connection switch also revokes the connection's live credentials. Suspending an agent empties its tools until someone resumes it, and revoking a machine's enrollment refuses every run on that machine at its next step.

The kill switches on the Guardrails page, with illustrative data. One switch is denying: Dana Okafor turned off Stripe after a suspected compromise of its restricted key. A class switch can stop every tool that moves money.

Kill switches on the Guardrails page

05

## How a stopped run behaves

The Runs page with illustrative data. The Live now card counts the runs that are working, parked for approval, paused by the no-progress limit, or on a host that is offline, and the table gives each run's state.

Each run's state on the Runs page

06

## Coverage by control

What each control covers
| Control | Covers | Leaves out |
| --- | --- | --- |
| Spend ceiling | Metered Oxagen calls in its organization or workspace, including calls made with an API key. On an enrolled machine, model calls through the local proxy and every harness's prompts and tool calls. | Spend in the minute before an enrolled machine reads that the ceiling ran out. Cursor's model calls, which skip the proxy. Oxagen's in-app agent. |
| Mandate run and daily limits | Model calls through the recorder's local proxy for Claude Code, Codex, and Stella | Cursor's model calls, which skip the proxy. |
| Kill switch | The next governed call at the switch's scope | Calls made with an API key, which roles and key revocation govern. Oxagen's in-app agent, which has its own switch. |
| Run pause | Live wrapped runs in the workspace | A run whose host is offline, until the host collects the pause. |

07

## Billing terms

A ceiling counts the spend Oxagen recorded. It is separate from your model provider's bill, from Oxagen's own plan, and from your credit wallet. [Read the pricing terms](https://oxagen.sh/pricing) for seats, allowances, and credits.

## Related pages

*   [
    
    ### Mandates
    
    The terms an agent works under
    
    ](https://oxagen.sh/product/mandates)

## Product walkthrough

Set a ceiling on a sample workspace and watch the point where it takes effect.

[Follow work from its source to its outcome](https://oxagen.sh/#demo)[Read the product overview](https://oxagen.sh/product)
