Claude Context Sync

What is Claude Context Sync?

Claude Context Sync is an MCP server that automatically summarizes and shares context across parallel Claude Code sessions. It watches session logs, generates structured summaries on demand, and provides real-time file conflict detection and cross-session messaging for developers running multiple Claude Code sessions simultaneously.

How to use Claude Context Sync?

Install globally with npm install -g claude-context-sync then run context-sync init. The MCP server starts automatically the next time you open Claude Code, and the init command registers a conflict detection hook. Four tools are available: list_sessions, get_session_context, get_all_changes, send_message, get_messages, and resolve_conflicts.

Key features of Claude Context Sync

• Session context sharing across parallel Claude Code sessions
• Real-time file conflict detection with symbol-level accuracy
• Cross-session messaging between terminals without switching
• Lazy evaluation with zero cost when tools aren't called
• Auto-cleanup of tracked data when sessions end
• Symbol-level detection for TypeScript, Python, Swift, Go, and Rust

Use cases of Claude Context Sync

• Working on multiple features simultaneously with full context awareness
• Preventing file conflicts when multiple sessions edit the same codebase
• Sending messages between sessions without leaving the terminal
• Getting a bird's-eye view of all active Claude Code sessions and their changes

FAQ from Claude Context Sync

How does Claude Context Sync share context between sessions?

It watches your session logs for changes, marks sessions as stale at zero cost, and when a tool is called it summarizes only stale sessions by parsing .jsonl files and generating structured summaries using claude -p.

What languages are supported for symbol-level conflict detection?

TypeScript/JavaScript, Python, Swift, Go, and Rust. Unsupported file types fall back to file-level conflict detection only.

Does Claude Context Sync require a separate daemon process?

No. It runs as a single MCP server process that Claude Code launches automatically via stdio transport with no separate daemon.

Where is session data stored and when is it cleaned up?

Data is stored locally in ~/.claude/context-sync/ and tracked data is automatically removed when sessions end.

What are the runtime requirements?

Node.js 20+, the Claude Code CLI (claude command available), and jq for the conflict detection hook.