Resume, fork or start fresh?
You come back to work Claude started earlier. Every option on the exam is a real way to carry on, and each one is right somewhere. The trap is picking the one that suits a different situation: resuming when the code has moved on, starting over when nothing changed, or trying two ideas one after the other in the same session.
D1 Agentic ArchitectureExam guide 1.7About 12 minutes
Start here: the bookmark, the photocopy and the fresh notes
You are reading a long book, with notes in the margins.
Claude's sessions work the same way. Everything Claude read in a session is kept as tool results: snapshots of the files as they were when it read them. Snapshots don't update when the code does.
--resume <session-name>reopens a named session with its whole history, snapshots included. It is the bookmark.fork_sessionmakes independent branches from one shared starting point. Each branch has the full history; neither sees the other's work. It is the photocopy.- A new session with a structured summary starts clean, seeded with a short, organised list of findings, decisions and what is left. It is the fresh notes. A structured summary means headed sections, not a paragraph of prose.
- Still true, one path:
--resume <session-name>. Keep everything it learned. - Still true, two paths (try two approaches, compare options):
fork_session, one branch per approach. - Mostly no longer true (many files changed, a refactor, or you can't say which files moved): a new session seeded with a structured summary, then re-read what changed.
- Mostly still true, a small known change (one or two files you can name): resume and tell the agent which files changed. It keeps every finding that still holds and re-reads just those files.
To tell these two apart, ask how much of what the session learned is now wrong. If only a little, and you know which part, correct it by naming the files. If a lot, or you can't tell, start clean from a summary.
Words in the question that tell you which side you're on
Resume
- “continue yesterday's session”
- “nothing has changed”, “nobody has touched”
- “named session”
- “pick up where it left off”
Fork
- “try two approaches”
- “compare options”
- “from the same starting point”
- “keep the better one”
Fresh, with a summary
- “files changed since”
- “a teammate merged”, “refactored”
- “stale tool results”
- “results are out of date”
Try it: carry on yesterday's work
Pick a situation, then pick how you carry on. The table shows what Claude's context says about each file against what is true now, with stale snapshots in pink. Below it, the run plays out. The diagram above highlights where your choice sits.
What Claude believes, and what is true
What happens next
The minutes are illustrative, chosen to show the shape. They are not measurements. The exam guide's point is that tool results do not update when files change, that a fork shares its starting point, and that a fresh session with a structured summary is more reliable than resuming with stale tool results.
Things to try: teammate changed 3 files + --resume, and watch the pink rows turn into rework. Then + tell it which files changed, and + new session with a summary. Then nothing changed + new session from scratch, the trap in reverse. Last, two approaches + --resume against fork_session.
The three traps
| Trap | What the wrong option looks like | Why it loses |
|---|---|---|
| Stale results | “Resume the session and carry on” after a merge or refactor; forking a session whose snapshots are out of date | The old tool results still describe the old code. Telling the agent what changed helps, but a fresh session with a structured summary is more reliable. |
| Wastes work | “Start a new session and explore again”, or a summary, when nothing has changed | It works, but it throws away context that was still true and repeats the exploration. |
| Polluted context | “Try approach A, then approach B in the same session” | The first attempt's reasoning colours the second. A fork gives each approach a clean branch from the same start. |
Practice: three exam-style questions
Answer first, then open “Think it through”.
Rule to remember
Exam guide 1.7: “--resume <session-name> continues a specific prior conversation.” “fork_session creates independent branches from a shared baseline.” “Inform the agent about file changes when resuming after modifications.” “Starting a new session with a structured summary is more reliable than resuming with stale tool results.”
A note on names: this page uses the exam guide's fork_session. In today's tools, forking is an Agent SDK session option, and the Claude Code command line spells it --fork-session, used together with --resume.