Claude Code Continuity
Persistent project state and History & Sources for every Claude Code session.
Two ways to connect
VerifiedState integrates with Claude Code through two complementary channels: the MCP server for direct tool access, and the vsync daemon for automatic background capture.
1. MCP server connection
Add VerifiedState as an MCP server so Claude Code can call memory tools directly:
claude mcp add verifiedstate \
--transport http \
--url https://mcp.verifiedstate.ai/mcp \
--header "Authorization: Bearer YOUR_API_KEY" \
--header "X-Namespace-ID: YOUR_NAMESPACE_ID"
This gives Claude Code access to 23 tools: memory_ingest, memory_query, session_save, session_load, and more. Claude can save and load session state, query past decisions, and verify assertions directly.
2. vsync daemon (automatic capture)
The vsync daemon watches Claude Code sessions in the background and captures every turn automatically. Capture is local-first (~/.vsync/queue), then syncs to cloud; Correct and team Now stay cloud authority — not a separate local mode.
npx @verifiedstate/sync init # one-time setup
vsync start # start daemon
vsync inspect # queue depth + hot-context trust
vsync check # safety verdict
vsync last # what happened last session
The daemon monitors ~/.claude/projects/ for session activity, captures conversation turns, extracts assertions, and links git commits to the sessions that produced them. Coding signals (active file, idle, commit) push into working state so dashboard/MCP Now can show them.
CLAUDE.md session protocol
Add session continuity instructions to your CLAUDE.md so Claude Code automatically loads and saves state:
# Session continuity
At the start of every session:
1. Call session_load with project = "your-project"
2. Read the returned state as starting context
At the end of every session:
1. Call session_save with summary, files_changed,
decisions, next_steps, blockers
2. Confirm the save succeeded
With this protocol, a fresh Claude Code session picks up exactly where the last one left off -- decisions, progress, and open questions all preserved.
What gets captured
- Full text of every session turn (human + assistant)
- Tool calls and their results
- Git commits made during the session
- File changes linked to the conversation that caused them
- Extracted decisions as signed SPO triples
Get your API key and start in 30 seconds
Get Free API Key