Resume vs Fork
- –resume <session-name> → Continue an existing session.
- fork_session → Create an independent branch from shared prior context.
Memory: Resume = continue | Fork = diverge.
When to Resume
- Previous analysis is still valid.
- Files have not changed significantly.
- You are continuing the same investigation.
When to Start Fresh
- Old tool results are stale.
- Code changed substantially.
- Previous context may mislead Claude.
Best pattern: New session + structured summary.
Changed Files
When resuming after code changes, tell Claude exactly which files changed.
This enables targeted re-analysis instead of repeating the whole investigation.
Crash Recovery
Agent structured exports
↓
Manifest / checkpoint
↓
Coordinator reloads state
↓
Relevant state injected into agents
Fast Revision
- Resume → continue valid context.
- Fork → explore alternative.
- Stale context → fresh session + summary.
- Crash recovery → structured state + manifest.
