- In short
- The three standard responses to context degradation are restart, summarise, and persist. Restart begins a new conversation when the current one has drifted beyond recovery or a genuinely new task is starting. Summarise captures decisions, work in progress, and open questions, then carries that summary into a new conversation. Persist saves information that should be available in every future session to Memory or the Project knowledge base. The three address different needs and are not mutually exclusive within a workflow.
Three tools for a degraded window
Once you can recognise context degradation, the next skill the CCAO-F exam tests, at the apply level, is knowing what to do about it. There are three standard responses -- restart, summarise, and persist -- and the competence is matching the response to the need, and combining them when a workflow calls for it. They are not competing options so much as complementary tools.
Each response targets a different aspect of the problem. Restart deals with the degraded conversation itself. Summarise deals with preserving the work done in it. Persist deals with facts that should outlive any single session. Because they address different needs, a real workflow often uses more than one together. Knowing what each does, and that they combine, is what this knowledge point delivers, feeding both choosing between restart and summarise and memory persistence.
- Restart, summarise, persist
- The three standard responses to context degradation. Restart begins a new conversation when the current one has drifted beyond recovery or a genuinely new task starts. Summarise captures decisions, work in progress, and open questions, then carries that summary into a new conversation. Persist saves information needed in every future session to Memory or the Project knowledge base. They address different needs and are not mutually exclusive.
What each response does
Restart means beginning a fresh conversation. It is the right move when the current session has drifted beyond recovery, or when you are starting a genuinely new task within the same workstream. Restarting clears the degraded window and starts clean. In a Project, the standing instructions and knowledge base carry into the new conversation automatically, though the conversation thread itself does not.
Summarise means, before starting anew, capturing the current state -- the decisions made, the work in progress, and the open questions -- and carrying that summary into the new conversation as its starting context. This preserves the thread's substance across the boundary without dragging the degraded window along. Persist means saving information that should be available in every future session, not just the next one, to Memory or the Project knowledge base. Persist is about durability across many sessions; summarise is about continuity into the next one. The distinction between what to persist and what not to is developed in memory persistence and curation.
They combine
The responses are not mutually exclusive, and treating them as a single either/or choice is a mistake. A well-run workflow often uses all three in sequence. Facing a degraded session near the end of a large task, you might persist the durable facts to the knowledge base so they survive indefinitely, summarise the in-progress state so the next conversation continues smoothly, and then restart into a fresh conversation that begins with that summary. Each response handles a layer the others do not.
Seeing them as complementary changes how you act. Rather than asking "should I restart or summarise or persist," you ask which needs are present -- is the window degraded, is there work to carry forward, are there facts that should outlive the session -- and apply the responses those needs call for, possibly several at once. This layered view is what makes the responses a toolkit rather than a menu.
What the CCAO-F exam trips candidates on
Two errors are tested. The first is restarting a session without capturing a summary first, losing the work already done. Restart alone clears the window but also discards the in-progress state unless you summarise before starting anew. The credited workflow summarises first, then restarts.
The second is persisting a transient, one-time detail to Memory that will not recur and only adds clutter. Persist is for information needed across future sessions, not for every passing detail. A question may show someone saving a one-off fact to Memory; the credited reading reserves persistence for durable, recurring information and lets transient details go.
Worked example
Deep into a long, degraded session, an analyst has made several key decisions, has work half-finished, and has established a couple of standing constraints that will apply to all future work in this workstream. She wants to move to a clean conversation. What should she do, and what should she avoid?
This situation actually calls for all three responses, because three distinct needs are present -- and the traps lie in using too few of them or misapplying one.
The standing constraints that apply to all future work in the workstream should be persisted: saved to Memory or the Project knowledge base so they are available in every future session, not just the next one. That is exactly what persist is for -- durability across many sessions.
The key decisions and half-finished work should be summarised before she leaves: capture the decisions made, the work in progress, and the open questions, so that substance can be carried into the new conversation. Skipping this and simply restarting would lose the work already done, which is the first trap. The summary is what preserves continuity across the boundary.
Then she should restart into a fresh conversation, pasting the summary as its starting context, clearing the degraded window. The order matters: persist and summarise first, restart last. What she should avoid, beyond restarting without summarising, is padding Memory with transient details from this session that will not recur -- only the durable standing constraints belong there; the one-off specifics belong in the summary, not in Memory. Used together and in order, the three responses move her cleanly to a fresh window without losing anything that mattered.
Common misreadings to avoid
Misconception
When a session degrades, just restart into a new conversation.
What's actually true
Misconception
Anything worth remembering should be persisted to Memory.
What's actually true
How this shows up on the exam
Questions describe a degraded session and ask what to do, with distractors that restart without summarising or persist transient details. Identify the needs present -- degraded window, work to carry forward, facts to keep across sessions -- and apply the matching responses, in the order persist and summarise before restart. The reliable answer treats the three as combinable tools, not an either/or choice.
This knowledge point builds on recognising context degradation and unlocks choosing between restart and summarise and memory persistence and curation.
An analyst in a long, degraded session has made key decisions, has half-finished work, and has set standing constraints for all future work in the workstream. She wants a clean conversation. What is the best sequence?
People also ask
What are the responses to a degraded Claude session?
What should I persist to Memory?
Can I combine restart, summarise, and persist?
Watch and learn
Official Anthropic Academy lessons first, then hand-picked walkthroughs. Videos load only when you press play.
No videos curated for this concept yet
We are still curating the best official and community videos for this topic.
Official prep for this domain
Anthropic's own free prep module for this part of the syllabus, on the official prep course. Free with an Anthropic Academy sign-in.
References & primary sources
Master this concept with Archie
Practice it inside an adaptive study session. Archie, your Socratic AI tutor, tracks your mastery with Bayesian Knowledge Tracing and schedules the perfect next review.