Detailed Analysis
A Reddit user in the r/Anthropic community has surfaced a technical complaint that could have real financial implications for heavy users of Claude's agentic coding tools: agents appear to be losing cached context between tasks and re-reading files from scratch rather than resuming from where they left off. The poster describes running Opus workflows through Fable (an orchestration tool) and using Opus to drive Sonnet sub-agents, two setups they characterize as among the most token-efficient ways to work with Claude. Previously, these agents would sit "ready and waiting" between tasks, preserving context at a reduced re-read usage rate. Now, the report claims, usage is being cleared and agents are forced to reprocess context from the beginning, sometimes repeatedly, driving up token consumption and cost without any corresponding change in the user's own workflow.
The mechanism at issue is context caching, a feature that underpins much of the cost efficiency in long-running or multi-agent Claude workflows. When an agent retains a cached context window, subsequent calls can reference that cached state at a fraction of the cost of processing the same tokens fresh. If that caching layer is silently failing or being invalidated more aggressively, users would see exactly the symptom described: usage spikes that seem disproportionate to the actual work being done, even for people running only one or two agents rather than large fleets. The user notes an especially concerning edge case, an apparent loop where the agent repeatedly lost and re-read context between each queued task, which suggests the issue may not be a simple one-time reset but potentially a bug in how session state or queue handling interacts with caching.
This kind of issue matters beyond a single user's frustration because it touches on the core value proposition of agentic AI systems. As developers increasingly rely on Claude to autonomously execute multi-step, long-horizon tasks, cost predictability and context persistence become essential infrastructure requirements. Anthropic has invested heavily in prompt caching and extended context handling precisely to make these workloads economically viable, and regressions in that system, whether from backend changes, model updates, or orchestration-layer interactions with tools like Fable, can quickly erode trust among power users who have built workflows around specific cost assumptions. The user's note that their driving model's context never exceeded 200k tokens is a useful diagnostic detail, ruling out simple context-window overflow as the cause and pointing instead toward something in the caching or session-management logic itself.
This report also reflects a broader pattern in the AI agent ecosystem: as third-party orchestration tools proliferate around foundation models, subtle interactions between platform-side changes and community-built tooling can produce hard-to-diagnose regressions that affect only certain workflows. The user's decision to file feedback directly with Anthropic, and to publicize the issue for others who might be experiencing unexplained usage spikes, is representative of how bug discovery increasingly happens collaboratively between vendors and their most sophisticated users. For Anthropic, unexplained cost inflation tied to agentic workflows is a particularly sensitive issue, since usage-based pricing means that any caching regression translates directly into higher bills, making rapid diagnosis and transparent communication about root causes important for maintaining confidence among developers building production agent systems on Claude.
Read original article →