Budgets and cost control
Cap what a ticket, a day, or a month can spend, and know roughly what to expect.
AI usage is real money on your own key, so every project has spending caps, set in Settings → Budgets & guardrails, and shown right next to the Claude key field in the setup wizard.
The caps
- Per ticket: stops a single run from running away with cost. A cap breach mid-stage stops that stage immediately; it doesn't wait for the stage to finish first.
- Per day and per month: a rolling ceiling across the whole project.
Hit any of them and:
- Autopilot pauses: it stops enqueueing new tickets until you raise the cap or the period resets.
- Run now is blocked on that project, with a clear message telling you which cap was hit.
Nothing already Running is interrupted destructively. A mid-stream cap stops the current stage cleanly rather than leaving a half-applied change.
Trial defaults
While you're on the 14-day trial, new projects start with a $5 per-ticket and $25 per-day cap. You can raise these yourself as the project owner: they're a safety default, not a hard plan limit.
What to actually expect
There's no fixed price per ticket. It depends on the size of the change and the model you've chosen for each stage. As a rough range, expect €5–€40 per ticket. The trial is the best way to get a real number for your own codebase: the dashboard shows cost per ticket as tickets ship, so by the end of it you'll know your actual figure instead of a rule of thumb.
You can also set a spend limit on the Anthropic Console side, independent of anything here, as a second line of defense.