Stop your AI from forgetting between sessions and tools. Shared, auto-updating memory across Claude Code, Cursor, and any MCP client.
npx @verifiedstate/sync initOne command. 30 seconds. Free for individuals.
You scaffold a backend with Claude Code. You switch to Cursor for the frontend.
Cursor has no idea what Claude just decided. You copy-paste context, manually update .cursorrules, and watch your AI rebuild things you already built.
Every developer using AI coding tools hits this daily.
In one command:
- Detects your repo and which AI tools you use (Claude Code, Cursor, Windsurf)
- Opens your browser for a one-click sign-in (no API keys to copy)
- Writes
CLAUDE.md,.cursor/rules/verifiedstate.mdc,AGENTS.md,.mcp.json - Starts a local daemon that captures every AI coding turn
- Generates a live hot-context file that updates as you work
After it finishes, every AI tool in your repo shares the same project memory. A decision in Claude Code shows up in Cursor's context within seconds. Open a new session — your AI already knows what you were doing.
vsync writes four files. You can see exactly what they look like in /examples before you run anything:
CLAUDE.md— current project state for Claude Code.cursor/rules/verifiedstate.mdc— persistent Cursor contextAGENTS.md— portable agent instructions (cross-tool standard).mcp.json— VerifiedState MCP server config
Don't want it anymore? npx @verifiedstate/sync eject removes everything cleanly.
A local daemon captures every Claude Code and Cursor turn as signed assertions in your VerifiedState memory. A hot-context worker regenerates the markdown files above on every state change. AI tools query the same backend via MCP, so a decision made in one tool is immediately available in another.
The memory substrate is cryptographically signed — every assertion is Ed25519-signed and hash-chained — so you have a verifiable record of what your AI did. That matters when the AI hallucinates or when you need to debug why it made a decision.
| Karpathy pack | Mem0 / Letta | Anthropic Memory | vsync | |
|---|---|---|---|---|
| One-command install | ✓ | ✓ | ||
| Auto-updates with project | ✓ | |||
| Cross-tool sync | ✓ | |||
| Cryptographic provenance | ✓ | |||
| Free for individuals | ✓ | limited | Claude only | ✓ |
The Karpathy pack made Claude behave better. vsync makes it remember — across tools.
Works alongside Anthropic's official MCP memory server. We're the cross-tool sync layer they don't provide.
Free — $0. For individual developers and personal projects. Everything in vsync with generous limits for solo work.
Pro — $19/month (founder pricing). For serious solo builders. Higher limits, multi-project workspaces, audit exports, commercial use. Pricing locked for 12 months for launch users. Join waitlist
Enterprise — Contact us. For teams, companies, and organizations. Multi-seat workspaces, SSO, SLA, audit exports, on-prem options, custom limits. Email hello@verifiedstate.ai
Free is for individual developers and personal use. Team, company, agency, or organizational use requires Enterprise — even when each developer installs separately.
vsync runs locally and only sends signed assertions to your VerifiedState account. Generated files are clearly marked and easy to remove. See SECURITY.md for details on what data leaves your machine and how it's protected.
- Website: verifiedstate.ai
- MCP server: mcp.verifiedstate.ai
- Dashboard: verifiedstate.ai/dashboard
- npm: @verifiedstate/sync
- Documentation: verifiedstate.ai/docs
MIT for this repo (CLI wrapper, templates, examples).
The hosted VerifiedState memory substrate is operated by VerifiedState. Free tier available for individual developers.