CCA Prep
CCAR-FUA

Lesson 1.7Lesson 7 of 30

Sessions, resumption and forking

Manage session state, resumption, and forking

Sessions, resumption and forkingShared analysis--resume auth-refactor+ "changed: a.ts, b.ts"fork_session → strategy Afork_session → strategy BResultsstale?New session +structured summary

Key points

  1. 1Name sessions and continue them later with --resume <session-name>.
  2. 2When resuming after code changed, tell the agent exactly which files changed so it re-reads only those.
  3. 3fork_session branches independent sessions from one shared analysis, e.g. to compare two refactoring strategies.
  4. 4If most earlier tool results are stale, start a new session with a structured summary instead of resuming.
What the exam guide checks here

Objective wording from the exam guide (English).

  • 1.7.K1Named session resumption with --resume <session-name>
  • 1.7.K2fork_session creates independent branches from a shared analysis baseline
  • 1.7.K3Tell a resumed agent which previously analysed files changed
  • 1.7.K4A new session with a structured summary is more reliable than resuming with stale tool results
  • 1.7.S1Use --resume with session names across work sessions
  • 1.7.S2Use fork_session to compare approaches (e.g. two testing or refactoring strategies)
  • 1.7.S3Choose resume (context mostly valid) vs fresh start with injected summary (stale results)
  • 1.7.S4Inform a resumed session about specific file changes for targeted re-analysis

Lock it in

Answer scenario questions on this topic. Every option comes with an explanation.

Practise 1.7 · 23 questions