Agent minutes and code session compute

Every plan includes two monthly allowances. Agent minutes are the time your agents and automations spend working on a run. Code session compute hours are the time a code session's sandbox runs. The pricing page lists both for every plan, and the per-hour rates past them. This page explains how they behave.

What counts

• Agent minutes count while a run is working. A run that stops to wait for you to approve an action or answer a question stops the clock, and the time you take never counts. A run that is refused before it starts costs nothing.
• Your own AI provider key does not exempt a run. The key pays for the tokens. The minutes are our compute, so they count on every plan, and on Free they are the only limit on those runs.
• Code session compute counts from the moment the sandbox starts until the session finishes, whoever pays for the model tokens.
• Each run or session rounds up to a whole second.

At the limit

Plan	What happens past the included time
Free	New runs are refused until the next month, with a message that names the allowance. One run can work for a limited time, and the pricing page states it. Work done before a run stops is kept.
Paid	Runs continue and each second is debited from your credits at the rate on the pricing page. Work stops when your credits run out, the same as every other credit-funded feature.
Enterprise	The allowance is set by your contract.

A code session that is already running is never cut off. New sessions are refused when the included hours are spent and no credits remain.

Where to see your usage

• Billing, Usage shows the minutes and hours used against the allowance, the credits spent past it, and the date it resets. The breakdown groups time by agent and by code session.
• Billing, Rates lists the current per-hour rates and each plan's allowances.
• A stopped run shows the reason on the run itself, in the Inbox and in run evidence.

Related

• Pricing
• Hosted Agents
• Warehouse