reddit.com via Reddit

Claude Code UltraCode Burns 1.7M Tokens, No Refunds

anthropic coding tools agents ai-tools claude-code dynamic-workflows

Key insights

  • UltraCode subagents consumed 1.7 million tokens in a degenerate loop two days after launch, producing zero usable output for the developer.
  • Subagents inherit the parent session's full model tier with no spending cap or automatic failure detection built into UltraCode at launch.
  • Anthropic's no-refund policy applies to runaway agent token consumption, leaving users with no contractual remedy for credit losses from feature failures.

Why this matters

Multi-agent orchestration introduces compounding cost exposure that flat token pricing was never designed to handle, and UltraCode's incident is the first documented case where Anthropic's agentic infrastructure created an unrecoverable financial loss with no contractual remedy. The absence of spending caps or circuit breakers in a feature that defaults to the most expensive model tier is a product safety gap that technical leaders must factor into any Claude Code production deployment decision. For enterprise buyers currently evaluating Claude Code, the no-refund policy combined with dynamic workflow failures creates a liability exposure that standard software vendor agreements do not typically impose on customers.

Summary

Claude Code's UltraCode setting, released May 28, triggered a runaway subagent loop that consumed 1.7 million tokens within minutes and produced zero output. Anthropic's no-refund policy left the developer with a complete credit loss. The mechanism: UltraCode spins up multiple subagents using the same expensive model tier as the parent session, with no spending cap or automatic circuit breaker. The main Claude agent identified the failure as a 'degenerate loop' only after the token budget was gone. Essentially: (Anthropic, Claude Code Pro/Max subscribers) are running dynamic multi-agent workflows with real financial exposure and no contractual safety net. - No built-in spending limit or failure guard shipped with UltraCode at launch. - Subagents inherit full model-tier pricing, making loop failures on Max plans especially costly. - Anthropic's terms explicitly exclude refunds for token consumption regardless of feature behavior. Flat-rate token pricing was designed for single-session use, and UltraCode's incident is the first documented case of that model breaking down at the agentic layer.

Potential risks and opportunities

Risks

  • Claude Code Pro and Max subscribers running complex UltraCode tasks in the next 30 days face unquantified token burn with no refund recourse if loops recur before safeguards ship.
  • Anthropic's enterprise sales pipeline faces friction if procurement teams flag the no-refund policy against documented agentic failure modes before a patch or policy update is issued.
  • Broader community confidence in Claude Code Dynamic Workflows degrades rapidly if additional loop failures surface publicly before Anthropic commits to a fix timeline.

Opportunities

  • Third-party Claude Code usage monitoring tools and token budget managers gain immediate demand from Pro and Max subscribers seeking financial guardrails that UltraCode does not yet provide.
  • Competing agentic coding platforms including Cursor, Devin, and GitHub Copilot Workspace can differentiate on built-in spending limits and loop detection in active sales cycles against Anthropic.
  • Anthropic can convert the incident into a trust signal by shipping a spending cap or automatic circuit breaker within 30 days and publicly documenting the fix, directly addressing enterprise procurement objections before they harden.

What we don't know yet

  • Total dollar cost of the 1.7M-token incident is undisclosed; Pro vs. Max plan pricing creates a wide range of possible losses from hundreds to thousands of dollars.
  • Whether Anthropic plans to ship spending caps or circuit breakers for UltraCode before additional incidents accumulate is unaddressed in any official communication as of May 30.
  • Frequency of degenerate loop failures across the broader UltraCode user base is unknown; the Reddit thread captures one case with no systematic incident data from Anthropic.