session-control

To resume a workflow session, pass the --resume flag to the /work command. This updates session.json and session.events.jsonl to restore the exact context and log subsequent changes for audit.

Forking a session branches the current workflow state by applying the --fork flag to /work. It creates a new execution path while preserving the original session context in session.json for reproducibility.

Session state changes are logged automatically to session.events.jsonl when you resume or fork workflows. This audit-friendly event log ensures traceability for automated bash execution paths.

Yes, session control requires no external dependencies. It operates internally using bundled scripts to validate argument handling and update state files like .claude/state/session.json directly.

You need session state management when running complex automated workflows that require traceability and reproducibility. It allows you to resume interrupted executions or branch workflows without losing prior context.

Session updates fail if argument validation scripts reject the flags or if the workflow does not properly invoke /work with --resume or --fork. Verify the command syntax to ensure session.json updates correctly.