When to Use VerifiedState
The right tool for the right problem.
Install vsync when you...
- Use AI coding agents (Claude Code, Cursor, Windsurf) and want to know what they actually did across sessions
- Work solo with multiple AI tools and need decisions made in one tool to be visible in another
- Lead a team where multiple developers use AI agents and you need shared History & Sources of what changed and why
- Need compliance evidence that AI-assisted changes were reviewed, attributed, and traceable
- Lose context between sessions -- your AI keeps re-asking questions it already answered yesterday
Do NOT use vsync when you...
- Don't use AI coding agents. vsync captures agent sessions. If you only use a text editor, there is nothing to capture.
- Need a generic vector database. VerifiedState uses pgvector internally but the product is a signed assertion ledger, not similarity search.
- Want a personal knowledge base. This is not a note-taking app. It stores structured, verified, attributed claims about what happened during agent work.
- Need RAG for document Q&A. VerifiedState is Trusted State with History & Sources (advanced integrity available), not a retrieval-augmented generation pipeline.
vsync vs git vs memory tools
Git tracks file snapshots. It tells you what changed in code. It does not tell you which agent session produced the change, what reasoning led to it, or what decisions were considered and rejected.
vsync tracks the agent sessions that produced those git commits. It links every file change to the conversation that caused it, with actor attribution and signed receipts. Capture is local-first (~/.vsync/queue; vsync inspect); Correct and team Now stay cloud authority — not a separate local/cloud mode product.
Memory tools (ChatGPT memory, Claude memory) store preferences and facts for a single tool. They don't share across tools, don't sign anything, and don't provide shared History & Sources. vsync captures from all your tools into one Trusted State ledger.
See it in action
Claude Code Setup