Skip to main content

Limits actually enforced

A limit that is documented but not enforced is a hope. Every cap below is enforced by a component that does not trust the harness, and every attempt that hit one is reported under that reason in the failure taxonomy.

limitenforced bywhen it binds
run spend capthe run's own provider key, minted with the cap as its hard limit (ADR-0044); the gateway key carries no budgetevery call from the run is refused; the run pauses and reports gateway blocked
per-instance costthe local proxy shim, from the gateway's metered usagethe session is ended; the attempt lands as budget_exceeded with whatever patch exists
per-instance tokensthe shimas above
per-instance turnsthe adapter, counting tool-call roundsmax_turns_exceeded
wall-clock per attemptthe task's timeouttimeout
context windowdeclared to the harness so it compacts before the model rejectsnot a terminal reason; visible as compaction events in the trajectory
provider rate limitsthe pacer holds calls at the pool's discovered rates; the planner sizes the fleetcalls wait (recorded as paced wait per call); nothing fails

The limits recorded with the MiniMax series​

limitopencodecustom_minimalclaude_codecodexmini_swe_agent
max_tokensnot setnot setnot setnot setnot set
max_cost_usd_per_instance22222
attempts_per_instance11111
temperature11not set11

max_tokens was not set for this series — the per-instance cost cap and the turn cap were the binding limits by design. not set is shown as such rather than as 0.