Claude Code users report quota burn and usage-meter failures

• Claude Code users reported quota burn without usable output: salamandyr's Reddit report described subagents hanging while quota kept burning, and ProperHelp1743's desktop report showed 49 tokens after 17.5 minutes.
• The usage UI looked inconsistent for some accounts: emericarust's report said a fresh chat hit a monthly limit while 5-hour and weekly meters looked empty, and chrisbbh's reset-bug report said limits jumped from 99/96 to 11%.
• Longer contexts turned into a cost-management problem: Spirited_Tie_3473 tied resume-session burn to enormous contexts, while dejavucoder blamed an old tab for invalidating the prompt cache.
• The failure mode was not just metering: ParticularAnt5424 said the bundled verify skill spent a full limit trying to install and rerun E2E tests for a 10-line change.
• Anthropic eventually reset both 5-hour and weekly limits, and kimmonismus's screenshot showed a restored 100% usage panel after ClaudeDevs announced the reset.

The strangest reports were mundane: subagents that hang while spending quota, fresh chats blocked by a monthly-limit message, and verification loops that turn a tiny UI edit into a full-account burn. The same week had Fable builders racing the ceiling on purpose, with elder_plinius using a one-shot prompt to parallelize dozens of agents into more than 50 playable demos, while doodlestein reported one Fable account that seemed to keep going when five others drained quickly. Claude Code's own releases were moving fast too: ClaudeCodeLog logged /doctor becoming /checkup, and the 2.1.207 changelog shipped a terminal-freeze fix plus auto mode changes.

The clearest failure report came from subagents. salamandyr said Opus 4.8 was asked to run coding workflows with Opus 4.6, appeared to spin up multiple agents, then left them hanging after a few seconds while quota continued burning.

ProperHelp1743 reported a different stall path in the macOS desktop app: a fresh session, cache clearing, restart, logout, login, and full app reset still left Claude producing 49 tokens in 17.5 minutes.

Both reports describe metered work with no useful forward motion.

Usage accounting looked split across surfaces. emericarust said a fresh chat claimed a monthly limit was hit, while the 5-hour and weekly meters looked basically empty and the website and client showed different figures.

chrisbbh saw another reset failure mode: limits showed 99/96 after a reset, then minutes later dropped back to 11%. Alone-Hat-Cap said support suggested the account was running out quickly because it was not Pro, even though the user said it was a Pro account Alone-Hat-Cap's subscription report.

Kimmonismus had a more visible before-and-after. His pre-reset screenshot showed 0% left on the 5-hour limit and 72% left weekly, and his follow-up showed both meters restored to 100%.

nptacek's weekly-limit screenshot split the problem by model pool: all models were 53% used, while Fable-only usage was 96% used nptacek's weekly-limit screenshot. Earlier, kimmonismus argued a reset was appropriate after Anthropic extended Fable 5 through the end of the week.

The reset came when ClaudeDevs said Anthropic had reset 5-hour and weekly rate limits for all users.

Large context created a quieter cost trap. Spirited_Tie_3473 said resuming sessions could burn usage because the context was enormous in token count, without the old visual warning or auto-compaction behavior kicking in.

Prompt caching added another edge. dejavucoder said asking a question in an old Claude Fable tab triggered higher usage because the prompt cache had already been invalidated dejavucoder's prompt-cache post.

Claude Code's new /checkup command reads like a direct response to context rot. bcherny's post said it can:

1. Clean up unused skills, MCPs, and plugins.
2. Deduplicate local CLAUDE.md against the checked-in version.
3. Break a root CLAUDE.md into nested CLAUDE.md files and skills.
4. Turn off slow hooks.
5. Update Claude Code.
6. Enable auto mode by default.
7. Pre-approve frequently denied read-only commands.

A separate aibuilderclub_ post framed /checkup as an audit for old skills, unused MCPs, forgotten plugins, and CLAUDE.md files that load too much context every session.

ParticularAnt5424 asked for a simple version number at the bottom of a screen. Claude loaded the bundled verify skill, tried to install packages to compile and run the entire game for E2E tests in a temp folder, failed, retried, and consumed the full limit.

