Editorial illustration for Update: Usage Limits Draining Faster Linked to Two Unrelated Experiments
Claude Usage Limits Drain Faster: Community Mystery
Update: Usage Limits Draining Faster Linked to Two Unrelated Experiments
The recent flurry of complaints about Claude’s usage caps disappearing quicker than users expect has been puzzling many in the open‑source community. When the issue first surfaced, engineers struggled to reproduce the behavior in a controlled environment, leading to a cascade of speculation on forums and GitHub. Behind the scenes, two distinct tests were running simultaneously, each touching different parts of the stack.
One was an internal‑only, server‑side tweak aimed at improving message queuing performance; the other altered the way the interface renders a particular “think” element, a change that seemed unrelated to resource accounting. The overlap of these experiments created a perfect storm for the observed limit‑drain anomalies, but the connection wasn’t obvious at first. As the team dug deeper, they began to see a pattern linking the faster‑than‑expected consumption to the concurrent modifications.
The following statement explains how the two unrelated experiments converged to produce the puzzling results.
We believe this is what drove the separate reports of usage limits draining faster than expected. Two unrelated experiments made it challenging for us to reproduce the issue at first: an internal-only server-side experiment related to message queuing; and an orthogonal change in how we display thinking suppressed this bug in most CLI sessions, so we didn't catch it even when testing external builds. This bug was at the intersection of Claude Code's context management, the Anthropic API, and extended thinking. The changes it introduced made it past multiple human and automated code reviews, as well as unit tests, end-to-end tests, automated verification, and dogfooding.
Will the fixes hold up? The team says the three problems were resolved on April 20 with version v2.1.116, and the API was not touched. Yet some users reported slower response quality before the patch.
Those reports traced back to changes in Claude Code, the Claude Agent SDK, and Claude Cowork. Two unrelated experiments – an internal server‑side test of message queuing and an orthogonal display tweak – appeared to drain usage limits faster than expected. Because the experiments were independent, reproducing the issue proved difficult at first.
The update notes that the combined effect likely caused the anomalous limit consumption. While the fixes are now live, it remains uncertain whether all affected accounts will see immediate normalization. Observers are encouraged to watch for any lingering irregularities.
The company’s communication emphasizes that the API remains unaffected, limiting broader impact. In short, the known problems have been addressed, but ongoing verification will determine if the resolution is comprehensive. Further feedback from the developer community will help gauge the durability of the changes.
Further Reading
- Claude Usage Limits: Why You're Running Out Faster (And the $338...) - Nicholas Rhodes Substack
- Widespread abnormal usage limit drain across all paid tiers - GitHub - Anthropic Claude Code Issues
- Claude Code users hitting usage limits 'way faster than expected' - Hacker News
- Anthropic tightens usage limits for Claude Code without telling users - Hacker News
- [BUG] Claude Code Usage for Max Plan hitting limits extremely fast - GitHub - Anthropic Claude Code Issues
Related Reading
Open Source UK PM vows action on Grok's deepfake scandal, Starmer condemns X
Open Source GPT-5 helps mathematicians offload tedious tasks, says Timothy Gowers
Open Source India proposes licensing and royalty rules for AI training by Google, OpenAI
From Archives Agent Improvement Loop Starts with Trace, Enabling Deterministic, Low‑Cost Validation
From Archives Anthropic's Mythos Leak Precedes Bland AI's Norm Voice Agent Builder
Common Questions Answered
What caused the rapid draining of Claude's usage limits?
Two unrelated experiments were simultaneously running that impacted usage tracking and display. One was an internal server-side experiment related to message queuing, while the other was an orthogonal change in how thinking was suppressed in CLI sessions.
When were the usage limit issues resolved?
The team resolved the three problems on April 20 with version v2.1.116. The API was not modified during these fixes, which addressed issues in Claude Code, the Claude Agent SDK, and Claude Cowork.
Why was it initially difficult to reproduce the usage limit drainage problem?
The independent nature of the two experiments made it challenging for engineers to consistently reproduce the behavior in a controlled testing environment. The orthogonal changes meant that the bug was not immediately apparent during standard testing procedures.