claude-session-continuity-mcp (v1.8.0)

Zero Re-explanation Session Continuity for Claude Code — Automatic context capture + semantic search

The Problem

Every new Claude Code session:

"This is a Next.js 15 project with App Router..."
"We decided to use Server Actions because..."
"Last time we were working on the auth system..."
"The build command is pnpm build..."

5 minutes of context-setting. Every. Single. Time.

The Solution

Fully automatic. Claude Hooks handle everything without manual calls:

# Session start → Auto-loads relevant context (Git-based semantic search)
# When asking → Auto-injects memories/solutions related to your query
# During conversation → Auto-captures important decisions/errors/learnings
# On commit → Commit messages automatically become memories

← Auto-output on session start:
# 🚀 my-app - Session Resumed

## Tech Stack
**framework**: Next.js, **language**: TypeScript

## Current State
📍 Implementing signup form
🚧 **Blocker**: OAuth callback URL issue

## 🧠 Relevant Memories (semantic: 0.89)
- 🎯 [decision] Decided on App Router, using Server Actions
- ⚠️ [error] OAuth redirect_uri mismatch → check env file
- 📚 [learning] Zod form validation gives automatic type inference

Zero manual work. Context follows you.

---

Quick Start

One Command Installation

npm install claude-session-continuity-mcp

That's it! The postinstall script automatically:

1. Registers MCP server in ~/.claude.json
2. Installs Claude Hooks in ~/.claude/settings.json

v1.6.1: Fixed critical bug where hooks were installed to wrong settings file. Now correctly installs to ~/.claude/settings.json. Auto-migrates existing users from settings.local.json.

What Gets Installed

MCP Server (in ~/.claude.json):

{
  "mcpServers": {
    "project-manager": {
      "command": "npx",
      "args": ["claude-session-continuity-mcp"]
    }
  }
}

Claude Hooks (in ~/.claude/settings.json):

{
  "hooks": {
    "SessionStart": [{ "hooks": [{ "type": "command", "command": "npm exec -- claude-hook-session-start" }] }],
    "UserPromptSubmit": [{ "hooks": [{ "type": "command", "command": "npm exec -- claude-hook-user-prompt" }] }],
    "PostToolUse": [{ "matcher": "Edit", "hooks": [{ "type": "command", "command": "npm exec -- claude-hook-post-tool" }] }, { "matcher": "Write", "hooks": [{ "type": "command", "command": "npm exec -- claude-hook-post-tool" }] }],
    "PreCompact": [{ "hooks": [{ "type": "command", "command": "npm exec -- claude-hook-pre-compact" }] }],
    "Stop": [{ "hooks": [{ "type": "command", "command": "npm exec -- claude-hook-session-end" }] }]
  }
}

Note (v1.5.0+): Full lifecycle coverage with 5 hooks. Uses npm exec -- which finds local node_modules/.bin first.

Installed Hooks (v1.5.0+)

Hook	Command	Function
SessionStart	claude-hook-session-start	Auto-loads project context on session start
UserPromptSubmit	claude-hook-user-prompt	Auto-injects relevant memories + past reference search
PostToolUse	claude-hook-post-tool	Tracks file changes (Edit, Write) automatically
PreCompact	claude-hook-pre-compact	Saves important context before compression
Stop	claude-hook-session-end	Auto-saves session on exit (no manual call needed)

Manual Hook Management

# Check hook status
npx claude-session-hooks status

# Reinstall hooks
npx claude-session-hooks install

# Remove hooks
npx claude-session-hooks uninstall

3. Restart Claude Code

After installation, restart Claude Code to activate the hooks.

---

Features

Feature	Description
🤖 Zero Manual Work	Claude Hooks automate all context capture/load
🎯 Query-Based Injection	Selectively inject only relevant memories/solutions
🧠 Semantic Search	multilingual-e5-small embedding (94+ languages, 384d)
🌍 Multilingual	Korean/English/Japanese + cross-language search (EN→KR, KR→EN)
🔗 Git Integration	Commit messages auto-memorized
🕸️ Knowledge Graph	Memory relations (solves, causes, extends...)
📊 Memory Classification	6 types: observation, decision, learning, error, pattern, code
✅ Integrated Verification	One-click build/test/lint execution
📋 Task Management	Priority-based task management
🔧 Solution Archive	Auto-search error solutions
📁 File Change Tracking	(v1.5.0) Auto-track Edit/Write tool usage
💾 Auto Backup	(v1.5.0) Daily SQLite backup (max 5)
🛡️ PreCompact Save	(v1.5.0) Save context before compression
🚪 Auto Session End	(v1.5.0) No manual session_end needed
🔍 Past Reference Detection	(v1.8.0) "저번에 X 어떻게 했어?" auto-searches DB
📝 User Directive Extraction	(v1.8.0) Auto-extracts "always/never" rules from prompts

