checkpoint

To save session state for recovery, run the checkpoint command to persist the current context locally. It writes handoff.json and per-task state files to the .claude/state directory, enabling a deterministic save-and-resume workflow after failures.

Persisting session context across multiple sessions requires using the optional MCP memory integration. By enabling the --mcp flag, the session state is stored in MCP memory, allowing cross-session recovery and resumption points beyond local file persistence.

Session checkpointing works with local file storage by default, saving minimal viable state directly to the .claude/state/ directory. This enables quick recovery locally after a terminal disconnect or system crash without requiring external dependencies.

You need to save progress during long-running tasks to prevent data loss from interruptions. Creating lightweight checkpoints captures the minimal viable state required to resume tasks seamlessly after unexpected restarts or terminal disconnects.

To resume a task after a terminal disconnect, rely on the previously saved checkpoint state. The skill captures minimal viable session context in local files, allowing you to recover your exact progress and continue the workflow deterministically.

You can use MCP memory for cross-session state persistence by enabling the optional --mcp flag. This stores the session context in MCP memory, extending recovery capabilities beyond the default local file storage for continuous workflows.