Integrations › Claude Code
Your CLAUDE.md decisions persist across sessions and sync to every connected tool.
Get API Key →Claude Code is powerful but stateless 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 sync to your other tools.
Context survives session resets.
Same project. Different day. Memory intact.
Run vsync or connect via MCP:
npx @verifiedstate/sync start
# That's it. Your CLAUDE.md syncs with .cursorrules automatically.
# Or connect via MCP:
claude mcp add verifiedstate --transport http https://mcp.verifiedstate.ai/mcp
# Add to CLAUDE.md:
# After every task, call session_save to persist context.{
"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
}| Feature | Without | With VerifiedState |
|---|---|---|
| Between sessions | Re-reads entire codebase | Loads verified context instantly |
| Architecture decisions | Lost when session ends | Persisted and synced to all tools |
| Contradictions | Agent contradicts yesterday's work | Conflicts detected automatically |
| CLAUDE.md | Manual, unversioned, local-only | Auto-synced to .cursorrules and every MCP tool |
It complements it. CLAUDE.md is static instructions. VerifiedState syncs those instructions to other tools and adds dynamic verified memory on top.
Under 100ms for full session context restore.
Any version that supports MCP servers.
No. vsync detects CLAUDE.md and .cursorrules in your project automatically. It just works.
Free: 50,000 assertions/month. No credit card. No trial expiration.