---

Claude Hooks - Auto Context System

How It Works

SessionStart Hook (npx claude-hook-session-start):

• Auto-detects project: monorepo (apps/project-name/) or single project (package.json root folder name)
• Loads context from ~/.claude/sessions.db
• Injects: Tech stack, current state, pending tasks, recent memories

UserPromptSubmit Hook (npx claude-hook-user-prompt):

• Runs on every prompt submission
• Injects relevant context based on current project

Example Output (Session Start)

# 🚀 my-app - Session Resumed

## Tech Stack
**framework**: Next.js, **language**: TypeScript

## Current State
📍 Implementing signup form
🚧 **Blocker**: OAuth callback URL issue

## 📋 Pending Tasks
- 🔄 [P8] Implement form validation
- ⏳ [P5] Add error handling

## 🧠 Key Memories
- 🎯 [decision] Decided on App Router, using Server Actions
- ⚠️ [error] OAuth redirect_uri mismatch → check env file

Hook Management

# Check status
npx claude-session-hooks status

# Reinstall
npx claude-session-hooks install

# Remove
npx claude-session-hooks uninstall

# Temporarily disable
export MCP_HOOKS_DISABLED=true

Past Reference Detection (v1.8.0)

When you ask about past work, the UserPromptSubmit hook automatically searches the database:

You: "저번에 인앱결제 어떻게 했어?"
→ Hook detects "저번에" + extracts keyword "인앱결제"
→ Searches sessions, memories (FTS5), and solutions
→ Injects matching results into context automatically

Supported patterns (Korean & English):

Pattern	Example
저번에/전에/이전에 ... 어떻게	"저번에 CORS 에러 어떻게 해결했지?"
~했던/만들었던/해결했던	"수정했던 로그인 로직"
지난 세션/작업에서	"지난 세션에서 결제 구현"
last time/before/previously	"How did we handle auth last time?"
did we/did I ... before	"Did we fix the database migration before?"
remember when/recall when	"Remember when we set up CI?"

Output example:

## Related Past Work (auto-detected from your question)

### Sessions
- [2/14] 카카오 로그인 앱키 수정, 인앱결제 IAP 플로우 수정

### Memories
- 🎯 [decision] 테스트: 인앱결제 상품 등록 완료

### Solutions
- **IAP_BILLING_ERROR**: StoreKit 2 migration으로 해결

Why npm exec? (v1.4.3+)

Previous versions used absolute paths or npx:

// v1.3.x - absolute paths (broke on multi-project)
"command": "node \"/path/to/project-a/node_modules/.../session-start.js\""

// v1.4.0-1.4.2 - npx (required global install or hit npm registry)
"command": "npx claude-hook-session-start"

Now we use npm exec --:

"command": "npm exec -- claude-hook-session-start"

npm exec -- finds local node_modules/.bin first, then falls back to global. Works with both local and global installation without hitting npm registry.

---

Tools (v5 API) - 24 Focused Tools

1. Session Lifecycle (4) ⭐

// Start of session - auto-loads context
session_start({ project: "my-app", compact: true })

// End of session - auto-saves context
session_end({
  project: "my-app",
  summary: "Completed auth flow",
  modifiedFiles: ["src/auth.ts", "src/login/page.tsx"]
})

// View session history
session_history({ project: "my-app", limit: 5 })

// Semantic search past sessions
search_sessions({ query: "auth work", project: "my-app" })

2. Project Management (4)

// Get project status with task stats
project_status({ project: "my-app" })

// Initialize new project
project_init({ project: "my-app" })

// Analyze project tech stack
project_analyze({ project: "my-app" })

// List all projects
list_projects()

3. Task Management (4)

// Add a task
task_add({ project: "my-app", title: "Implement signup", priority: 8 })

// Update task status
task_update({ taskId: 1, status: "done" })

// List tasks
task_list({ project: "my-app", status: "pending" })

// Suggest tasks from TODO comments
task_suggest({ project: "my-app" })

4. Solution Archive (3)

// Record an error solution
solution_record({
  errorSignature: "TypeError: Cannot read property 'id'",
  solution: "Use optional chaining: user?.id"
})

// Find similar solutions (keyword or semantic)
solution_find({ query: "TypeError property", semantic: true })

// AI-powered solution suggestion
solution_suggest({ errorMessage: "Cannot read property 'email'" })

5. Verification (3)

// Run build
verify_build({ project: "my-app" })

// Run tests
verify_test({ project: "my-app" })

