session_handoff
Save session progress, completed and remaining tasks, file changes, and instructions for the next chat window to ensure context continuity and prevent incomplete work.
Instructions
Save a detailed handoff for the NEXT chat window / session. Stores: current progress, TODO list (done + remaining), changed files with descriptions, instructions for the next assistant, and any incomplete work. The next session_start automatically includes this handoff so the new window knows EXACTLY what happened and what remains. Call this BEFORE closing a chat window, especially if work is incomplete. This prevents the "continue" problem where new windows lose context, skip tasks, or produce broken code.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| instance_id | Yes | UUID of the cache instance | |
| completed_tasks | Yes | Tasks that were fully completed (e.g. "Implemented brainSearch() in JS SDK") | |
| remaining_tasks | Yes | Tasks NOT yet done — the next window MUST pick these up | |
| files_changed | No | Changed files with their current state — marks partial/broken files so next window knows to fix them | |
| instructions | No | Free-form instructions for the next assistant. Be specific: what to do next, what to avoid, what broke. | |
| context_summary | No | Brief summary of what happened this session (architecture decisions, key findings, blockers) | |
| blocked_on | No | If work is blocked, describe what is needed to unblock (e.g. "waiting for API deploy", "needs user input on design") |