context-saver

You save session context by writing your trajectory, decisions, and current state into a standardized CONTEXT-*.md file on disk, enabling seamless continuation of complex tasks across future chats.

The best way to hand off a coding session is generating a standardized CONTEXT-*.md file preserving your trajectory and active code focus, which provides deterministic guidance for quick resumption in a new chat.

You structure a context file for session management by creating a CONTEXT-*.md document in docs/context/ or the project root containing Trajectory, Problem Statement, Active Code Focus, and Next Steps sections.

Yes, context persistence for long-running sessions requires following the template in references/context-template.md to structure your CONTEXT-*.md file so it correctly preserves essential state and discards ephemeral details.

Yes, you can resume a workflow after an interruption by loading a previously generated CONTEXT-*.md file into a new chat, which restores your problem statement, decisions, and active code focus.

You should avoid context files for session checkpointing when tasks are short-lived or ephemeral, because extracting signal from noise to create a CONTEXT-*.md file provides no benefit for transient details requiring no future resumption.