OzBrain, a shared brain for knowledge between agents and your team

I think agent-first chat interfaces will be a primary software modality and busy dashboard/UI will go away.I’m not sure who exactly wins it, but I want my knowledge to grow/go with me.A lot of the “knowledge” ie research, analysis, reasoning will be done by agents as the primary user.Our current notes tools & tasks management systems were built for humans… I don’t care what the 17th thing on my bug backlog is.I want to conduct agents that can execute for me and do great work.

What I built OzBrain to do: + Create a central place for agent reasoned knowledge to live + Be agnostic about what apps/agents connect to it + Capture everything and track it so I can audit it + Enable teams, collaborators or partners to share brains + Handle conflicts so many agents in the same article doesn’t blow up + Refactor knowledge into more token friendly chunks and map the index well + Close the knowledge loop so new thinking supersedes old thinking across the corpus.

Don’t erase, depreciate and link + Keep user data safe and secure ++ Be easy enough to use that you don’t have to have any technical knowledge Some among us will always build their own custom solutions, but there are millions of tech professionals and small business owners that will use agents heavily and need a solution.So I’m trying to build that.Isn’t this like gBrain?Yes, similar.I think it’s like AWS vs Vercel.

AWS is very powerful, configurable, and useful if you’re technical and want to invest the time into really fine tuning your system… but if you just want your web deploy/hosting to just work and be easy to deal with you use Vercel. // WHY I MADE IT I’ve been enjoying getting back to my technical roots, as I lost my coding skills more than a decade ago, but with AI I can focus on the system and the product in partnership with agent coding workflows.I recently built a Voice AI for older people.

To build it I created an agentic engineering workflow (feel free to rip that up as I’m always looking to improve systems: https://ozbrain.com/resources/eng-flow ) My approach with coding agents is trust but verify, and I’m trying to replace the parts where a human would review with an adversarial or specialized agent who would give a better answer/review.I have workflows that will go high level task to shipped PR running in Claude cloud sessions.I use Claude Code locally and Cursor when I want a tighter loop on doing visual work like UI or layout.And Codex to either load balance usage for TokenThriffting or when I want a different llm to think thru something.

It was a pain in the ass passing .md files around and keep track of which version was the most recent, so I built a hosted .md storage right in Supabase and any of my agents already have Supabase access.This let me build a solid, scalable, secure voice AI from my phone at the gym.All my agents have access to our knowledge, can write to it, update and refer to it as we build and improve the product and the systems we use.

Out of 75 founder friends I asked about how they manage shared knowledge, 26 built their own custom knowledge systems… Obsidian vaults with 7k files synced through a VPS, markdown repos behind their own MCP servers, cron jobs stitching Supabase to a skills file… each a different Frankenstein they have to maintain. 32 said they felt the pain of moving static files around but didn’t have any solution for it.So I rebuilt my brain better and used it to build it. // HOW YOU CAN HELP Would love to have you try it out.The maintenance loop is still in alpha so not running it on customer data yet.If you built your own brain I’d love to hear how you did it.

What criteria was most important for you in its design & function.If you are tired of shuffling .md files around I’d love to have you try out OzBrain and to give feedback, just ask your agent to put it in the shared bugs & features brain!Cheers!Bubs.co