Detailed Analysis
A Reddit post in r/ClaudeAI captures a recurring frustration among Claude users engaged in long-form creative work: the automatic "compacting" of conversations, a context-management feature that summarizes and compresses prior dialogue once a session approaches its token limit. The original poster describes working on a book project with Claude, only to find that nearly every session—roughly every five hours—triggers a compaction event before substantive work can resume. In the specific case described, the user returned to continue a chapter after running out of usage, watched Claude begin the task, then abruptly pivot to compacting the chat instead. By the time compaction finished, session usage had already jumped to 84%, and by the time the chapter itself was completed, usage had climbed to 98%—leaving little room for further iteration before the cycle repeats.
This complaint highlights a structural tension in how large language models like Claude manage extended interactions. Compaction exists to solve a real problem: conversations that exceed the model's context window need to be summarized so that Claude can "remember" earlier content without literally holding the entire raw transcript in active memory. For short-lived tasks, this is largely invisible and beneficial. But for sustained creative projects like novel-writing, where nuance, voice, character consistency, and plot continuity accumulate over tens of thousands of words, compaction can feel like a lossy compression that eats into the very usage budget it's meant to preserve. The user's core complaint isn't that compaction happens, but that it consumes a disproportionate and unpredictable share of session capacity—sometimes finishing a single chapter costs more in "overhead" than in actual output.
This tension matters because it exposes a gap between how AI companies design context-management systems and how creative professionals actually work. Book projects, unlike coding tasks or one-off Q&A sessions, require persistent state across many hours and sessions—something current context windows and usage-based pricing models aren't fully optimized for. Anthropic, like other AI labs, faces the challenge of balancing computational cost, context window size, and user experience: larger context windows and less aggressive compaction would ease this friction but at higher compute expense, which either gets passed to users through pricing tiers or absorbed by the company. The frustration voiced here is emblematic of a broader user base pushing against the limits of subscription-tier usage caps, especially as more people use Claude for long-duration, high-context creative and professional work rather than quick queries.
More broadly, this episode reflects an ongoing trend in the generative AI space: as tools like Claude, GPT, and Gemini get marketed as capable collaborators for long-term projects—novels, codebases, research papers—the underlying infrastructure (context windows, memory systems, session limits) is still catching up to that promise. Features like Claude's "Projects," memory tools, and extended context windows are attempts to address exactly this gap, but as this thread shows, the mechanics of automatic compaction remain opaque and frustrating to end users who lack fine-grained control over when and how their context gets summarized. Community discussions like this one often surface practical workarounds—manually saving chapter summaries outside the chat, breaking work into smaller discrete sessions, or using Projects/artifacts to persist key details—but they also serve as informal feedback loops that can pressure companies like Anthropic to give users more transparency and control over context management as long-horizon AI collaboration becomes more mainstream.
Read original article →