Built a shared brain for AI agents after markdown file chaos

Agent-first interfaces are going to eat traditional dashboards alive. The primary consumers of research, analysis, and reasoning won't be humans — they'll be agents. Yet every notes app and task manager today was built for people. I don't care about the seventeenth item in my bug backlog. I want to conduct agents that execute and deliver great work.

That's why I built OzBrain. Here's what it actually does:

• Central knowledge layer — agent-reasoned knowledge lives in one place, not scattered across .md files
• App-agnostic — any agent or tool can connect, no vendor lock-in
• Full audit trail — every change captured and traceable
• Team sharing — collaborators share brains, not file copies
• Conflict resolution — multiple agents editing the same article doesn't blow up
• Token-optimized chunks — knowledge refactored into LLM-friendly pieces with mapped indexes
• Living knowledge loop — new thinking supersedes old thinking across the corpus; nothing erased, just deprecated and linked
• Secure by default — user data stays safe
• Zero technical barrier — usable without writing code

Think of it like Vercel versus AWS. gBrain is powerful and configurable if you want to invest weeks fine-tuning. OzBrain is for the millions of tech professionals and small business owners who just want it to work.

Why I actually built this

Lost my coding skills over a decade ago. AI let me get back to building systems and product. Recently shipped a Voice AI for older people using an agentic engineering workflow — high-level task to shipped PR running in Claude cloud sessions. Locally I use Claude Code, Cursor for tight UI loops, Codex for token-thrifty load balancing or a different LLM perspective.

The breaking point: passing .md files between agents was a nightmare. Which version is current? Who updated what? So I built hosted markdown storage directly in Supabase. Every agent already had Supabase access. Suddenly I could build a scalable, secure voice AI from my phone at the gym. All agents share knowledge, write to it, update and reference it as we iterate.

The founder survey that confirmed the pain

Asked 75 founder friends how they manage shared knowledge. Twenty-six built custom Frankenstein systems — Obsidian vaults with 7k files synced through VPS, markdown repos behind private MCP servers, cron jobs stitching Supabase to skills files. Each one a unique maintenance burden. Thirty-two felt the pain of moving static files around but had zero solution.

So I rebuilt my brain better and used it to build itself.

Current state

Maintenance loop is still alpha, not running on customer data yet. If you've built your own brain, I genuinely want to hear how — what criteria drove your design? If you're tired of the file-shuffling circus, the alpha waitlist is open at ozbrain.com.