Launching today
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.
Panic Free Symptom Checker
Nitrosend
@bubsexcited to see this one live! I've been on the beta for a few weeks, it's one of those immediately useful/straight into my daily workflow tools like Wispr flow/granola/claude routines. set up was a prompt or two, and I just added in a line to my common skills to update ozbrain when the skill runs.
I've found it super useful for product analytics and GTM insights, even kicking off a new feature. Feels like the glue between a lot of systems we run on nitrosend, I don't think I've been back to the UI since I set it up but I use it all the time (from my agent). Very cool
Panic Free Symptom Checker
@gthartley Thanks George! Yup, while there is a UI, I think we're all moving Agent-First and that is where I expect 99.99% of usage happens for OzBrain. Glad it's going well for you!
@bubs nice launch! the idea of the having one shared brain across claude, cursor and other agent make a lot of sense, and also the Dropbox for agent knowledge likeness make the idea pretty easy to understand.
how does OzBrain decide when the something should be obsolete or kept as the current versions??
Panic Free Symptom Checker
@amrita_prajapati2 Thanks! A lot of the "thinking" the brain does around current versions is handled by the system which has versioning built in, so every change is staged/promoted... and your agent that is making the most recent update is holding the context of where-else the content of the article is is working with is linked to/from. So it's really about create a system that helps your agents ensure they are working from the latest thinking.
@bubs congrats for launch🙌qq how does this compare to just using a shared Notion database with an API hook?
Panic Free Symptom Checker
@priya_kushwaha1 Thanks! That's basically where I started... tables in my own DB, agents hooked in over MCP. It works until two agents write at once and clobber each other, or it rots because nobody maintains it, or the agent dumps the whole table into context instead of the part it needed. OzBrain is that same idea with those parts solved: stage/promote conflict handling with a log of who changed what, deprecate-don't-overwrite versioning, and structure so agents pull the right thing. Solo with one agent, a Notion hook is honestly fine. It's the multi-agent, multi-person case where the glue turns into a maintenance job.