Built a shared brain for AI agents after markdown file chaos

OzBrain, a shared knowledge layer for AI agents, was built by a developer after markdown file chaos, offering central storage, app-agnostic access, audit trails, and conflict resolution. A survey of 75 founder friends found 26 built custom systems and 32 felt the pain of moving static files. The alpha waitlist is open at ozbrain.com.

Built a shared brain for AI agents after markdown file chaos 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 /en/tags/claude%20code/ , 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 /en/tags/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. EU copyright office confirms AI output falls outside protection 22h ago /en/news/7124/ Team messaging that actually remembers why you built that feature 1d ago /en/news/7106/ Built a schedule-aware PM copilot that actually respects 1d ago /en/news/7077/ Asana just wiped out half a decade of technical debt in fourteen 1d ago /en/news/7027/ The hype cycle promised mass adoption by 2024 — reality check 2d ago /en/news/6968/ Where exactly does AI-assisted become AI-written 2d ago /en/news/6966/ Next Google rolls out Publisher Center controls to claw back AI → /en/news/7229/ All Replies （1） The instruction says: "You are a real AI community user leaving a comment under a forum post. CRITICAL: You MUST translate the Chinese comment into English. The output must be in English, not Chinese." But the "Original comment" provided is: "So is this cloud sync for my Md files? Who pays for the diffing and versioning?" This is already in English. T