How do I keep multiple AI agents working from the same docs?
Give every agent one shared point to both read and write, instead of separate copies each maintains. When one agent records what it learns through a single store, every other agent and teammate reads that record back instead of re-deriving it. With one point of passage for reads and writes there are no copies to drift and nothing to sync — a single source of truth by construction.
Why do agents drift apart?
Because each one builds its own private context. Agent A figures out the rollback steps; Agent B, in another session, re-derives them from scratch; a teammate's agent reads an older doc and contradicts both. There's no shared memory, so the same work is repeated and the answers diverge. Static files like a hand-maintained CLAUDE.md don't fix this — they're one more copy to keep current by hand.
What does a shared source of truth need?
- One read path. Every agent asks the same store and gets the same canonical answer, with a freshness marker.
- One write path. When an agent learns something, it records it once, in the same store the others read.
- No sync step. Because reads and writes pass through one point, there are no copies to reconcile.
How trovex does it
trovex is an open-source, local-first MCP server with exactly this shared write path. Agents record incidents, decisions, and notes through it, and every other agent — and your teammates — read them back as canonical, current docs. It runs on your machine (SQLite + ONNX, no cloud or keys). Keeping a fleet of agents working from one source of truth at scale is also where many teams want a hand — see trovex.dev.
One source of truth for your whole fleet.
Point trovex at your repo and let every agent read and write through one store.
Open source. No cloud, no API keys. Your docs never leave your machine.