context-save — Claude Code command: keep project context between sessions
A slash command that writes down the project state and the decisions behind it, so the next agent session picks up where the last one stopped.
/plugin marketplace add wshobson/agents
/plugin install context-management@claude-code-workflowsWhat context-save does
The command takes a snapshot: project layout, architecture choices with their reasoning, a dependency graph and semantic tags. Everything lands in a file that the agent can reload later.
You pass the project root, how much to capture (minimal, standard, comprehensive), the storage format (json, markdown, vector) and optional tags. Vector storage means an outside database such as Pinecone, Weaviate or Qdrant, which is extra setup you can skip. The description warns about two things: sensitive material has to be left out by hand, and capture costs compute time.
It arrives through the wshobson/agents marketplace as part of the context-management bundle. Snapshots can be versioned, so you get to diff context across sessions and notice when the project has drifted.
What it helps with
- record an architecture choice along with the reason for it
- get back into a project after a week away without rereading everything
- hand the current state to another agent or teammate
- compare context before and after a large refactor
- compress accumulated project notes into one readable file
Example prompts for the agent
- Save the project context to
.context/state.mdat standard depth - Take a snapshot with the tags
authandrefactor - Write today's architecture decisions into a markdown file
How to install context-save
1Plugin marketplace
/plugin marketplace add wshobson/agents/plugin install context-management@claude-code-workflows2Manually: put the files in place
.claude/commands/context-save.mdCall it with /context-save. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/context-save.mdCall it with /prompts:context-save. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/context-save.prompt.mdManually: put the files in place
.gemini/commands/context-save.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about context-save
How do I install context-save in Claude Code?
Add the marketplace first with /plugin marketplace add wshobson/agents, then run /plugin install context-management@claude-code-workflows. The command file appears at .claude/commands/context-save.md.
What does context-save do?
It captures project layout, architecture decisions and their rationale, dependencies and tags, then writes them to a file the agent reads in a later session.
Which storage formats can it write?
Structured JSON, markdown with frontmatter, Protocol Buffers, MessagePack and annotated YAML. The vector option needs an external store like Pinecone, Weaviate or Qdrant.
Source text
context-save.md · MIT
---
description: Save project context, decisions, and progress for a later session
---
# Context Save Tool: Intelligent Context Management Specialist
## Role and Purpose
An elite context engineering specialist focused on comprehensive, semantic, and dynamically adaptable context preservation across AI workflows. This tool orchestrates advanced context capture, serialization, and retrieval strategies to maintain institutional knowledge and enable seamless multi-session collaboration.
## Context Management Overview
The Context Save Tool is a sophisticated context engineering solution designed to:
- Capture comprehensive project state and knowledge
- Enable semantic context retrieval
- Support multi-agent workflow coordination
- Preserve architectural decisions and project evolution
- Facilitate intelligent knowledge transfer
## Requirements and Argument Handling
### Input Parameters
- `$PROJECT_ROOT`: Absolute path to project root
- `$CONTEXT_TYPE`: Granularity of context capture (minimal, standard, comprehensive)
- `$STORAGE_FORMAT`: Preferred storage format (json, markdown, vector)
- `$TAGS`: Optional semantic tags for context categorization
## Context Extraction Strategies
### 1. Semantic Information Identification
- Extract high-level architectural patterns
- Capture decision-making rationales
- Identify cross-cutting concerns and dependencies
- Map implicit knowledge structures
### 2. State Serialization Patterns
- Use JSON Schema for structured representation
- Support nested, hierarchical context models
- Implement type-safe serialization
- Enable lossless context reconstruction
### 3. Multi-Session Context Management
- Generate unique context fingerprints
- Support version control for context artifacts
- Implement context drift detection
- Create semantic diff capabilities
### 4. Context Compression Techniques
- Use advanced compression algorithms
- Support lossy and lossless compression modes
- Implement semantic token reduction
- Optimize storage efficiency
### 5. Vector Database Integration
Supported Vector Databases:
- Pinecone
- Weaviate
- Qdrant
Integration Features:
- Semantic embedding generation
- Vector index construction
- Similarity-based context retrieval
- Multi-dimensional knowledge mapping
### 6. Knowledge Graph Construction
- Extract relational metadata
- Create ontological representations
- Support cross-domain knowledge linking
- Enable inference-based context expansion
### 7. Storage Format Selection
Supported Formats:
- Structured JSON
- Markdown with frontmatter
- Protocol Buffers
- MessagePack
- YAML with semantic annotations
## Code Examples
### 1. Context Extraction
```python
def extract_project_context(project_root, context_type='standard'):
context = {
'project_metadata': extract_project_metadata(project_root),
'architectural_decisions': analyze_architecture(project_root),
'dependency_graph': build_dependency_graph(project_root),
'semantic_tags': generate_semantic_tags(project_root)
}
return context
```
### 2. State Serialization Schema
```json
{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"properties": {
"project_name": { "type": "string" },
"version": { "type": "string" },
"context_fingerprint": { "type": "string" },
"captured_at": { "type": "string", "format": "date-time" },
"architectural_decisions": {
"type": "array",
"items": {
"type": "object",
"properties": {
"decision_type": { "type": "string" },
"rationale": { "type": "string" },
"impact_score": { "type": "number" }
}
}
}
}
}
```
### 3. Context Compression Algorithm
```python
def compress_context(context, compression_level='standard'):
strategies = {
'minimal': remove_redundant_tokens,
'standard': semantic_compression,
'comprehensive': advanced_vector_compression
}
compressor = strategies.get(compression_level, semantic_compression)
return compressor(context)
```
## Reference Workflows
### Workflow 1: Project Onboarding Context Capture
1. Analyze project structure
2. Extract architectural decisions
3. Generate semantic embeddings
4. Store in vector database
5. Create markdown summary
### Workflow 2: Long-Running Session Context Management
1. Periodically capture context snapshots
2. Detect significant architectural changes
3. Version and archive context
4. Enable selective context restoration
## Advanced Integration Capabilities
- Real-time context synchronization
- Cross-platform context portability
- Compliance with enterprise knowledge management standards
- Support for multi-modal context representation
## Limitations and Considerations
- Sensitive information must be explicitly excluded
- Context capture has computational overhead
- Requires careful configuration for optimal performance
## Future Roadmap
- Improved ML-driven context compression
- Enhanced cross-domain knowledge transfer
- Real-time collaborative context editing
- Predictive context recommendation systems
© Seth Hobson · MIT · wshobson/agents