Shared AI memory that stops agents from repeating mistakes
RoBrain is open-source shared memory for teams using AI agents. It captures every decision and the alternatives you ruled out — automatically, across every developer's sessions — and flags when a new decision contradicts an old one. Your team revisits past decisions intentionally, with the original rationale in front of them, instead of re-litigating from zero. Works across Claude Code, Cursor, and Copilot.
Hey Product Hunt 👋 I built RoBrain because I kept watching my AI agent re-suggest things my team had already ruled out. Every new session, a clean slate — and a clean slate means re-litigating decisions we'd already made. The fix everyone reaches for is CLAUDE.md (or its equivalent for other agents). It works for a week, then drifts. Nobody updates it. Claude Code's Auto-Memory writes notes automatically now, but they live on your laptop — your teammates' agents have no idea what you decided. And critically — none of these capture the vetoes. The reasons something was rejected. That's the part that matters most when an agent suggests the same idea three months later. RoBrain captures decisions as structured data, including what was rejected and why: json{ "decision": "Use Zustand for state management", "rationale": "Redux caused re-render issues in cart", "rejected": [{ "option": "Redux", "reason": "re-render perf issues in cart" }], "files_affected": ["src/store/cart.ts"] } Every developer's sessions feed one shared decision history. Next time your teammate's agent suggests Redux, RoBrain surfaces the prior rejection with the original rationale — so your team revisits intentionally instead of from zero.
About RoBrain on Product Hunt
“Shared AI memory that stops agents from repeating mistakes”
RoBrain launched on Product Hunt on May 14th, 2026 and earned 65 upvotes and 7 comments, placing #47 on the daily leaderboard. RoBrain is open-source shared memory for teams using AI agents. It captures every decision and the alternatives you ruled out — automatically, across every developer's sessions — and flags when a new decision contradicts an old one. Your team revisits past decisions intentionally, with the original rationale in front of them, instead of re-litigating from zero. Works across Claude Code, Cursor, and Copilot.
On the analytics side, RoBrain competes within Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1M followers on Product Hunt. The dashboard above tracks how RoBrain performed against the three products that launched closest to it on the same day.
Who hunted RoBrain?
RoBrain was hunted by Adelina Martiniuc. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of RoBrain including community comment highlights and product details, visit the product overview.
Adelina Martiniuc
Hey Product Hunt 👋
I built RoBrain because I kept watching my AI agent re-suggest things my team had already ruled out. Every new session, a clean slate — and a clean slate means re-litigating decisions we'd already made.
The fix everyone reaches for is CLAUDE.md (or its equivalent for other agents). It works for a week, then drifts. Nobody updates it. Claude Code's Auto-Memory writes notes automatically now, but they live on your laptop — your teammates' agents have no idea what you decided.
And critically — none of these capture the vetoes. The reasons something was rejected. That's the part that matters most when an agent suggests the same idea three months later.
RoBrain captures decisions as structured data, including what was rejected and why:
json{
"decision": "Use Zustand for state management",
"rationale": "Redux caused re-render issues in cart",
"rejected": [{ "option": "Redux", "reason": "re-render perf issues in cart" }],
"files_affected": ["src/store/cart.ts"]
}
Every developer's sessions feed one shared decision history. Next time your teammate's agent suggests Redux, RoBrain surfaces the prior rejection with the original rationale — so your team revisits intentionally instead of from zero.