The Summarize, Restart, and Persist Moves
CoreManage context limits and memory across a conversation · Difficulty 1/5
Explanation
Three Practical Moves
| Move | What it does |
|---|---|
| Summarize | Condense a long thread into a short recap and continue from that |
| Restart | Begin a fresh chat when the current one is cluttered or off-track, carrying over only what matters |
| Persist | Put durable, reusable context (instructions, reference documents) into a Project so it doesn't have to live in a fragile chat history |
These moves address the same underlying problem -- a crowded context window -- from different angles. Summarize and restart both reduce what the *current* conversation is carrying: summarize keeps a condensed thread going, while restart cuts over to a clean one. Persist takes a different approach entirely, moving durable knowledge out of the conversation altogether and into a more stable home (a Project) so it never has to accumulate in chat history in the first place.
Choosing Among Them
- Use summarize when the conversation should continue but has grown long.
- Use restart when the conversation has drifted off-track or is too cluttered to salvage with a summary.
- Use persist for anything durable and reusable -- instructions, reference documents -- so future conversations do not need to rebuild that context at all.
Common exam traps
- Treating summarize, restart, and persist as interchangeable rather than fits for different situations -- persist in particular is a structural fix (moving knowledge to a Project), not just another way to shrink the current thread.
- Repeatedly summarizing or restarting the same durable background information instead of persisting it once into a Project.
Key Takeaways
- Summarize condenses a long thread into a recap and continues from it
- Restart begins a fresh chat, carrying over only what matters, when the current one is off-track
- Persist moves durable, reusable context into a Project so it doesn't live in fragile chat history
- Persist is a structural fix; summarize and restart manage the current conversation's length
Glossary Terms
A persistent workspace in claude.ai that bundles standing Instructions (role, tone, format, rules) and Project Knowledge (uploaded reference documents) so every conversation inside it draws on the same configuration without re-supplying it each time. Scales beyond a single context window because large Project Knowledge is retrieved rather than loaded in full on every turn.
A context management technique that retains only the N most recent conversation turns, evicting older turns as new ones arrive. Simple to implement with zero summarization overhead. Best deployed as a rolling-window+summary-header hybrid to prevent silent loss of early constraints or decisions. One specific technique under the broader umbrella of [context compression](/glossary/context-compression).
A context management approach that condenses older conversation turns or completed task phases into compact summaries, preserving essential conclusions while freeing token budget. Inherently lossy — never summarize active tool results, in-flight constraints, or partially completed tasks. One specific technique under the broader umbrella of [context compression](/glossary/context-compression).
Related Concepts
The Context Window and Quality Drift in Long Conversations
The context window is a finite budget covering instructions, uploaded material, history, and the answer
Claude Product Surfaces: Chat, Projects, Research Mode, Artifacts
Plain chat suits quick, one-off questions with no need for persistent knowledge