Integrations › Claude Code

AI Code Editor

Install VerifiedState — Claude Code Never Starts From Zero

Trusted State for Claude Code: richest conversation capture + handoff to Cursor.

Get API Key →
12MCP tools
0.01mslookup
Freefor individuals
ed25519signed

The Problem

Claude Code is powerful but loses continuity between sessions. It re-reads your codebase every time. It doesn't remember your preferences, your architecture decisions, or the bugs it already fixed. CLAUDE.md helps, but it's manual, unversioned, and doesn't hand off to your other tools.

Context survives session resets.

• • • Session 1
> Use Tailwind, not custom CSS
✓ Stored · rct_f92e · 0.98
• • • Session 2 (next day)
> How should I style this component?
✦ Loading session context...
Use Tailwind — decided yesterday.
Receipt: rct_f92e · still valid

Same project. Different day. Memory intact.

Step 1
Connect
→
Step 2
Ingest + Extract
→
Step 3
Verify + Receipt

The Fix

Connect my first agentReturns here after auth · then run vsync init

One command — recommended:

bash
npx @verifiedstate/sync init # Anonymous key + MCP + daemon capture + hot-context. # Claim a durable account later: vsync claim # Capture: Claude JSONL (full conversation when available) # Retrieval: hot-context auto-refresh + MCP session_load (agent protocol) # Advanced MCP-only: claude mcp add verifiedstate --transport http \ https://mcp.verifiedstate.ai/mcp

What You Get Back

✓ VERIFIED
receipt.json
{ "receipt_id": "rct_7f3a...", "assertion": "User prefers dark mode", "status": "verified", "confidence": 0.94, "signature": "ed25519:a8c3f1...", "verified_at": "2026-04-06T14:32:01Z", "chain_position": 42 }

Without VerifiedState vs. With VerifiedState

FeatureWithoutWith VerifiedState
Between sessions Re-reads entire codebase Loads verified context instantly
Architecture decisions Lost when session ends Persisted and available to connected agents
Contradictions Agent contradicts yesterday's work Conflicts detected automatically
Capture quality Nothing persisted Full conversation when Claude capture is rich

FAQ

Does this replace CLAUDE.md?

It complements it. vsync manages a VerifiedState section in CLAUDE.md and syncs hot-context. Your own CLAUDE.md content is preserved.

Do I need to keep the dashboard open?

No. Install once, work normally. Open VerifiedState when you need History, Search, Now, or Review.

Which Claude Code version?

Any version that supports MCP servers.

Do I need to configure anything after npx?

Usually no. Run init in the project, then keep working. Verify with vsync status.

Related Integrations

Never explain your project twice.

Add VerifiedState once. Keep project state available across your AI agents.