handoff

To preserve conversation context across multiple sessions, you structure completed steps, current status, and next steps into a persistent file. This approach saves your task progress as a recovery point, allowing long-running workflows to resume seamlessly after interruptions.

The best way to save and restore interrupted task context is by writing a structured handoff file that captures your exact progress. This creates a reliable snapshot of your work, ensuring that the next session can pick up exactly where the previous one left off.

Yes, you can use git to commit changes and capture recovery points during a cross-session handoff. The process coordinates with your version control system to securely persist task context alongside your code changes, ensuring both progress and state are tracked.

To start a session restoration, you read the structured handoff file which details your previously completed steps, current status, and upcoming next steps. This file acts as a persistent guide to quickly reload the necessary context and continue your workflow immediately.

No specific dependencies are required to automate cross-session handoffs, as the core mechanism relies on writing a standard markdown file. However, integrating with git is optional and requires a git environment if you want to capture versioned recovery points.