Decisions made in Cursor don't disappear when someone opens Claude Code. VerifiedState gives your team and every agent one shared Trusted State.
Developer A tells Cursor to use Supabase for auth. Developer B asks Claude Code to build the login page. Claude Code writes Firebase because it doesn't know about Developer A's decision.
Your agents work in silos. Your team pays the price.
Five steps. Two minutes. Then it just works.
When a team member stores a decision, it's written to your team workspace. Connected agents (Claude Code, Cursor, MCP clients) can retrieve that state via hot-context and MCP tools such as session_load — retrieval is available, but host agents must follow the continuity protocol (not guaranteed silent auto-injection in every IDE).
Yes. One developer can use Cursor, another Claude Code — as long as they're connected to the same VerifiedState workspace. Best-supported pair today is Claude Code ↔ Cursor. State is kept available; agents retrieve it via vsync hot-context and/or MCP.
Completely. Your personal namespace is private — only you can read and write to it. Team memory lives in a shared namespace that all team members can access. You control what goes where.
Create a team in the dashboard, click Invite, and share the link. After they join and connect an agent (vsync init / MCP), they can retrieve shared workspace state. Join alone does not magically reconfigure every IDE.
Free tier: 50,000 assertions/month. No credit card. No trial expiration.