Spending limits

Organization Settings > Spend > Limits is the page where the invoice stops being a surprise: org caps, per-user limits, and budgets with teeth.

Caps that actually cap

Limits sits beside Usage, Costs, and Productivity in the Spend section. The org cap is the hard ceiling; under it, per-user and per-trigger budgets keep any one person or automation from eating the month. Budgets roll on a schedule, and triggered work (GitHub events, flow schedules) carries its own budget so background automation cannot silently outspend the humans.

The full Limits tab: GitHub trigger budgets, the org cap with grace and critical thresholds, cumulative spend against the cap, then per-project, per-model, and per-flow caps — ↳The whole enforcement surface: the ceiling, the thresholds that warn before it, and a cap line for every project, model family, and flow.

The strip at the top of every Spend page keeps score: 30-day spend, share of work not written off, and agent awake hours. Caps on is a status, not a promise.