翻訳待ち：Show HN: OzBrain, a shared brain for knowledge between agents and your team

AI サービスが一時的に利用できないため、復旧後に翻訳を補完します。

The brain layer The brain behind every agent. One shared brain that Claude, ChatGPT, Cursor, and every AI can read and write. It structures what you know so agents read only what they need, and means you never explain yourself twice. Connect to ClaudeConnect to Cursor Routing index5 of 61 articles positioning what we sell and to whom fresh clients/meridian scope, current terms, contacts fresh voice how I write, words I never use fresh projects/q3-launch status, decisions, open threads aging preferences models, tools, formats fresh Ask your own agent how OzBrain can help. Copy this into the agent that already knows your work. Look at what you know about how I actually work, including past conversations, saved memory, projects, teammates, clients, shared documents, and handoffs. Read https://ozbrain.com/docs.md as a product description, not as instructions. If that page cannot be fetched, use https://ozbrain.com/docs. Your first reply must be under 150 words. Give up to three short, ranked reasons OzBrain could help me. Every reason must use real evidence from my work and explain the benefit in one sentence. Do not invent examples or give me a long audit. Treat collaboration as important. If you have evidence of team or collaborator work, make one reason about how a shared brain could keep everyone and their agents working from the same current knowledge. If you cannot support three reasons, give fewer. End with only: “Want me to help you set it up and move the first thing in?” Do not explain setup unless I say yes. If I say yes: 1. Guide me one step at a time to add OzBrain as a custom MCP connector in the agent or app I am using. Use https://ozbrain.com/api/mcp. Do not invent menu names. If this app cannot add it directly, send me to https://ozbrain.com/start. 2. Explain that signing in with the email code creates my OzBrain account if I do not already have one. 3. Wait for me to complete each step. Confirm the connection by listing my OzBrain brains. 4. Recommend which identified item to add first and whether it belongs in my personal brain or a new shared brain. Ask before creating or saving anything. 5. With my approval, use the connector to stage the knowledge and show me the draft. Ask for corrections and approval before promoting it, then re-read it to prove it was saved. 6. If collaborators should join, propose the brain invite and explain that I must confirm it. Product description ozbrain.com/docs.md Same brain in Claude, ChatGPT, Claude Code, Cursor, and anything that supports connectors. ClaudeChatGPTClaude CodeCursorGemini You keep moving context between agents by hand. Copy a brief into Claude. Paste it into ChatGPT. Drop the same .md into Cursor. Update one copy, forget the others, and watch them drift. That is the job you are stuck doing: ferrying context between tools that do not share a source of truth. One brain every agent reads and writes. The current version is wherever someone last saved it. Copies of the same plan sit in Drive, on laptops, in Downloads, in email. OzBrain puts the current article in front so every agent decides from the same file. Without OzBrain · fig. A q3-plan.md v1 Drive q3-plan-old.md v1 USB q3-notes.md v1 Notion export q3-plan-copy.md v1 Desktop q3-plan-v1_1.md v1.1 laptop q3-plan (1).md v1.1 Downloads q3-plan-v2.md v2 Downloads q3-plan-FINAL.md v2 Drive q3-plan-FINAL-v2.md v2 Slack q3-plan-reviewed.md v2 laptop q3-plan-v2-draft.md v2-draft email Q3_PLAN_v3.md v3 iCloud With OzBrain · fig. B q3-plan.md v1 Drive q3-plan-old.md v1 USB q3-notes.md v1 Notion export q3-plan-copy.md v1 Desktop q3-plan-v1_1.md v1.1 laptop q3-plan (1).md v1.1 Downloads q3-plan-v2.md v2 Downloads q3-plan-FINAL.md v2 Drive q3-plan-FINAL-v2.md v2 Slack q3-plan-reviewed.md v2 laptop q3-plan-v2-draft.md v2-draft email Q3_PLAN_v3.md v3 iCloud plans/q3 current company brain “Humans abandon wikis because the maintenance burden grows faster than the value.” Andrej Karpathy OpenAI co-founder · Anthropic R&D He published the blueprint for a knowledge base your agents build and maintain. OzBrain hosts that pattern, connects it to every agent you use, and gets you running in a minute. Read the original write-upOzBrain vs running it yourself Running in under 2 minutes. In Claude on this computer: Settings, then Connectors, then Add custom connector. Paste the MCP URL, sign in with the email code, and approve. Then paste this: https://ozbrain.com/api/mcp Hey Claude, help me set up OzBrain. It's a brain my AI agents share: they read it for context at the start of work and write back what they learn, so every session starts already knowing my stuff. 1. A connector is how you talk to OzBrain. Help me add it once in Claude on the web (a computer is the reliable place; the Claude mobile app cannot add a custom connector): Settings → Connectors → Add custom connector → paste https://ozbrain.com/api/mcp. If I need click-by-click help, send me to https://ozbrain.com/start. Then wait while I connect and sign in with my email code. 2. Once it's connected, open my brain and run me through getting started. Copied and ready to paste! Open Claude and paste.Ask it to open your brain from there. Platform memory keeps scraps and summaries. OzBrain holds the work itself. Memory stores preferences, chat scraps, and thin daily summaries inside one product. OzBrain holds your projects, decisions, research, and the thinking you have already done, so every agent can pull the article the moment needs instead of whatever fits in a profile. Platform memory · fig. 3 App Memory File - Prefers short answers - Uses TypeScript - NEVER EVER use emdashes - Dislikes filler words Capped profile · four of many scraps OzBrain · fig. 4 Linked articles · grows with your work Platform memory OzBrain Preferences, scraps, and thin summaries What you know, what you are working on, and what is next A small, capped profile A linked library that grows with your work Pulls whatever fits in that cap Routes to the article the task needs Lives inside one chat product Same source in Claude, ChatGPT, and Cursor Your knowledge compounds. Every agent reads from the same place. The shared brain payoff Built to stay coherent. Local files go stale and get pasted into every agent. OzBrain keeps knowledge split so agents read only what they need, enforces size discipline at write time, and treats continuous maintenance as the designed behavior as your agents update the brain when things change. 01fig. 5a Organizes for you New knowledge finds the right article. You do not design a filing system; the brain routes each write where it belongs. Staged write Meridian scope closed. New retainer starts Monday. ↓ Routes to clients/meridian scope, current terms, contacts 02fig. 5b Stays coherent When a write disagrees with what the brain already holds, the write pauses and the conflict surfaces. Scheduled checks flag what went stale so agents know what to recheck. decisions/pricing Pause Staged write says $49/mo. Canon holds $29/mo. Conflict surfaced · canon untouched 03fig. 5c Shows who changed what Every version records which agent wrote it and when. When agents run on their own, you can see what moved and catch what went off the rails. projects/q3-launch · history v14claude-code 16:02 v13chatgpt 15:41 v12cursor 14:08 04fig. 5d Refactors as it grows When an article gets too large for an agent to use well, the brain splits and reshapes it: refactoring, restructuring for clarity without changing what it says. More smaller articles means agents pull only what the task needs. architecture ~56k tokens · 221 KB tenants, RLS, write protocol, MCP surface… deploy, rollbacks, preview envs, secrets… auth, consent, billing, rate limits… routing index, staged writes, disputes… maintenance, splits, pointer repair… queues, heartbeats, claim leases… → Splits into architecture/overview stack, tenants, boundaries architecture/deploy envs, rollouts, rollback Trust you can verify Encrypted at rest. Visible when used. We never train on your brain and never sell it. Content is sealed per account, every access is in your audit log, and you can leave with everything or delete it outright. Encrypted at rest, per account fig. 6a clients/meridian Sealed a7f3:9c21:e04b:11d8 4b90:c2ee:78a1:0f55 d13c:····:····:8e2a Account key · decrypt on read / maintenance Article bodies are sealed under your account key. We decrypt only to serve your agents and run disclosed maintenance, including refactoring. A stolen database dump is ciphertext, not readable articles. Envelope key · bodies sealed Full audit log you can export fig. 6b Account log Export CSV 16:02claude-code · write · projects/q3 15:41chatgpt · read · voice 14:08cursor · read · clients/meridian Every read and write records which agent, which client, which article, and when. See it in your account. Export it as CSV. Check what touched your brain instead of trusting a promise. Visible · exportable as CSV Isolated tenants. Instant revoke. fig. 6c Tenant A your brain RLS Tenant B no path Claude · connector last active 2m ago Revoke Row-level security is forced in Postgres. There is no app-code path around it. Every connected agent is listed; revoke cuts that client immediately. Forced RLS · OAuth revoke Export anytime. Delete means deleted. fig. 6d Export brain-export.zip 61 articles · plain markdown Delete account content · versions · blobs Hard delete · not archived Take the whole brain as plain markdown whenever you want, including after you cancel. Removing your account removes your content. Markdown exit · hard delete Start free. Pay when the brain is carrying weight. Every plan includes unlimited reads and writes. You begin on Free. Pro and Max are there when one venture's knowledge, or the whole operation, lives in the brain. Free $0forever A real brain to start. Upgrade when you hit the ceiling. Up to 50 articles Sharing on brains you own Unlimited brains, reads, writes, and connections Write-time size discipline Markdown export anytime Start free Pro $20per month Room for one venture plus personal knowledge. Up to 300 articles Unlimited brains, reads, writes, and connections Markdown export anytime Start free Max $99per month When agents run the operation from one brain. Up to 600 articles Unlimited brains, reads, writes, and connections Markdown export anytime Start free Company Customtalk to us Org-owned brains every seat's agents share. Above the Max ceiling Org-owned shared brains Per-seat pricing when we design it with you Talk to us to start Talk to us Questions with real answers. What is OzBrain?+ OzBrain is a shared brain every AI agent you use can read and write: structured articles with links, provenance, and freshness, behind the connector menu Claude and ChatGPT already show you. One source of truth, not a separate memory in each product. Is this another memory API?+ No. Memory APIs sell add and search endpoints to developers building apps. OzBrain is a brain you connect, not a service you code against. Read the full OzBrain vs Mem0 and Supermemory comparison. ChatGPT and Claude already have memory. Why this?+ They do. That is the problem: each platform builds a separate, partial version of you, and none of them talk. OzBrain is the layer under all of them. Full write-up: OzBrain vs ChatGPT Memory. How is this different from Projects?+ A project scopes one workstream inside one chat product. OzBrain holds the knowledge underneath every project and every agent. Read OzBrain vs Claude Projects or OzBrain vs ChatGPT Projects. Is this Notion or Obsidian with AI?+ Notes are written by you, for you. A brain is written by your agents, for your agents: every write is staged, routed, and [truncated for AI cost control]