Memory you can trust
RepoOps memory is a wiki where every claim carries a citation, a CI check, and a receipt. Six ways it compounds instead of resetting, for you, your team, and the community.
Why you can trust it
Proven, gated, and yours
On the synthetic accountability benchmark, RepoOps blocked all 12 recurrence attempts, because each fix becomes a standing rule. The fixture and results file are committed, so the number is auditable.
Everything a connector ingests is written as a proposal for review. Nothing external ever becomes active memory unread.
Your brain is plain files you own, readable from any MCP client, so the same memory follows you across tools and machines.
The six boxes
Descriptive, experiential, proactive, and how it compounds
Verified Memory
A generated wiki where every claim cites its source files, a strict CI gate checks those citations against HEAD on every commit, and each claim renders a memory receipt: source file, line, last-verified commit, CI timestamp. We run the same audit on our own brain in public, failing rows included, at repoops.ai/verified.
- Outcome: a page tells you it is fresh as of a specific commit, so you never trust a stale doc.
- Put it to work: open the Wiki tab and read the receipts before you rely on a page.
Experiential memory
Lessons, errors, decisions, and causal links, learned from what actually happened when your agents ran and enforced back into every agent session as pre-merge rules. No generator can produce this.
- Outcome: wire in the merge gate and a bug you fixed once is blocked if it tries to ship again.
- Put it to work: let RepoOps write the lesson; it reads on the next run automatically.
Proactive personal brain
Connectors can fill your personal brain on a schedule from email, docs, the web, X, and Slack, and session briefings deliver the relevant piece where you already work.
- Outcome: the context you need arrives at session start, ranked by what you have open.
- Put it to work: connect a source and set your priorities on the personal-brain page.
Lessons write back
The top-ranked fixes land in CLAUDE.md automatically, ordered by how many recurrences each has prevented and bounded so the manual stays readable, with the full set on the Lessons tab. A recurring fix becomes a proposed prevention rule. Your accumulated knowledge is plain files you own, not a database you rent.
- Outcome: the same mistake never costs you twice.
- Put it to work: keep your rules in the brain and let new sessions inherit them.
Team brain
Every member's lessons pool into one shared brain, each carrying the repo it came from and a count of how many teammates hit it. A new teammate starts with everything the team already learned, not a blank page.
- Outcome: onboarding a developer or a repo starts from the conventions your team already earned.
- Put it to work: share a slice, and the team wiki synthesizes cross-member topic pages from it.
Brain marketplace
Publish a brain template to the marketplace, or install one as a staged proposal you review and approve before it lands. Your hardest-won lessons become something the whole community can build on.
- Outcome: a new project starts from a proven setup instead of an empty CLAUDE.md.
- Put it to work: install a template to skip the cold start, or publish yours to help others.
Ready to start? Install RepoOps and your first lessons are captured on the first run. Connect a source and set priorities to grow the proactive side, and read the Wiki tab's verified badges to trust the descriptive side.