That incident matches the broader complaint that coding-agent harnesses keep accumulating prompt text, skills, tools, and hooks. Vtrivedy10 argued Claude Code's harness is broad because it serves many downstream personas, while a company-specific harness can be narrower.

The release notes show Anthropic was already patching adjacent verify behavior. Claude Code 2.1.205 fixed project verify skills being rewritten on every session, according to the 2.1.205 changelog.

Fable 5 made the quota story harder to read because some users were deliberately spending as fast as possible. elder_plinius used an unused Claude Max 20x account near reset, asked Fable to parallelize dozens of agents, and ended up with more than 50 playable games.

The ceiling still appeared. In a follow-up, elder_plinius said the run hit the 5-hour limit twice before the weekly usage was gone, adding that far more games would be possible without rate limits.

Doodlestein reported the opposite anomaly: one Mac and account used for FrankenSim seemed to keep going, while five other dev machines and accounts drew down Fable usage quickly. His reply said the account was running xhigh across about five sessions at once, and another reply said the model itself seemed normal while the usage was unusual.

Even the jokes turned into billing speculation. doodlestein's reply floated the idea of Fable tricking Anthropic's billing system, and nptacek's post showed Claude treating a $30 API-credit drain as a billing-routing problem in its own project memory.

The parallel OpenAI rollout sharpened the quota comparison. kimmonismus cited Sam Altman's claim that GPT-5.6 Sol was 54% more token-efficient on agentic coding, then said he could not confirm it because he was hitting rate limits faster than ever on Pro.

Other Sol users narrowed the mechanism to effort levels. pvncher said 5.6 Sol Medium and 5.5 Medium are not 1:1, that 5.6 Sol Low is the default for a reason, and that xhigh is only needed for very tough problems pvncher's effort-level post.

OpenAI's public response was unusually explicit. thsottiaux said OpenAI had reset usage limits across Codex and ChatGPT Work, would reset again later that day, and had made the highest-compute settings too easy to use without making their impact on usage limits clear.

His same update named other launch problems: a desktop reorganization that hid chats and projects, Codex fans worrying Codex was being phased out, regressions in existing multi-agent workflows, plugin rough edges, and a next-week plan to make usage and reset timing more visible.

Claude Code 2.1.207 landed with 24 CLI changes and two system prompt changes. The most relevant fix for the stall reports was terminal responsiveness: long lists, tables, paragraphs, and code blocks had been freezing the terminal and lagging keystrokes.

The same changelog fixed several agent-run surfaces:

• Malformed teammate mailbox messages could crash-loop agent teams every second until the mailbox file was manually deleted.
• Background sessions that entered a git worktree could resume blank after a cold reopen from the agent list.
• Remote Control task status updates could be lost after a network interruption or credential refresh.
• Desktop-hosted Remote Control sessions could fail to show background-agent and workflow progress on mobile and web.

Auto mode changed too. ClaudeCodeLog said 2.1.207 made auto mode available without CLAUDE_CODE_ENABLE_AUTO_MODE on Bedrock, Vertex AI, and Foundry, added disableAutoMode as the off switch, and moved auto mode configuration out of repo-resident .claude/settings.local.json into user-level ~/.claude/settings.json ClaudeCodeLog's additional updates.

The prompt surface grew. The same update reported +11,939 prompt tokens, a +9.0% increase, and a new system reminder telling Claude to use persistent file-based memory, prefer file-based tools over shell, and use Agent or subagents for broad code exploration.

The community response was to build thinner wrappers around the expensive parts.

RDXmin compresses tool output, logs, and prose, removes duplicate output, strips ANSI sequences, and supports multiple optimization modes. Its author claimed 40-60% reductions on tested coding conversations and linked a GitHub repo plus an npm package.

Webify targets WebFetch specifically. Its author said Claude often dumps 3,000-15,000 tokens from a page into context, while Webify parses the HTML into a DOM graph, scores nodes with BM25, traverses nearby nodes with BFS, and usually returns 80-300 tokens.

The Webify benchmark was small but concrete: 15 unseen queries, Sonnet as judge, Webify at 68/75 and Deep Research at 73/75. The author put the project at GitHub.

LangChain attacked observability instead of compression. LangChain's plugin post said three commands and one JSON block can trace every Claude Code message, tool call, and subagent run into LangSmith.