Detailed Analysis
A Reddit user posting to r/claude raises a common point of confusion about Anthropic's Projects feature in Claude: individual conversations within a project do not share conversational context with one another. The user created a project, conducted a lengthy conversation, then started a new chat within the same project expecting continuity, only to find the new session had no memory of the prior exchange. The post reflects a fundamental misunderstanding of what Projects are architecturally designed to do, which points to a broader gap between user expectations and product communication.
Claude's Projects feature is not designed to create a persistent conversational memory that flows between chats. Instead, Projects function as a persistent *configuration* layer — allowing users to attach files, documents, and custom instructions (a "project prompt") that are automatically loaded into every new conversation within that project. Each individual chat still operates within its own discrete context window. The value proposition of Projects, therefore, is consistency of *setup* rather than continuity of *conversation*. A user working on a software codebase, for example, can attach their repository files and a set of behavioral instructions once, and every new chat in that project inherits that foundation without re-uploading materials each time.
The confusion is understandable because the word "project" carries strong associative weight from tools like Notion, Linear, or even Google Docs, where a project implies a shared, accumulating workspace. Users reasonably infer that a "project" in an AI assistant context should function like a unified memory space. This expectation gap is a significant UX challenge for Anthropic, as the feature's utility — while real — requires users to reframe what "shared context" means in a stateless, context-window-bound system.
This tension connects to one of the most actively discussed limitations in the broader AI assistant landscape: the absence of long-term, cross-session memory. All major frontier AI systems, including Claude, ChatGPT, and Gemini, have grappled with how to simulate persistence without the architectural ability to natively recall prior conversations. OpenAI has introduced explicit "Memory" features that summarize and store facts across chats; Anthropic has taken a more document-centric approach with Projects. Neither solution fully satisfies the intuition that a digital assistant should "remember" the way a human colleague would.
The Reddit post ultimately illustrates a critical product communication challenge for Anthropic: the distinction between *context injection* (what Projects do) and *cross-chat memory* (what Projects do not do) is consequential enough that users discovering the difference organically — through failed expectations — risk churning or misjudging the product's capabilities. As AI assistants move toward deeper workflow integration, the industry will increasingly need clearer taxonomies and onboarding flows that set accurate mental models for features that have no clean analog in prior software paradigms.
Read original article →