AI Agent Cost Control: How to Stop an Unattended Agent Burning Your Budget

Why do unattended AI agent runs cost so much?

Interactive work is self-limiting. You are sitting there, you see the cost, you stop. Unattended work has none of that, and the failure is silent until the bill arrives.

The most-discussed example in r/ClaudeAI is a post titled "I accidentally burned ~$6,000 of Claude usage overnight with one command", which drew 1,200+ upvotes and 340+ comments. The amount is self-reported rather than verified, but the mechanism is mundane and repeatable: a loop running unattended with a context that kept growing.

How many spending ceilings do I need?

The community's first instruction, from the auto-generated consensus summary of that thread, was to set a hard spending limit in your Anthropic account settings, noting that it exists for exactly this reason.

That is necessary but blunt. An account limit stops you at the wall, usually mid-task, leaving half-finished work and no clean record. A second ceiling inside whatever schedules the agent can be smarter: before starting a cycle, check the day's spend and decline if it cannot be afforded. You end the day with completed work and a logged reason rather than a run severed in the middle.

• Account-level limit: the hard backstop, set it first
• Harness-level daily ceiling: refuses to start work it cannot finish
• Count every attempt, including retries and repairs, not just the first
• Exclude cached input from the count, or you will stop well short of your real budget
• Bound each cycle in wall-clock time too, so one wedged task cannot consume the night

Why does polling cost more than scheduling?

A loop that wakes up and asks the model whether there is anything to do pays for that question every single time. Over a night, the questions can cost more than the work.

The r/ClaudeAI consensus called this a terrible design pattern and recommended proper infrastructure instead: a cron script, webhooks or GitHub Actions that call the model only when an event has actually happened. A top comment in that thread, with 194 upvotes, described using an old school cron script that invokes Claude hourly to check pull requests, which is the correct shape.

Does a long context make an agent more expensive?

Every turn of a conversation is re-sent on the next turn. A single session held open across an unattended run therefore costs progressively more for progressively less focused work.

The community's advice was to start a fresh context each time rather than letting one conversation grow indefinitely. The refinement worth making is a session per role: each role resumes its own thread so it retains what it decided, without one role's history inflating another's context. Anything that must survive longer belongs in a bounded memory file, not the conversation.

Which model is cheapest for unattended work?

Also from the same consensus: use a cheaper model such as Sonnet for unattended tasks. Repetitive, well-specified work is where a cheaper model gets close to a frontier one for a fraction of the price.

Set this per role, not globally. Deciding what to build next deserves a strong model. Writing a changelog entry from a diff does not.

Which failures should never be retried?

A subtler waste is retrying failures that cannot succeed. A rate limit is worth retrying with backoff. An authentication failure is not, and neither is a run that exhausted its turn limit, because the same limit will stop the next attempt at exactly the same point.

Classifying failures before retrying is a small change with a real saving. In our own testing, a turn-limit failure that was retried twice before being classified correctly wasted roughly 90 seconds and three full attempts to arrive at the identical outcome.

Method and limitations

Engagement counts come from a reddit-mcp query against r/ClaudeAI over the past year and are rounded; they are a snapshot.

Quotes are attributed to the subreddit only. The $6,000 figure is a self-report, not verified spend.

The 90-second retry figure is from our own instrumented run against the Claude Code CLI, not a benchmark.

FAQ