CCA-F study guide · Domain 1: Agentic Architecture & Orchestration (27%)

Task 1.7: Session state, resumption and forking

Long investigations outlive a single sitting. A named session can be resumed later, a session can be forked into independent branches to compare approaches from one shared analysis, and when the old context has gone stale it is more reliable to start fresh with a structured summary than to resume.

Updated 10-26-2026 · Official guide §6, Task 1.7

Key points

--resume <session-name> continues a specific prior conversation.
fork_session creates independent branches from a shared analysis baseline.
After code changes, a resumed session must be told which files changed; it cannot detect this itself.
When prior tool results are stale, a new session seeded with a structured summary beats resuming.
Resume when most prior context is still valid; start fresh when it is not.

Common misconceptions

"Resuming is always cheaper, so it is always better." Stale tool results lead to confident wrong answers.
"The agent will notice that files changed." It only knows what it is told.
"Forking re-runs the analysis." It reuses the baseline; that is the point.

Watch for

Resuming over heavily changed code without flagging the changes, and re-analysing a whole codebase to compare two approaches.

Practice Task 1.7

Start with the free 10-question check to see where you stand across all five domains. In CCA Prep Studio, 56 practice items cover this task, each tracked toward your mastery score.

Take the 10-question check Practice free

All Domain 1 tasks · All 30 tasks · The full CCA-F exam guide