Detailed Analysis
A Reddit post in r/ClaudeAI surfaces a mundane but telling friction point in how people actually use Claude day to day: chat organization. The poster describes a common failure mode—an ever-growing sidebar of conversations that becomes unnavigable once the user can no longer recall the exact title they gave a chat weeks earlier. Their workaround was to migrate everything into Claude's Projects feature, splitting conversations by area of life (work, personal, hobbies, etc.). The tradeoff they identify is instructive: Projects are easy to maintain as organizational buckets, but the custom instructions attached to each project tend to become too generic to be useful, since a single project meant to cover "work" or "personal life" broadly can't carry the same specificity as a narrowly scoped project built around one task or context.
This kind of post matters less for any single insight and more as a signal of how power users are pushing against the current limits of conversational AI interfaces. Projects, introduced by Anthropic as a way to group related chats with shared context, custom instructions, and uploaded knowledge, were designed to solve exactly this kind of sprawl. But the tension the poster surfaces—breadth versus specificity—reflects a deeper unsolved problem in AI product design: users want both persistent, retrievable memory across many conversations and highly tailored, context-specific behavior within each one. Folding everything into a handful of broad life-area projects sacrifices the latter for the former, while creating narrow, single-purpose projects for every task would recreate the original sidebar-sprawl problem at a different layer.
The underlying issue points to a broader theme in the evolution of chatbot products: as usage matures beyond one-off Q&A sessions into sustained, multi-week or multi-month workflows, users increasingly resemble knowledge workers managing a filing system rather than casual questioners. This is the same organizational challenge that has shaped email, note-taking apps, and project management tools for decades, and it's now arriving at the doorstep of conversational AI. Anthropic, along with competitors like OpenAI, has been iterating on features like Projects, memory, and custom instructions precisely because raw chat history doesn't scale as a retrieval mechanism—search-by-title or scroll-by-date breaks down once volume crosses a threshold that, based on this user's experience, seems to arrive after only a few weeks of regular use.
More broadly, this thread reflects growing user sophistication and expectation around AI assistants as persistent tools rather than disposable sessions. It also hints at a feature gap Anthropic may want to address: the ability to nest more granular sub-contexts or dynamically scoped instructions within a broader project, so that users don't have to choose between maintainable top-level organization and precise, situation-specific guidance. As memory and continuity features become more central to how companies like Anthropic differentiate their assistants, solving this exact pain point—retaining specificity at scale—will likely become a competitive battleground alongside raw model capability.
Read original article →