Detailed Analysis
A Claude Pro subscriber on Reddit's r/Anthropic community has raised a pointed complaint about unexpectedly rapid session token consumption within Anthropic's Projects feature, a tool designed to give users persistent, organized workspaces across multiple conversation threads. The user, paying $100 per month for the service, reports burning through 65% of their session allocation within just thirty minutes of starting a fresh thread — primarily by having Claude read transfer documents and engage in general conversation. Compounding the frustration, an accidental click of the "retry" button on an older message during a migration between threads apparently wiped out multiple days of prior conversation, and the user reports that even Claude's internal context-compacting process consumed approximately 10% of session capacity on its own. These are not edge-case grievances; they point to structural tensions in how Claude's Projects architecture manages context at scale.
The underlying mechanics driving this consumption are rooted in how large language models handle context windows and how Anthropic's platform manages token accounting. When a user transfers extensive documentation into a new thread — particularly as part of a cross-thread migration — the model must ingest and process that content in full, which is inherently expensive in token terms. Claude's compaction feature, designed to summarize and compress long conversations to extend usability, is itself a token-intensive operation, essentially generating a dense summary that must be prepended to the continued conversation. On a plan with fixed monthly usage limits, these overhead costs accumulate quickly and non-transparently, leaving users with little visibility into what is consuming their allocation and why. The accidental retry behavior that destroyed prior conversation history also suggests insufficient safeguarding around destructive actions in the UI — a UX failure that is separate from, but compounded by, the token drain issue.
Research context drawn from Claude Code's open GitHub issues suggests that timeout failures, repeated API retries, and large prompt ingestion are well-documented contributors to session exhaustion, particularly in new or freshly initialized project threads. While the Reddit user does not appear to be using Claude Code specifically, the same fundamental dynamics apply: when Claude must process large volumes of text at session initialization — whether through CLI tooling or the web interface's Projects feature — the token cost is front-loaded and disproportionately high relative to what users typically expect from a "new" session. Anthropic has been actively patching related issues in Claude Code (GitHub issues #5851, #5615, and #20519 among them), but the web-based Projects interface has received less granular public documentation about its internal token accounting behavior.
This situation reflects a broader tension in the commercialization of large-scale AI assistants: the gap between user mental models and technical realities. Subscribers reasonably interpret "a new thread" as a clean slate with minimal overhead. In practice, Projects threads inherit shared context, persistent files, and architectural state that carry token costs from the moment of initialization. Anthropic's $100/month Pro plan is marketed as a high-capacity offering, but users engaged in complex, document-heavy workflows — exactly the demographic Projects is designed to serve — can exhaust meaningful portions of their allocation through routine operations. Until Anthropic provides real-time, granular token usage dashboards and clearer documentation of how compaction, document ingestion, and thread initialization consume capacity, power users will continue encountering these limits unexpectedly and without recourse beyond rationing their interactions.
The incident also signals a product design challenge that is not unique to Anthropic: as AI platforms add features meant to enhance productivity and persistence (like Projects, memory, and cross-thread continuity), each new layer of sophistication introduces new hidden costs and new failure modes. The accidental data loss via retry button and the opaque token consumption are symptoms of a platform that has grown in capability faster than its user-facing controls and transparency mechanisms have matured. Addressing this will likely require not only UI guardrails against destructive actions but also a fundamental rethinking of how session limits are communicated and managed for users operating at the boundary of what the platform's architecture can efficiently support.
Read original article →