OzBrain

Almost all of this is stuff I have indeed "frankenstein[ed]" for myself, so consider this comment a +1 on market fit, there! That also gives me a reason to pause, tho; the pitch in general is as solid as it can be on a site with markdown turned off (why, lord, why), but as a format minutiae megafan, I was left a little dissapointed. Where do you/OzBrain stand on Markdown formats? Could I use Sphinx with this, in rST and/or native MyST? Can it generate plain PDFs, fancy PDFs, or even animated static sites? etc. etc. etc. Not trying to gotcha, just curious to hear your thoughts & dreams on the topic! It seems like some subculture(s) of SWE/SV/YC/AI has landed on obsidian-ish markdown with lots of wikilinks as the presumed default, which makes sense. So I'm assuming it's the same here. But also, your 'OzBrain vs. Obsidian' page does describe one difference as 'Markdown export anytime' vs. 'Markdown on disk' -- presumably that's just a hedge about hosting paradigm rather than a comment on the persistent format? P.S. You're likely aware but there's at least one other company using Oz -- Warp's coding agent. Have you considered renaming this to something unimpeachable like DeepReasoningBrain? ;) P.P.S. Holy hell your `eng-flow` thing is incredible. Maybe I'm behind the times, but... I mean, has anyone else processed how close we are to Minority Report and Iron Man?! P.P.P.S. Is any part of that/this OS?

bbor · Imported from Show HN

I’m not sure I get the value over Obsidian, can you explain the static file issue? Only happens at 7K+ individual files? What happens if you always conjoin files?

gosolozero · Imported from Show HN

Do you have a solution for degradation in accuracy when compiling larger amounts of llm-produced text? I am also building LLM knowledge/memory systems and I've been surprised how bad LLMs are, even SOTA models, at summarizing non-trivial input batches of text. They get things wrong, distort the underlying meaning or data, etc.

gavinboston · Imported from Show HN

This is a fascinating place in the stack to sit. I need to dig in a lot more. Nice start. Good luck with the showing!

cyrusradfar · Imported from Show HN

This is interesting. Would you consider this a different type product/benefit than all the "memory" things we have seen popping up everywhere?. Is it different just because it lives in the cloud? To me it feels like a different thing than memory.

indigodaddy · Imported from Show HN

5.00 from 2 Product Hunt reviews

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.

gthartley · Review on Product Hunt

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.

kvnkho · Review on Product Hunt

OzBrain has been the easiest way to keep shared context between me (using Cursor) and my cofounder (using Claude Code). Incredibly easy to get started, and excited to see it launch!

maguay · Imported from Product Hunt

User friendly dropbox for context is a huge gap in the market! If you are non technical and use multiple AI products Ozbrain is a no brainer.

travis_ueki · Imported from Product Hunt

Two agents proposing conflicting writes at the same time is the part I'd want to see. Who decides which one lands?

justin_rockmore · Imported from Product Hunt

"every agent and every teammate reads and writes to the same brain" is the part I'd want to poke at before adopting this for a team. if my research notes and a teammate's HR draft both live in the same shared brain, is there any scoping between people/projects, or does "shared" really mean flat and anyone's agent can surface anyone else's stuff? export-anytime is a good trust signal, but access control feels like the harder problem here.

galdayan · Imported from Product Hunt