Detailed Analysis
A Reddit user on the r/ClaudeAI subreddit has documented a methodical investigation into an unexplained phenomenon: their Claude Max 5x usage meter appeared to climb steadily even after the desktop app was fully closed. Using a macOS setup running Cowork with a custom "Fable 5" configuration, the user watched their session counter tick from 33% to 42% while idle, then jump to 51% after quitting the app with Cmd+Q and waiting roughly nine minutes before reopening. Rather than simply reporting a bug, the poster ran through a thorough diagnostic checklist — scheduled tasks, beta dispatch features, skills, plugins, connectors, active sessions, API keys, and even a `ps aux` process audit — ruling out nearly every conventional explanation for background consumption. The most revealing clue was that the same account, same machine, and same browser session showed the drain only on their Personal Max workspace and never on a separate Team workspace tied to the same email, which effectively eliminates device-level culprits like rogue background processes or leaked session tokens and points instead to something specific to how usage is tracked or billed within a particular workspace context.
The investigation surfaces several under-documented realities about how Claude's infrastructure actually behaves, which matters because they complicate any simple mental model of "usage only accrues when I'm actively prompting the model." The user notes that subagents inherit the parent model's configuration by default, meaning a custom setup like "Fable" can silently spawn additional Fable-flavored subagents that consume tokens without the user explicitly invoking them. Scheduled tasks, they point out, execute server-side in Anthropic's cloud infrastructure regardless of whether the desktop client is open, which means the visible app state and the actual compute state can diverge significantly. Perhaps most tellingly, the user discovered that quitting the app via Cmd+Q does not terminate all associated processes — a helper process from Claude.app persisted on their machine for over 13 hours post-quit, even though it showed negligible CPU usage. These findings collectively suggest that the boundary between "app is closed, nothing is happening" and "background work continues" is far blurrier than users assume.
The poster also self-critiques their own methodology in a way that adds credibility rather than undermining it: reopening a session after closing the app likely re-sends the entire prior conversation — including all screenshot attachments — as fresh input tokens, meaning the apparent "growth while idle" could actually be an artifact of resumption rather than genuine idle-time consumption. This kind of transparent, hypothesis-testing approach is unusual for anecdotal bug reports and signals a broader pattern among power users who are pushing Claude's agentic features (subagents, scheduled tasks, MCP servers, multi-workspace accounts) hard enough to expose gaps in observability. The explicit callout that Claude Code's `/usage` command breaks down consumption by skill, subagent, plugin, and individual MCP server — while the web/desktop app has no equivalent breakdown — highlights a real product gap: as Anthropic pushes users toward increasingly autonomous, multi-agent workflows, the tooling for auditing where tokens actually go has not kept pace with the complexity of what can silently consume them.
This episode is emblematic of a broader tension in the current wave of agentic AI products. As companies like Anthropic layer on features such as scheduled/cloud-resident tasks, subagent delegation, persistent connectors, and multi-workspace billing, the attack surface for "mystery consumption" grows in tandem with capability. Usage-based pricing models depend on users trusting that meters reflect actual work performed, and stories like this — where a technically sophisticated user methodically rules out every conventional explanation and still can't fully explain the behavior — erode that trust faster than outright outages do. It also reflects a maturing user base: rather than assuming a scary AI is "doing something," this poster treats it as a systems debugging problem, cataloguing server-side statefulness, process lifecycle quirks, and workspace-scoped billing anomalies. Whether the root cause turns out to be a UI reporting glitch, a subagent inheritance quirk, or a genuine background-billing bug, the case underscores that transparency and per-source usage accounting are becoming necessary infrastructure — not optional nice-to-haves — as AI agents take on more autonomous, persistent, and cloud-resident responsibilities.
Read original article →