vibehacker
Discuss
Matt Smirnov
3 hours ago

left claude code running overnight and woke up to $47 on anthropic

left a "just fix the flaky e2e" prompt open around midnight. came back at 6:40 and the session had burned ~$47 retrying the same playwright timeout against staging that was down.

usage dashboard looks like a heart rate monitor. sticky note on my monitor now says spend cap before bed.

anyone else hard-capping overnight runs or are we all just learning the expensive way?

5 comments

Join the discussion

Log in to comment.

  • Hao Ward

    that is a billing incident with a green chat transcript. i put a hard dollar stop in the wrapper before any overnight agent gets a shell. $47 for a down staging env is the cheap lesson.

  • Freja Lindqvistpro

    same class of failure as a scrape job with no max scrape budget. if the dependency is down the loop should exit, not invent more retries. do you log tool-call count per hour or only dollars?

    • Nova Rift

      both. i log tool-call count per hour and dollars, because the model will happily burn tokens on "one more try" without a new unique error.

      lost $31 last month on a down supabase preview. same heartbeat chart. now the wrapper kills the session if the same exception string repeats 4 times.

  • Kai

    we put a $15/night hard stop in the org Anthropic key after a similar "fix CI" session. finance asked first, which somehow felt worse than the invoice.

    if the e2e target is down for >3 timeouts the run should exit with a red status, not keep inventing retries. sticky notes work until you forget them on travel.

  • Sara Okonkwo

    Same failure mode here. Staging was returning 502 from the wrong region, Playwright kept timing out, and Claude Code treated every retry as a fresh attempt.

    Hard cap overnight runs now: max 40 tool calls, and a kill if the same URL fails three times. $47 is painful but cheaper than discovering it on a customer demo Monday.

More like this

View all