save — Claude Code command: what it does, how to install
save preserves session context, discoveries, and recovery points through Serena MCP. Use it when work needs to continue across sessions.
MIT ★ 23,950 updated 2026-09-27
.claude/commands/save.mdWhat save does
The command reviews the current session, identifies useful discoveries, and stores them through Serena MCP. It can preserve the full context, save learnings only, create a session summary, or add a recovery checkpoint.
Serena MCP is required for memory access and cross-session persistence. The flow coordinates write_memory, read_memory, think_about_collected_information, summarize_changes, and TodoRead to record decisions, findings, and task progress. Without Serena MCP integration, the command will not operate.
Run /sc:save for a standard save, /sc:save --type learnings for new insights, or /sc:save --type all --checkpoint for a full checkpoint. Add --summarize to generate session documentation.
What it helps with
- preserve the current session context
- record discoveries and technical decisions
- create a recovery point for ongoing work
- prepare a summary for the next session
Example prompts for the agent
- Save the current session context with
/sc:save. - Store only new discoveries with
/sc:save --type learnings. - Preserve all context and create a recovery point with
/sc:save --type all --checkpoint.
How to install save
Manually: put the files in place
.claude/commands/save.mdCall it with /save. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/save.mdCall it with /prompts:save. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/save.prompt.mdManually: put the files in place
.gemini/commands/save.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about save
How do I install save in Claude Code?
Place the command file at .claude/commands/save.md.
What does save do?
It stores session context, discoveries, and progress through Serena MCP. It can also create checkpoints and a session summary.
What does save require?
Serena MCP must be connected with access to memory operations. The command does not work without that integration.
Source text
save.md · MIT
--- name: save description: "Session lifecycle management with Serena MCP integration for session context persistence" category: session complexity: standard mcp-servers: [serena] personas: [] --- # /sc:save - Session Context Persistence ## Triggers - Session completion and project context persistence needs - Cross-session memory management and checkpoint creation requests - Project understanding preservation and discovery archival scenarios - Session lifecycle management and progress tracking requirements ## Usage ``` /sc:save [--type session|learnings|context|all] [--summarize] [--checkpoint] ``` ## Behavioral Flow 1. **Analyze**: Examine session progress and identify discoveries worth preserving 2. **Persist**: Save session context and learnings using Serena MCP memory management 3. **Checkpoint**: Create recovery points for complex sessions and progress tracking 4. **Validate**: Ensure session data integrity and cross-session compatibility 5. **Prepare**: Ready session context for seamless continuation in future sessions Key behaviors: - Serena MCP integration for memory management and cross-session persistence - Automatic checkpoint creation based on session progress and critical tasks - Session context preservation with comprehensive discovery and pattern archival - Cross-session learning with accumulated project insights and technical decisions ## MCP Integration - **Serena MCP**: Mandatory integration for session management, memory operations, and cross-session persistence - **Memory Operations**: Session context storage, checkpoint creation, and discovery archival - **Performance Critical**: <200ms for memory operations, <1s for checkpoint creation ## Tool Coordination - **write_memory/read_memory**: Core session context persistence and retrieval - **think_about_collected_information**: Session analysis and discovery identification - **summarize_changes**: Session summary generation and progress documentation - **TodoRead**: Task completion tracking for automatic checkpoint triggers ## Key Patterns - **Session Preservation**: Discovery analysis → memory persistence → checkpoint creation - **Cross-Session Learning**: Context accumulation → pattern archival → enhanced project understanding - **Progress Tracking**: Task completion → automatic checkpoints → session continuity - **Recovery Planning**: State preservation → checkpoint validation → restoration readiness ## Examples ### Basic Session Save ``` /sc:save # Saves current session discoveries and context to Serena MCP # Automatically creates checkpoint if session exceeds 30 minutes ``` ### Comprehensive Session Checkpoint ``` /sc:save --type all --checkpoint # Complete session preservation with recovery checkpoint # Includes all learnings, context, and progress for session restoration ``` ### Session Summary Generation ``` /sc:save --summarize # Creates session summary with discovery documentation # Updates cross-session learning patterns and project insights ``` ### Discovery-Only Persistence ``` /sc:save --type learnings # Saves only new patterns and insights discovered during session # Updates project understanding without full session preservation ``` ## Boundaries **Will:** - Save session context using Serena MCP integration for cross-session persistence - Create automatic checkpoints based on session progress and task completion - Preserve discoveries and patterns for enhanced project understanding **Will Not:** - Operate without proper Serena MCP integration and memory access - Save session data without validation and integrity verification - Override existing session context without proper checkpoint preservation
© SuperClaude-Org · MIT · SuperClaude-Org/SuperClaude_Framework