context-save

To save your working context, you instruct the system to capture your current git state, branch, uncommitted changes, decisions, and remaining tasks into a deterministic checkpoint. This persists your session provenance so you can restore the exact project state later without losing momentum.

The best way to checkpoint a complex workflow is to capture the current project state, including git state, decisions made, and remaining work. This creates a reliable checkpoint with traceability that works across branches and environments, ensuring seamless restoration when you return.

Session restore works by persisting your uncommitted git changes, branch context, decisions, and remaining tasks into a saved state. When you resume, this deterministic save with provenance and traceability is loaded, returning you to the exact point you left off without data loss.

You do not need to commit your work before saving the current project context. The context capture process explicitly records uncommitted changes and decisions made during the session, allowing you to save progress mid-workflow and resume later with full traceability of your pending state.

Yes, you can use context checkpointing across different branches and environments. The system captures the full project state including git state and decisions, providing a reliable checkpoint for complex work that ensures seamless restoration regardless of where you resume the session.

When saving and restoring a working session, expect that the checkpoint captures git state, decisions, and remaining tasks deterministically. While it ensures traceability and provenance across branches, complex uncommitted environmental states outside the tracked project context may not be fully restored without explicit session-restore actions.