VerifiedState

Never re-explain your project to an agent.

Trusted State for coding agents — every agent starts from current intent, not a blank chat.

Capture local · Authority cloud — no mode menus

npx @verifiedstate/sync@latest init

Primary: npx @verifiedstate/sync · MCP: mcp.verifiedstate.ai/mcp · Correct/Now in dashboard · Start in 30s

verifiedstate.ai/dashboard — Now
Synced

Now

Updated 2m ago · demo project

Current goal
Ship Trusted State without a second history database.
View source →
What we're working on
Finish Search UI and Now briefing
2m ago · View source →
Important decisions
History is session_state-anchored; no messages table
Aug 9 · View source →
Private synthesis requires private model
Aug 2 · View source →
Constraints
Do not publish packages in this phase
Open loops
Capture enrichment for Cursor deferred
Authoritative current state

What agents inherit next. Correct anything wrong — human intent beats the last model.

Synced · working_state + corrections + decisions

History

Sessions across agents — open one to read the source

Today
Dashboard ops facelift
Claude Code · 14m ago · 24 turns
Activation banner collapsed
Cursor · 1h ago · 11 turns
Earlier
MAX_RETRIES policy session
Human corrected · Aug 10 · decision in thread
No second history database
Aug 9 · decision · Open session →
Real History is a conversation list you can open. Sign up to capture yours →

Correct

Fix conflicts and wrong state — human Correct is Trusted State

Conflict · current goal

Agent said: Continue from last commit

Observed: Ship Trusted State without a second history database

Correct → · Ignore · View source
Example after Correct

MAX_RETRIES=5 with linear delay

Agents inherit this. History keeps the old claim.
Correct is why this isn't chat memory. Try it on your project →

Search

Ask across History and decisions

why session_state instead of a messages table? Search
Answer
History is session_state-anchored so we don't maintain a second history database. Sources stay linked to the session that produced the decision.
Sources
Open session → · Aug 9 · decision
Search your own ledger after capture. Create account →

Agents

What is capturing Trusted State for you

Claude Code
Connected · full conversation capture · 2m ago
Cursor
Connected · activity + limited conversation · 1h ago
MCP
Idle · manual tool calls · advanced
Agents fill the ledger — Now + Correct + History are the product. Connect yours →

Integrations

How capture gets into your workspace

vsync init
One command — provisions access, MCP, capture
GitHub
Optional · link repos for context
Wire integrations after signup. Open Trusted State →

Account

Keys, billing, and team settings need a real workspace

Demo ends here. Sign up, run npx @verifiedstate/sync@latest init, then Correct anything wrong before the next agent runs.

Click the menu to see how it's used — demo data. Sign up for your project.

The product is authority — not a handoff tip.

Now, Correct, and History are Trusted State. Multi-agent tools are how you capture it.

Start Trusted State in your project.

Capture local · Authority cloud — Correct and Now stay in the dashboard.

npx @verifiedstate/sync@latest init