Your Dropbox for agent knowledge (it works without you having to "work" it or maintain it.) Every agent you use reads and writes to the same brain, and so do your teammates and theirs. Start a new chat and it can know what you've all already worked on. Your IP, research, sci-fi romance novel or notes are encrypted and I won't train on it. Export it to markdown and leave whenever, because I think you shouldn't have your knowledge locked in anywhere, including OzBrain.

We have a lot of different surfaces for my start up, and our whole team had individual patched their own silo'd solution together with their agent, github, slack, granola etc. Most founders I chat with I ask "what are you doing for a team brain/data lake?" and most have some sub optimal, stuck-together fix. So I've been looking for this exact thing, Ozbrain, for months. And my review after two weeks using it daily:
it does exactly what I need, it's slotted sleamlessly into my daily work flow, it's great. The versioning is really cool too, we take it for granted with code and git, but having it for company wide knowledge/data is great. Make so much sense.

It's truely MCP first, set up was a prompt and a few follow up questions in my agent, super simple.

I'd like a slack connector to run ozbrain queries in slack (like Claude Tag)

Our team had been using a frankenstein combo of github, google drive and shared skills. Ozbrain is way way better.

OzBrain is the third agent memory product that I've used and the one that I ultimately stuck with. The nice thing about OzBrain is that memory doesn't have to be overcomplicated. I find that simple is normally better when it comes to coding agents.

I just have instructions in my AGENTS.md that tell it to persist any decisions that were made in any design docs. From there, it has just continued to write and update any decisions made. It's very useful for iterating and experimenting, especially on AI pipelines where I'm tweaking the inputs and prompts a lot, then benchmarking against some output.

Memory should just be used when necessary and shouldn't drown the agent context. I find OzBrain with very simple setup already succeeds in both. I have not opened the UI. It just works.

Honestly, simple is better, so I feel that it doesn't need to be improved drastically. I'm already close to 20 articles, and I somehow find that Codex continues to find the correct article without me having to point it towards.

I think that the other tools in this space try to do some fancy stuff like indexing your code. These often produce graphs that are left stale. And I also find that they bloat context but don't provide as much value. On the other hand, OzBrain is much simpler in that I just need to tell it to remember something. It doesn't need to remember the technical implementation. I just use it as more of a fact ledger for things that I've tried before and decisions that I want to be committed to memory so that I don't fall into the same trap again. This is good enough to save me from having to check old git commits for much less tokens.

OzBrain

Your knowledge shared with every AI agent & any teammate

Your knowledge shared with every AI agent & any teammate

OzBrain Reviews

The community submitted 2 reviews to tell us what they like about OzBrain, what OzBrain can do better, and more.

What's great

What needs improvement

vs Alternatives

What's great

What needs improvement

vs Alternatives