Our review
Provides persistent working memory for coding sessions by automatically tracking goals, decisions, progress, and open questions in per-repo state files.
Strengths
- Automatically captures session context without manual effort
- Structured JSON files allow precise queries via jq
- Maintains a decision log with rationale for future reference
- Supports resuming work after interruptions with full context
Limitations
- Only works with Claude Code's hook system
- Relies on hooks firing correctly (e.g., SessionStart, PreCompact)
- May add minor overhead on session boundaries
Use when working on complex, multi-session projects where maintaining context and rationale is critical.
Avoid for trivial one-off tasks or when privacy concerns require minimal file persistence.
Security analysis
SafeThis skill only reads and writes to local files under `.claude/voyager/` for session tracking; no destructive commands, no network access, no exfiltration. Uses jq for safe JSON querying. No instructions to execute arbitrary code or disable safety.
No concerns found
Examples
resume where we left offremember this decision: we switched from REST to GraphQL because it reduces over-fetchingwhat's next?name: session-brain description: | Persistent working memory for coding sessions. Automatically tracks what you're doing, why you're doing it, decisions made, and what's next.
Trigger phrases:
- "resume where we left off"
- "what were we doing?"
- "recap this repo" / "catch me up"
- "remember this decision: ..."
- "why did we decide to ..." / "what was the rationale for ..."
- "what's next?" / "what should I work on?"
- "what are the open questions?"
- "save this as a project rule" allowed-tools:
- Read
- Write
- Grep
- Glob
- Bash
Session Brain
Persistent per-repo working memory stored under .claude/voyager/.
State Files
| File | Purpose |
|------|---------|
| brain.json | Canonical structured state (validated against schema) |
| brain.md | Human-readable summary for quick reference |
| episodes/ | Per-session summaries for history |
How It Works
Session Brain updates automatically via hooks:
- SessionStart: Injects current brain context + repo snapshot
- PreCompact/SessionEnd: Persists changes to brain.json and creates episode
You don't need to manually update the brain—just work normally and it tracks context.
Reading brain.json
When exploring brain.json, use jq to query specific sections instead of reading the whole file:
# Current context (goal, plan, questions)
jq '.working_set' .claude/voyager/brain.json
# Decision history
jq '.decisions' .claude/voyager/brain.json
# Recent progress
jq '.progress' .claude/voyager/brain.json
# Project overview
jq '.project' .claude/voyager/brain.json
For a quick human-readable summary, read .claude/voyager/brain.md instead.
Answering User Questions
When users ask about context, read and interpret the brain files:
"Resume" / "What were we doing?"
- Read
.claude/voyager/brain.mdfor quick context - Check
brain.json→working_set.current_goalandworking_set.current_plan - Summarize: current goal, plan progress, any open questions
"What's next?"
- Read
brain.json→working_set.current_plan - Check
progress.recent_changesto see what's done - Suggest the next uncompleted step from the plan
"Why did we decide X?" / "What was the rationale?"
- Read
brain.json→decisionsarray - Find matching decision by keyword
- Return the
rationaleandimplications
"What are the open questions?"
- Read
brain.json→working_set.open_questions - Also check
working_set.risksfor blockers
Recording Decisions
When the user says "remember this decision: ..." or explicitly wants to record a decision:
- Read current
.claude/voyager/brain.json - Append to the
decisionsarray:{ "when": "<ISO timestamp>", "decision": "<what was decided>", "rationale": "<why>", "implications": ["<what this affects>"] } - Write updated
brain.json
Note: brain.md will be re-rendered automatically on the next session end or compaction.
Brain Schema Overview
See schemas/brain.schema.json for full schema. Key sections:
- project: Stable project understanding (summary, stack, key commands)
- working_set: Current context (goal, plan, open questions, risks)
- decisions: Append-only decision log with rationale
- progress: Recent changes and completed milestones
- signals: Metadata (last session ID, timestamp)
Technical Details
See reference.md for:
- Full file structure
- Update flow details
- Manual operations (reset, view history)
- Graceful degradation behavior
Task Prioritizer
Productivity
Prioritizes your tasks using Eisenhower, ICE, and RICE frameworks.
Weekly Status Report Generator
Productivity
Generate structured and concise weekly status reports.
Daily Standup Report
Productivity
Generates structured and concise daily standup reports.