save-state

Save session state by dumping your current task summary, progress, decisions, git diff listings, and blockers into production/session-state/active.md before clearing history. This checkpoint file captures the working context so a new session can resume without losing task details.

The best way to checkpoint conversation context is writing task summaries, open questions, and next steps to active.md, while extracting broad architectural lessons into .claude/memory/ files to keep long-term durable memory alive across sessions.

Save your working context when nearing context compaction limits, before clearing conversation history, and at the end of work sessions. Checkpointing at these points ensures you can quickly restore the conversation state and resume without missing anything.

Yes, context-saving works with git diff listings by collecting them alongside task summaries and open questions before writing the checkpoint file. This captures file changes and progress accurately for reliable recovery in the next session.

Yes, you can extract broad architectural lessons or constraints into .claude/memory/ files before overwriting active.md. This keeps long-term durable memory alive while the active session state is reset for new tasks.

A new session starts blind without a checkpoint because previous task details, decisions, and progress are lost during context compaction or history clearing. Predefined hooks automatically surface the saved state file during session start to prevent this.