// Run all (build + test + lint)
verify_all({ project: "my-app" })

6. Memory System (4)

// Store a classified memory
memory_store({
  content: "State management with Riverpod makes testing easier",
  type: "learning",  // observation, decision, learning, error, pattern
  project: "my-app",
  tags: ["flutter", "state-management"],
  importance: 8,
  relatedTo: 23  // Connect to existing memory
})

// Search memories (keyword or semantic)
memory_search({
  query: "state management test",
  type: "learning",
  semantic: true,  // Use embedding similarity
  limit: 10
})

// Find related memories (graph + semantic)
memory_related({
  memoryId: 23,
  includeGraph: true,
  includeSemantic: true
})

// Get memory statistics
memory_stats({ project: "my-app" })

7. Knowledge Graph (2)

// Connect two memories with a typed relation
graph_connect({
  sourceId: 23,
  targetId: 25,
  relation: "solves",  // related_to, causes, solves, depends_on, contradicts, extends, example_of
  strength: 0.9
})

// Explore knowledge graph
graph_explore({
  memoryId: 23,
  depth: 2,
  relation: "all",  // or specific relation type
  direction: "both"  // outgoing, incoming, both
})

Memory Types

Type	Description	Use Case
observation	Patterns, structures found in codebase	"All screens are separated in features/ folder"
decision	Architecture, library choices	"Decided to use SharedPreferences for caching"
learning	New knowledge, best practices	"Riverpod is better for testing"
error	Occurred errors and solutions	"Provider.read() doesn't rebuild → use watch()"
pattern	Recurring code patterns, conventions	"Avoid late keyword abuse"

Relation Types

Relation	Description	Example
related_to	General relation	A and B are related
causes	A causes B	Caching decision → folder structure change
solves	A solves B	Riverpod learning → Provider bug fix
depends_on	A depends on B	Folder structure → Caching decision
contradicts	A conflicts with B	Two design decisions conflict
extends	A extends B	late pattern → Extended to Riverpod learning
example_of	A is example of B	Specific code is example of pattern

---

Data Storage

SQLite database at ~/.claude/sessions.db:

Table	Purpose
memories	Classified memories (observation, decision, learning, error, pattern)
memories_fts	Full-text search index (FTS5)
memory_relations	Knowledge graph relations
embeddings_v4	Semantic search vectors (multilingual-e5-small, 384d)
project_context	Fixed project info (tech stack, decisions)
active_context	Current work state
tasks	Task backlog
solutions	Error solution archive
sessions	Session history

---

Environment Variables

Variable	Default	Description
WORKSPACE_ROOT	-	Workspace root path (required)
MCP_HOOKS_DISABLED	false	Disable Claude Hooks
LOG_LEVEL	info	Log level (debug/info/warn/error)
LOG_FILE	-	Optional file logging path

---

Development

# Clone
git clone https://github.com/leesgit/claude-session-continuity-mcp.git
cd claude-session-continuity-mcp

# Install
npm install

# Build
npm run build

# Test
npm test

# Test with coverage
npm run test:coverage

---

Performance

Metric	Value
Context load (cached)	<5ms
Memory search (FTS)	~10ms
Semantic search	~50ms
Build verification	Project-dependent

---

Roadmap

• v2 API (15 focused tools)
• v4 API (24 tools - memory + graph)
• v5 Claude Hooks (auto-capture)
• Knowledge Graph with typed relations
• Memory classification (6 types)
• Semantic search (embeddings)
• Multilingual pattern detection (KO/EN/JA)
• Git commit integration
• 111 tests (6 test suites)
• GitHub Actions CI/CD
• Multilingual semantic search (v1.6.0 - multilingual-e5-small)
• Cross-language search EN↔KR (v1.6.0)
• Solution semantic search (v1.6.0)
• Fix hooks settings file path (v1.6.1 - settings.json, not settings.local.json)
• Auto-migrate legacy hooks (v1.6.1)
• Fix PostToolUse matcher format to string (v1.6.3)
• Fix README documentation for new hook format (v1.6.4)
• Empty session skip and techStack save improvements (v1.7.1)
• Past reference auto-detection in UserPromptSubmit hook (v1.8.0)
• User directive extraction ("always/never" rules) (v1.8.0)
• sqlite-vec native vector search (v2 - when data > 1000 records)
• Web dashboard
• Cloud sync option

---

Contributing

PRs welcome! Please:

1. Fork the repo
2. Create a feature branch
3. Add tests for new features
4. Ensure npm test passes
5. Submit PR

---

License

MIT © Byeongchang Lee

---

Acknowledgments

• Model Context Protocol by Anthropic
• Xenova Transformers for embeddings