Understand and manage context limitations and memory considerations (when to restart, summarize, or persist)
Understand that each chat starts fresh and that long chats degrade, and know when to restart with a summary, persist context in a Project or memory, or move large material into Project knowledge.
Key points
- 1
The context window is Claude's working memory for one conversation. A portion is reserved for the response, and once a conversation approaches the limit Claude tells you; the remedy is to start a new conversation or use a Project.
- 2
Claude does not carry one chat's content into another by itself. Without a persistence feature, each chat starts fresh; "same tone as yesterday" only works if yesterday's draft is pasted, stored in a Project, or covered by memory or chat search.
- 3
Long conversations get slower, consume more usage and become less reliable as early details are crowded out or contradicted. Restating decisions in every message makes the problem worse.
- 4
Restart pattern: ask Claude to summarise the decisions, open questions and constraints so far, then seed a new chat (or a Project) with that summary. Summaries carry state; they should not replace reference documents that need detail.
- 5
Persist pattern: put recurring context (client background, report structure, style rules, handbooks) into Project instructions and knowledge so every chat in the Project sees it.
- 6
For material larger than a conversation can hold, add it as Project knowledge; on paid plans retrieval loads only the relevant portions for each question. Splitting files across parallel chats or shrinking them to a one-page summary loses cross-references or detail.
- 7
Memory (on by default for Free, Pro and Max; off by default for Team and Enterprise until an owner enables it) saves context about your role, preferences and ongoing work, organised as topics you can view, edit or delete in Settings. Each Project has its own memory space. Incognito chats are not saved to memory or history.
- 8
Chat search lets Claude find and reuse past conversations when asked ("what did we decide about X?") on plans that include it; it is a retrieval step, not automatic recall.
- 9
Memory is for preferences and working context, not verbatim documents; it will not store a 300-page procedure set or six syllabi word for word.
- 10
Automatic context management can summarise earlier messages as a chat nears its limit; it keeps the conversation going but uses more of your usage allowance, so restarting or using a Project is still the efficient choice.
- 11
Model tier does not change what is remembered across chats or add room to a chat at its limit.
- 12
Common distractors: "switch to a bigger model so it can reach further back"; "tell Claude to remember harder"; "turn on memory so it memorises the documents"; "keep one enormous chat per client"; "give the chat a good title so Claude can reuse it".
Read the source
Test yourself on Understand and manage context limitations and memory considerations (when to restart, summarize, or persist)
Ten questions, with the answer and explanation after each one.