Session Checkpoint
Purpose: Quickly save current state so you can recover after a session failure.
Instructions
Update the Quick Recovery section at the top of SESSION_CONTEXT.md with:
- Current timestamp
- Branch name (run
git rev-parse --abbrev-ref HEAD) - Working on - Brief description of current task
- Files modified - List files changed since last commit
(
git diff --name-only) - Next step - What to do next if session dies
- Uncommitted work - Yes/No
Quick Recovery Template
Update SESSION_CONTEXT.md "Quick Recovery" section with this format:
## 🔄 Quick Recovery
**Last Checkpoint**: YYYY-MM-DD HH:MM **Branch**: `branch-name-here` **Working
On**: [brief task description] **Files Modified**: [list or "none"] **Next
Step**: [what to do next] **Uncommitted Work**: yes/no
Also Update State Files
Write current task state to .claude/state/ for compaction recovery:
If working on a multi-step task, write/update
.claude/state/task-{name}.state.json:{ "task": "task-name", "started": "ISO datetime", "lastUpdated": "ISO datetime", "steps": [ { "name": "Step 1", "status": "completed" }, { "name": "Step 2", "status": "in_progress" }, { "name": "Step 3", "status": "pending" } ], "context": { "branch": "branch-name", "notes": "key info" } }Update
.claude/state/handoff.jsonwith current progress (thecompaction-handoff.jshook does this automatically, but manual updates add richer task-specific context).
Also Consider
If uncommitted work exists, consider committing now:
git add -A && git commit -m "WIP: checkpoint before potential failure"If working on risky operations, push the branch:
git push -u origin $(git rev-parse --abbrev-ref HEAD)
When to Use This Command
- Before large file operations
- Before complex multi-step tasks
- When you notice session becoming slow
- Periodically during long sessions (every 30-60 minutes)
- Before any operation that previously caused failures
Run this checkpoint now and update SESSION_CONTEXT.md.