Garry's Opinionated OpenClaw/Hermes Agent Brain
TypeScript
README: open on one brain for you and your company (#9382)
Garry Tan88ecc3156f3f
diff --git a/README.md b/README.mdindex 499d680a51..fb11952ed0 100644--- a/README.md+++ b/README.md@@ -1,92 +1,26 @@<h1><picture><source media="(prefers-color-scheme: dark)" srcset="docs/images/brand/gbrain-wordmark-light.svg"><img src="docs/images/brand/gbrain-wordmark.svg" alt="GBrain" height="52"></picture></h1>-**Give the agent you already use a memory you control.** GBrain stores explicit facts with their sources, supports corrections and withdrawal, and makes the same memory available across your agents. Start with keyless memory and keyword retrieval; add semantic search, synthesis, and background enrichment when you need them.+**One brain for you and your company, read by every agent you use.** Put your own notes and your company's docs in one place: a facts page, a decisions log, call transcripts. Claude Code, Codex and your other agents look there before they answer, so they stop starting from zero and work from what you and your team actually wrote down.-GBrain is MIT-licensed and free to self-host; gbrain.io is optional paid hosting.+GBrain is MIT-licensed and free to self-host, and it starts with no API keys: search is by keyword until you add one. gbrain.io is optional paid hosting.> [!TIP]> **Need hosted? First time running an agent?** Try **[gbrain.io](https://gbrain.io/?ref=readme)**, hosted GBrain, for the easiest experience: one brain for you and your team, connected to ChatGPT, Claude and Cursor, with nothing to install or keep online. Stuck? Email [email protected] and a person will set it up with you, free.-**Keep skills beside knowledge.** New local brains include memory skills in their-content root. Agents can join an authorized catalog; only approved editors can-publish. Managed coding-agent installs add an owned native router; restart and-real-use verification are separate steps. Staged migration preserves sharing-choices and personal edits. See [shared brain skills](docs/guides/shared-brain-skills.md).--## Choose your setup--1. **Add GBrain to my existing agent — recommended.** Keep your agent's identity and save memory inside its environment. No new personal-agent identity or private repository is required. Start with the guide for **[Grok Bot](docs/guides/grok-bot.md)**, **[Muse](docs/guides/muse.md)**, or **[Codex / Claude Code](docs/tutorials/connect-coding-agent.md)**. [Other harnesses](#connect-gbrain-to-your-ai-client-mcp).-2. **Use the brain on my own computer from everywhere.** One command publishes it over MCP on your Tailscale tailnet and keeps it running: `gbrain mcp expose` (add `--funnel` for cloud agents such as Grok Bot, Muse and ChatGPT). Follow **[use your brain from anywhere over MCP](docs/guides/remote-mcp.md)**. **Say to your agent:** *"use my brain over mcp"* — *"put my brain on tailscale"*.-3. **Connect my existing hosted brain.** Follow **[hosted harness access](docs/guides/hosted-harness-access.md)** to choose native OAuth or a private machine connection. For dashboard login, clients, and permissions, use **[MCP administration](docs/mcp/ADMIN.md)** with the server's separate owner credential. Delegation is an explicit choice.--Grok **Bot** and Grok **Build** are different products. Muse's personal agent and **Muse Code** are different products too. Muse already has native editable memory; GBrain adds an explicit, portable record with provenance and shared access. See each guide's dated evidence and remaining verification steps.--I'm Garry Tan, President and CEO of Y Combinator. I built GBrain to run my own AI agents. It's the production brain behind my OpenClaw and Hermes deployments: **155,795 pages, 24,589 people, 5,340 companies**, 66 cron jobs running autonomously. My agent ingests meetings, emails, tweets, voice calls, and original ideas while I sleep. It enriches every person and company it encounters. It fixes its own citations and consolidates memory overnight. I wake up smarter than when I went to bed — and so will you.--**It works as a company brain too.** Authenticated remote clients are constrained by source and operation grants plus visibility filters. Local files and shared database credentials are a different trust boundary: sources alone do not isolate those callers. The authorization tests exercise specific access paths, not a universal no-leak guarantee. Read the [sharing boundaries](docs/architecture/brains-and-sources.md#what-confines-remote-callers-and-what-does-not) and [company-brain tutorial](docs/tutorials/company-brain.md) before setting up shared access.--Alongside keyword and semantic retrieval, GBrain offers two optional ways to use your stored knowledge:--- **A synthesis layer that gives you the actual answer.** Synthesized, well-cited prose across people, companies, deals, and ideas. Not "here are 10 chunks that mention your query"; an actual answer with citations and an explicit note on what the brain doesn't know yet. The gap analysis is the part that changes how you use the brain.-- **A typed knowledge graph.** Trusted local page writes extract supported references without LLM calls when auto-linking is enabled. Remote `put_page` edges arrive later, via sweeps, maintenance or `add_link`. Ask "who works at acme-example?": walks are breadth-first, milliseconds on dense clusters ([how](docs/architecture/RETRIEVAL.md#breadth-first-graph-walks)). On BrainBench relationship questions, relationship retrieval lifts production **R@5 from 0.6626 to 0.7241** ([benchmark](docs/architecture/RETRIEVAL.md#the-benchmark)); 0.9791 is the `graph-oracle-parse` upper bound, not a product score.+**A few minutes after you install it:**-The point of building a 150K-page brain is to use it as a strategic moat. To never lose context. To query what's in your own head without re-reading it. The brain layer is what makes the moat usable. The 24/7 dream cycle is what keeps it sharp. Both run on your hardware, your DB, your keys.+- Every new Claude Code or Codex session looks in your brain before it answers, without being told to.+- Anything you ask your agent to remember is still there in the next session, in every agent connected to the brain.+- Your notes and your company's docs are searchable, and your agent answers questions like *"what did we decide about pricing, and why?"* from them.-It's easier to ship a daemon that runs 24/7 to ingest, enrich, and consolidate than it is to keep an agent in chat working hard. GBrain is that daemon, generalized. Install in 30 minutes. Your agent does the work. As my personal agent gets smarter, so does yours.+**Works with these agents** (each name links to its guide):-> **Start keyless.** Your harness subscription and any separately configured model API usage are different costs. The optional personal-agent bootstrap takes about 15 minutes; always-on enrichment needs its own compute and API configuration.--Durable preferences and facts can be shared across agents; transient task and-harness configuration state stay local. Configured cloud embedding, reranking,-extraction, and synthesis providers can receive text, and the harness model sees-recalled memory even in keyless mode. Markdown export is not a full database-backup. Read [memory boundaries](docs/guides/memory-boundaries.md).--> **LLMs:** fetch [`llms.txt`](llms.txt) for the documentation map, or [`llms-full.txt`](llms-full.txt) for the same map with core docs inlined in one fetch. **Agents:** start with [`AGENTS.md`](AGENTS.md) (or [`CLAUDE.md`](CLAUDE.md) if you're Claude Code).--## What this looks like--Say you have a meeting with Alice tomorrow. You want to walk in remembering what she works on, when you last talked, and what's still open between you. Here's what you'd type, and what you'd get back.--**You ask:**--> "What do I need to know before my meeting with Alice tomorrow?"--**Most personal-knowledge tools give you back a list of pages.** Something like:--```-1. people/alice — Alice runs engineering at Acme...-2. meetings/2026-03-15-alice-q1 — Q1 product review with Alice...-3. meetings/2026-01-08-acme-kickoff — Kickoff meeting with Acme team...-4. customers/acme — Acme is a series-B fintech we work with...-5. notes/2026-04-22 — Quick chat with Alice about pricing...-```--Five pages you now have to open and read yourself to actually prepare. The tool found the right material, but it didn't do the work.--**GBrain gives you back the answer, with sources:**--```-Alice runs engineering at Acme (a series-B fintech). You last spoke-on April 22 in a quick pricing chat. Three things are still open-from that conversation:--1. She owes you the security review for the new tier- (deadline was May 1; no update since).-2. You committed to pricing for a 500-seat tier- (you sent it April 25; no response yet).-3. She mentioned they're hiring a CISO; you said you'd intro- someone from your network.--Heads up: nothing's been added to the brain about Alice or Acme-since April 22, six weeks ago. She may have replied through email-or Slack DM, channels the brain doesn't see. Worth asking her to-catch up before assuming any of this is still current.-```--Every claim has a source page behind it. The "heads up" at the end tells you what the brain doesn't know yet, so you can ask Alice about it directly instead of being surprised. The brain just did your meeting prep.--This is the difference between a search engine and a brain. Search finds the pages. The brain reads them for you and writes the answer.+| How it connects | Agents |+|---|---|+| One command wires memory, hooks and instructions | [Claude Code](docs/mcp/CLAUDE_CODE.md) (`gbrain setup claude-code`), [Codex](docs/mcp/CODEX.md) (`gbrain setup codex`) |+| MCP from its guide, then `gbrain setup <name>` adds the brain-first instructions | [OpenClaw](docs/mcp/OPENCLAW.md), [Hermes](docs/mcp/HERMES.md), [opencode](docs/mcp/OPENCODE.md), [Cursor](#connect-gbrain-to-your-ai-client-mcp) |+| MCP from its guide | [ChatGPT](docs/mcp/CHATGPT.md), [Claude Desktop](docs/mcp/CLAUDE_DESKTOP.md), [Claude Cowork](docs/mcp/CLAUDE_COWORK.md), [Perplexity](docs/mcp/PERPLEXITY.md), [Grok Build](docs/mcp/GROK.md), [Grok Bot](docs/guides/grok-bot.md), [Muse](docs/guides/muse.md), [Windsurf and other stdio clients](#connect-gbrain-to-your-ai-client-mcp) |+| Any other coding agent | Paste the [install prompt](#heres-how-to-self-host-it) below |## Install@@ -140,6 +74,20 @@ search-mode choice. Verify a remember/recall round trip with real GBrain calls.Postgres, thin clients, API keys and upgrades: [docs/INSTALL.md](docs/INSTALL.md). Agents: [INSTALL_FOR_AGENTS.md](INSTALL_FOR_AGENTS.md). Memory-only walkthrough: [give your coding agent a memory](docs/tutorials/connect-coding-agent.md).+### Add your notes and your company's docs++Point GBrain at two folders of Markdown files: your own notes (an Obsidian vault works) and your company's docs. In the company folder, keep `facts.md` (numbers and statements agents may repeat), `decisions.md` (each decision with its date, its reason and who made it) and call transcripts saved as `.md` files.++```bash+gbrain sources add notes --path ~/notes --federated --force # your notes+gbrain sources add company --path ~/company --federated --force # company docs+gbrain sync --all # rerun after edits+```++Then open a new agent session and ask *"What did we decide about a free plan, and why?"*: the answer comes from your decisions log. `--federated` puts the folder in default search, and `--force` accepts a folder that isn't a git repository; in a folder that is one, GBrain reads only committed files, so commit your edits before you sync. To see the shape first, `gbrain sources demo company-brain` runs a fictional company in a few seconds without touching your brain. Before you share a company brain with a team, read the [company-brain tutorial](docs/tutorials/company-brain.md).++GBrain is not a data warehouse or analytics store. Keep ads, analytics, CRM and payment data in your warehouse, and connect your agent to it separately.+### CLI standalone (no agent)```bash@@ -173,6 +121,87 @@ The repo is not a complete backup; see the [bootstrap guide](docs/guides/bootstrPer-client guides: [Claude Code](docs/mcp/CLAUDE_CODE.md) · [Codex](docs/mcp/CODEX.md) · [ChatGPT](docs/mcp/CHATGPT.md) · [Claude Desktop](docs/mcp/CLAUDE_DESKTOP.md) · [Claude Cowork](docs/mcp/CLAUDE_COWORK.md) · [Perplexity](docs/mcp/PERPLEXITY.md) · [Hermes](docs/mcp/HERMES.md) · [OpenClaw](docs/mcp/OPENCLAW.md) · [opencode](docs/mcp/OPENCODE.md) · [Grok Build](docs/mcp/GROK.md) · [Grok Bot](docs/guides/grok-bot.md) · [Muse](docs/guides/muse.md) · [everything MCP](docs/mcp/README.md).+**Keep skills beside knowledge.** New local brains include memory skills in their+content root. Agents can join an authorized catalog; only approved editors can+publish. Managed coding-agent installs add an owned native router; restart and+real-use verification are separate steps. Staged migration preserves sharing+choices and personal edits. See [shared brain skills](docs/guides/shared-brain-skills.md).++## Choose your setup++1. **Add GBrain to my existing agent — recommended.** Keep your agent's identity and save memory inside its environment. No new personal-agent identity or private repository is required. Start with the guide for **[Grok Bot](docs/guides/grok-bot.md)**, **[Muse](docs/guides/muse.md)**, or **[Codex / Claude Code](docs/tutorials/connect-coding-agent.md)**. [Other harnesses](#connect-gbrain-to-your-ai-client-mcp).+2. **Use the brain on my own computer from everywhere.** One command publishes it over MCP on your Tailscale tailnet and keeps it running: `gbrain mcp expose` (add `--funnel` for cloud agents such as Grok Bot, Muse and ChatGPT). Follow **[use your brain from anywhere over MCP](docs/guides/remote-mcp.md)**. **Say to your agent:** *"use my brain over mcp"* — *"put my brain on tailscale"*.+3. **Connect my existing hosted brain.** Follow **[hosted harness access](docs/guides/hosted-harness-access.md)** to choose native OAuth or a private machine connection. For dashboard login, clients, and permissions, use **[MCP administration](docs/mcp/ADMIN.md)** with the server's separate owner credential. Delegation is an explicit choice.++Grok **Bot** and Grok **Build** are different products. Muse's personal agent and **Muse Code** are different products too. Muse already has native editable memory; GBrain adds an explicit, portable record with provenance and shared access. See each guide's dated evidence and remaining verification steps.++I'm Garry Tan, President and CEO of Y Combinator. I built GBrain to run my own AI agents. It's the production brain behind my OpenClaw and Hermes deployments: **155,795 pages, 24,589 people, 5,340 companies**, 66 cron jobs running autonomously. My agent ingests meetings, emails, tweets, voice calls, and original ideas while I sleep. It enriches every person and company it encounters. It fixes its own citations and consolidates memory overnight. I wake up smarter than when I went to bed — and so will you.++**It works as a company brain too.** Authenticated remote clients are constrained by source and operation grants plus visibility filters. Local files and shared database credentials are a different trust boundary: sources alone do not isolate those callers. The authorization tests exercise specific access paths, not a universal no-leak guarantee. Read the [sharing boundaries](docs/architecture/brains-and-sources.md#what-confines-remote-callers-and-what-does-not) and [company-brain tutorial](docs/tutorials/company-brain.md) before setting up shared access.++Alongside keyword and semantic retrieval, GBrain offers two optional ways to use your stored knowledge:++- **A synthesis layer that gives you the actual answer.** Synthesized, well-cited prose across people, companies, deals, and ideas. Not "here are 10 chunks that mention your query"; an actual answer with citations and an explicit note on what the brain doesn't know yet. The gap analysis is the part that changes how you use the brain.+- **A typed knowledge graph.** Trusted local page writes extract supported references without LLM calls when auto-linking is enabled. Remote `put_page` edges arrive later, via sweeps, maintenance or `add_link`. Ask "who works at acme-example?": walks are breadth-first, milliseconds on dense clusters ([how](docs/architecture/RETRIEVAL.md#breadth-first-graph-walks)). On BrainBench relationship questions, relationship retrieval lifts production **R@5 from 0.6626 to 0.7241** ([benchmark](docs/architecture/RETRIEVAL.md#the-benchmark)); 0.9791 is the `graph-oracle-parse` upper bound, not a product score.++The point of building a 150K-page brain is to use it as a strategic moat. To never lose context. To query what's in your own head without re-reading it. The brain layer is what makes the moat usable. The 24/7 dream cycle is what keeps it sharp. Both run on your hardware, your DB, your keys.++It's easier to ship a daemon that runs 24/7 to ingest, enrich, and consolidate than it is to keep an agent in chat working hard. GBrain is that daemon, generalized. Install in 30 minutes. Your agent does the work. As my personal agent gets smarter, so does yours.++> **Start keyless.** Your harness subscription and any separately configured model API usage are different costs. The optional personal-agent bootstrap takes about 15 minutes; always-on enrichment needs its own compute and API configuration.++Durable preferences and facts can be shared across agents; transient task and+harness configuration state stay local. Configured cloud embedding, reranking,+extraction, and synthesis providers can receive text, and the harness model sees+recalled memory even in keyless mode. Markdown export is not a full database+backup. Read [memory boundaries](docs/guides/memory-boundaries.md).++> **LLMs:** fetch [`llms.txt`](llms.txt) for the documentation map, or [`llms-full.txt`](llms-full.txt) for the same map with core docs inlined in one fetch. **Agents:** start with [`AGENTS.md`](AGENTS.md) (or [`CLAUDE.md`](CLAUDE.md) if you're Claude Code).++## What this looks like++Say you have a meeting with Alice tomorrow. You want to walk in remembering what she works on, when you last talked, and what's still open between you. Here's what you'd type, and what you'd get back.++**You ask:**++> "What do I need to know before my meeting with Alice tomorrow?"++**Most personal-knowledge tools give you back a list of pages.** Something like:++```+1. people/alice — Alice runs engineering at Acme...+2. meetings/2026-03-15-alice-q1 — Q1 product review with Alice...+3. meetings/2026-01-08-acme-kickoff — Kickoff meeting with Acme team...+4. customers/acme — Acme is a series-B fintech we work with...+5. notes/2026-04-22 — Quick chat with Alice about pricing...+```++Five pages you now have to open and read yourself to actually prepare. The tool found the right material, but it didn't do the work.++**GBrain gives you back the answer, with sources:**++```+Alice runs engineering at Acme (a series-B fintech). You last spoke+on April 22 in a quick pricing chat. Three things are still open+from that conversation:++1. She owes you the security review for the new tier+ (deadline was May 1; no update since).+2. You committed to pricing for a 500-seat tier+ (you sent it April 25; no response yet).+3. She mentioned they're hiring a CISO; you said you'd intro+ someone from your network.++Heads up: nothing's been added to the brain about Alice or Acme+since April 22, six weeks ago. She may have replied through email+or Slack DM, channels the brain doesn't see. Worth asking her to+catch up before assuming any of this is still current.+```++Every claim has a source page behind it. The "heads up" at the end tells you what the brain doesn't know yet, so you can ask Alice about it directly instead of being surprised. The brain just did your meeting prep.++This is the difference between a search engine and a brain. Search finds the pages. The brain reads them for you and writes the answer.+## Two ways to query your brainRaw retrieval (what most personal-knowledge tools ship) and a synthesis layer that gives you an actual answer. They serve different jobs.diff --git a/changelog.d/capy-readme-first-screen.md b/changelog.d/capy-readme-first-screen.mdnew file mode 100644index 0000000000..d9081267ab--- /dev/null+++ b/changelog.d/capy-readme-first-screen.md@@ -0,0 +1,6 @@+**The README now opens on one brain for you and your company.**++### Changed+- The first screen says who GBrain is for, what you have a few minutes after installing, and how to add your own notes and your company's docs (a facts page, a decisions log, call transcripts) as two searchable folders with three commands.+- It says plainly that GBrain is not a data warehouse or analytics store.+- The install block and the hosted option are unchanged; the sections that used to sit above the install now follow it.diff --git a/llms-full.txt b/llms-full.txtindex c6d2cf8271..ce24b3d89c 100644--- a/llms-full.txt+++ b/llms-full.txt@@ -4382,93 +4382,27 @@ Source: https://raw.githubusercontent.com/garrytan/gbrain/master/README.md<h1><picture><source media="(prefers-color-scheme: dark)" srcset="docs/images/brand/gbrain-wordmark-light.svg"><img src="docs/images/brand/gbrain-wordmark.svg" alt="GBrain" height="52"></picture></h1>-**Give the agent you already use a memory you control.** GBrain stores explicit facts with their sources, supports corrections and withdrawal, and makes the same memory available across your agents. Start with keyless memory and keyword retrieval; add semantic search, synthesis, and background enrichment when you need them.+**One brain for you and your company, read by every agent you use.** Put your own notes and your company's docs in one place: a facts page, a decisions log, call transcripts. Claude Code, Codex and your other agents look there before they answer, so they stop starting from zero and work from what you and your team actually wrote down.-GBrain is MIT-licensed and free to self-host; gbrain.io is optional paid hosting.+GBrain is MIT-licensed and free to self-host, and it starts with no API keys: search is by keyword until you add one. gbrain.io is optional paid hosting.> [!TIP]> **Need hosted? First time running an agent?** Try **[gbrain.io](https://gbrain.io/?ref=readme)**, hosted GBrain, for the easiest experience: one brain for you and your team, connected to ChatGPT, Claude and Cursor, with nothing to install or keep online. Stuck? Email [email protected] and a person will set it up with you, free.-**Keep skills beside knowledge.** New local brains include memory skills in their-content root. Agents can join an authorized catalog; only approved editors can-publish. Managed coding-agent installs add an owned native router; restart and-real-use verification are separate steps. Staged migration preserves sharing-choices and personal edits. See [shared brain skills](docs/guides/shared-brain-skills.md).--## Choose your setup--1. **Add GBrain to my existing agent — recommended.** Keep your agent's identity and save memory inside its environment. No new personal-agent identity or private repository is required. Start with the guide for **[Grok Bot](docs/guides/grok-bot.md)**, **[Muse](docs/guides/muse.md)**, or **[Codex / Claude Code](docs/tutorials/connect-coding-agent.md)**. [Other harnesses](#connect-gbrain-to-your-ai-client-mcp).-2. **Use the brain on my own computer from everywhere.** One command publishes it over MCP on your Tailscale tailnet and keeps it running: `gbrain mcp expose` (add `--funnel` for cloud agents such as Grok Bot, Muse and ChatGPT). Follow **[use your brain from anywhere over MCP](docs/guides/remote-mcp.md)**. **Say to your agent:** *"use my brain over mcp"* — *"put my brain on tailscale"*.-3. **Connect my existing hosted brain.** Follow **[hosted harness access](docs/guides/hosted-harness-access.md)** to choose native OAuth or a private machine connection. For dashboard login, clients, and permissions, use **[MCP administration](docs/mcp/ADMIN.md)** with the server's separate owner credential. Delegation is an explicit choice.--Grok **Bot** and Grok **Build** are different products. Muse's personal agent and **Muse Code** are different products too. Muse already has native editable memory; GBrain adds an explicit, portable record with provenance and shared access. See each guide's dated evidence and remaining verification steps.--I'm Garry Tan, President and CEO of Y Combinator. I built GBrain to run my own AI agents. It's the production brain behind my OpenClaw and Hermes deployments: **155,795 pages, 24,589 people, 5,340 companies**, 66 cron jobs running autonomously. My agent ingests meetings, emails, tweets, voice calls, and original ideas while I sleep. It enriches every person and company it encounters. It fixes its own citations and consolidates memory overnight. I wake up smarter than when I went to bed — and so will you.--**It works as a company brain too.** Authenticated remote clients are constrained by source and operation grants plus visibility filters. Local files and shared database credentials are a different trust boundary: sources alone do not isolate those callers. The authorization tests exercise specific access paths, not a universal no-leak guarantee. Read the [sharing boundaries](docs/architecture/brains-and-sources.md#what-confines-remote-callers-and-what-does-not) and [company-brain tutorial](docs/tutorials/company-brain.md) before setting up shared access.--Alongside keyword and semantic retrieval, GBrain offers two optional ways to use your stored knowledge:--- **A synthesis layer that gives you the actual answer.** Synthesized, well-cited prose across people, companies, deals, and ideas. Not "here are 10 chunks that mention your query"; an actual answer with citations and an explicit note on what the brain doesn't know yet. The gap analysis is the part that changes how you use the brain.-- **A typed knowledge graph.** Trusted local page writes extract supported references without LLM calls when auto-linking is enabled. Remote `put_page` edges arrive later, via sweeps, maintenance or `add_link`. Ask "who works at acme-example?": walks are breadth-first, milliseconds on dense clusters ([how](docs/architecture/RETRIEVAL.md#breadth-first-graph-walks)). On BrainBench relationship questions, relationship retrieval lifts production **R@5 from 0.6626 to 0.7241** ([benchmark](docs/architecture/RETRIEVAL.md#the-benchmark)); 0.9791 is the `graph-oracle-parse` upper bound, not a product score.--The point of building a 150K-page brain is to use it as a strategic moat. To never lose context. To query what's in your own head without re-reading it. The brain layer is what makes the moat usable. The 24/7 dream cycle is what keeps it sharp. Both run on your hardware, your DB, your keys.+**A few minutes after you install it:**-It's easier to ship a daemon that runs 24/7 to ingest, enrich, and consolidate than it is to keep an agent in chat working hard. GBrain is that daemon, generalized. Install in 30 minutes. Your agent does the work. As my personal agent gets smarter, so does yours.--> **Start keyless.** Your harness subscription and any separately configured model API usage are different costs. The optional personal-agent bootstrap takes about 15 minutes; always-on enrichment needs its own compute and API configuration.+- Every new Claude Code or Codex session looks in your brain before it answers, without being told to.+- Anything you ask your agent to remember is still there in the next session, in every agent connected to the brain.+- Your notes and your company's docs are searchable, and your agent answers questions like *"what did we decide about pricing, and why?"* from them.-Durable preferences and facts can be shared across agents; transient task and-harness configuration state stay local. Configured cloud embedding, reranking,-extraction, and synthesis providers can receive text, and the harness model sees-recalled memory even in keyless mode. Markdown export is not a full database-backup. Read [memory boundaries](docs/guides/memory-boundaries.md).--> **LLMs:** fetch [`llms.txt`](llms.txt) for the documentation map, or [`llms-full.txt`](llms-full.txt) for the same map with core docs inlined in one fetch. **Agents:** start with [`AGENTS.md`](AGENTS.md) (or [`CLAUDE.md`](CLAUDE.md) if you're Claude Code).--## What this looks like--Say you have a meeting with Alice tomorrow. You want to walk in remembering what she works on, when you last talked, and what's still open between you. Here's what you'd type, and what you'd get back.--**You ask:**--> "What do I need to know before my meeting with Alice tomorrow?"+**Works with these agents** (each name links to its guide):-**Most personal-knowledge tools give you back a list of pages.** Something like:--```-1. people/alice — Alice runs engineering at Acme...-2. meetings/2026-03-15-alice-q1 — Q1 product review with Alice...-3. meetings/2026-01-08-acme-kickoff — Kickoff meeting with Acme team...-4. customers/acme — Acme is a series-B fintech we work with...-5. notes/2026-04-22 — Quick chat with Alice about pricing...-```--Five pages you now have to open and read yourself to actually prepare. The tool found the right material, but it didn't do the work.--**GBrain gives you back the answer, with sources:**--```-Alice runs engineering at Acme (a series-B fintech). You last spoke-on April 22 in a quick pricing chat. Three things are still open-from that conversation:--1. She owes you the security review for the new tier- (deadline was May 1; no update since).-2. You committed to pricing for a 500-seat tier- (you sent it April 25; no response yet).-3. She mentioned they're hiring a CISO; you said you'd intro- someone from your network.--Heads up: nothing's been added to the brain about Alice or Acme-since April 22, six weeks ago. She may have replied through email-or Slack DM, channels the brain doesn't see. Worth asking her to-catch up before assuming any of this is still current.-```--Every claim has a source page behind it. The "heads up" at the end tells you what the brain doesn't know yet, so you can ask Alice about it directly instead of being surprised. The brain just did your meeting prep.--This is the difference between a search engine and a brain. Search finds the pages. The brain reads them for you and writes the answer.+| How it connects | Agents |+|---|---|+| One command wires memory, hooks and instructions | [Claude Code](docs/mcp/CLAUDE_CODE.md) (`gbrain setup claude-code`), [Codex](docs/mcp/CODEX.md) (`gbrain setup codex`) |+| MCP from its guide, then `gbrain setup <name>` adds the brain-first instructions | [OpenClaw](docs/mcp/OPENCLAW.md), [Hermes](docs/mcp/HERMES.md), [opencode](docs/mcp/OPENCODE.md), [Cursor](#connect-gbrain-to-your-ai-client-mcp) |+| MCP from its guide | [ChatGPT](docs/mcp/CHATGPT.md), [Claude Desktop](docs/mcp/CLAUDE_DESKTOP.md), [Claude Cowork](docs/mcp/CLAUDE_COWORK.md), [Perplexity](docs/mcp/PERPLEXITY.md), [Grok Build](docs/mcp/GROK.md), [Grok Bot](docs/guides/grok-bot.md), [Muse](docs/guides/muse.md), [Windsurf and other stdio clients](#connect-gbrain-to-your-ai-client-mcp) |+| Any other coding agent | Paste the [install prompt](#heres-how-to-self-host-it) below |## Install@@ -4522,6 +4456,20 @@ search-mode choice. Verify a remember/recall round trip with real GBrain calls.Postgres, thin clients, API keys and upgrades: [docs/INSTALL.md](docs/INSTALL.md). Agents: [INSTALL_FOR_AGENTS.md](INSTALL_FOR_AGENTS.md). Memory-only walkthrough: [give your coding agent a memory](docs/tutorials/connect-coding-agent.md).+### Add your notes and your company's docs++Point GBrain at two folders of Markdown files: your own notes (an Obsidian vault works) and your company's docs. In the company folder, keep `facts.md` (numbers and statements agents may repeat), `decisions.md` (each decision with its date, its reason and who made it) and call transcripts saved as `.md` files.++```bash+gbrain sources add notes --path ~/notes --federated --force # your notes+gbrain sources add company --path ~/company --federated --force # company docs+gbrain sync --all # rerun after edits+```++Then open a new agent session and ask *"What did we decide about a free plan, and why?"*: the answer comes from your decisions log. `--federated` puts the folder in default search, and `--force` accepts a folder that isn't a git repository; in a folder that is one, GBrain reads only committed files, so commit your edits before you sync. To see the shape first, `gbrain sources demo company-brain` runs a fictional company in a few seconds without touching your brain. Before you share a company brain with a team, read the [company-brain tutorial](docs/tutorials/company-brain.md).++GBrain is not a data warehouse or analytics store. Keep ads, analytics, CRM and payment data in your warehouse, and connect your agent to it separately.+### CLI standalone (no agent)```bash@@ -4555,6 +4503,87 @@ The repo is not a complete backup; see the [bootstrap guide](docs/guides/bootstrPer-client guides: [Claude Code](docs/mcp/CLAUDE_CODE.md) · [Codex](docs/mcp/CODEX.md) · [ChatGPT](docs/mcp/CHATGPT.md) · [Claude Desktop](docs/mcp/CLAUDE_DESKTOP.md) · [Claude Cowork](docs/mcp/CLAUDE_COWORK.md) · [Perplexity](docs/mcp/PERPLEXITY.md) · [Hermes](docs/mcp/HERMES.md) · [OpenClaw](docs/mcp/OPENCLAW.md) · [opencode](docs/mcp/OPENCODE.md) · [Grok Build](docs/mcp/GROK.md) · [Grok Bot](docs/guides/grok-bot.md) · [Muse](docs/guides/muse.md) · [everything MCP](docs/mcp/README.md).+**Keep skills beside knowledge.** New local brains include memory skills in their+content root. Agents can join an authorized catalog; only approved editors can+publish. Managed coding-agent installs add an owned native router; restart and+real-use verification are separate steps. Staged migration preserves sharing+choices and personal edits. See [shared brain skills](docs/guides/shared-brain-skills.md).++## Choose your setup++1. **Add GBrain to my existing agent — recommended.** Keep your agent's identity and save memory inside its environment. No new personal-agent identity or private repository is required. Start with the guide for **[Grok Bot](docs/guides/grok-bot.md)**, **[Muse](docs/guides/muse.md)**, or **[Codex / Claude Code](docs/tutorials/connect-coding-agent.md)**. [Other harnesses](#connect-gbrain-to-your-ai-client-mcp).+2. **Use the brain on my own computer from everywhere.** One command publishes it over MCP on your Tailscale tailnet and keeps it running: `gbrain mcp expose` (add `--funnel` for cloud agents such as Grok Bot, Muse and ChatGPT). Follow **[use your brain from anywhere over MCP](docs/guides/remote-mcp.md)**. **Say to your agent:** *"use my brain over mcp"* — *"put my brain on tailscale"*.+3. **Connect my existing hosted brain.** Follow **[hosted harness access](docs/guides/hosted-harness-access.md)** to choose native OAuth or a private machine connection. For dashboard login, clients, and permissions, use **[MCP administration](docs/mcp/ADMIN.md)** with the server's separate owner credential. Delegation is an explicit choice.++Grok **Bot** and Grok **Build** are different products. Muse's personal agent and **Muse Code** are different products too. Muse already has native editable memory; GBrain adds an explicit, portable record with provenance and shared access. See each guide's dated evidence and remaining verification steps.++I'm Garry Tan, President and CEO of Y Combinator. I built GBrain to run my own AI agents. It's the production brain behind my OpenClaw and Hermes deployments: **155,795 pages, 24,589 people, 5,340 companies**, 66 cron jobs running autonomously. My agent ingests meetings, emails, tweets, voice calls, and original ideas while I sleep. It enriches every person and company it encounters. It fixes its own citations and consolidates memory overnight. I wake up smarter than when I went to bed — and so will you.++**It works as a company brain too.** Authenticated remote clients are constrained by source and operation grants plus visibility filters. Local files and shared database credentials are a different trust boundary: sources alone do not isolate those callers. The authorization tests exercise specific access paths, not a universal no-leak guarantee. Read the [sharing boundaries](docs/architecture/brains-and-sources.md#what-confines-remote-callers-and-what-does-not) and [company-brain tutorial](docs/tutorials/company-brain.md) before setting up shared access.++Alongside keyword and semantic retrieval, GBrain offers two optional ways to use your stored knowledge:++- **A synthesis layer that gives you the actual answer.** Synthesized, well-cited prose across people, companies, deals, and ideas. Not "here are 10 chunks that mention your query"; an actual answer with citations and an explicit note on what the brain doesn't know yet. The gap analysis is the part that changes how you use the brain.+- **A typed knowledge graph.** Trusted local page writes extract supported references without LLM calls when auto-linking is enabled. Remote `put_page` edges arrive later, via sweeps, maintenance or `add_link`. Ask "who works at acme-example?": walks are breadth-first, milliseconds on dense clusters ([how](docs/architecture/RETRIEVAL.md#breadth-first-graph-walks)). On BrainBench relationship questions, relationship retrieval lifts production **R@5 from 0.6626 to 0.7241** ([benchmark](docs/architecture/RETRIEVAL.md#the-benchmark)); 0.9791 is the `graph-oracle-parse` upper bound, not a product score.++The point of building a 150K-page brain is to use it as a strategic moat. To never lose context. To query what's in your own head without re-reading it. The brain layer is what makes the moat usable. The 24/7 dream cycle is what keeps it sharp. Both run on your hardware, your DB, your keys.++It's easier to ship a daemon that runs 24/7 to ingest, enrich, and consolidate than it is to keep an agent in chat working hard. GBrain is that daemon, generalized. Install in 30 minutes. Your agent does the work. As my personal agent gets smarter, so does yours.++> **Start keyless.** Your harness subscription and any separately configured model API usage are different costs. The optional personal-agent bootstrap takes about 15 minutes; always-on enrichment needs its own compute and API configuration.++Durable preferences and facts can be shared across agents; transient task and+harness configuration state stay local. Configured cloud embedding, reranking,+extraction, and synthesis providers can receive text, and the harness model sees+recalled memory even in keyless mode. Markdown export is not a full database+backup. Read [memory boundaries](docs/guides/memory-boundaries.md).++> **LLMs:** fetch [`llms.txt`](llms.txt) for the documentation map, or [`llms-full.txt`](llms-full.txt) for the same map with core docs inlined in one fetch. **Agents:** start with [`AGENTS.md`](AGENTS.md) (or [`CLAUDE.md`](CLAUDE.md) if you're Claude Code).++## What this looks like++Say you have a meeting with Alice tomorrow. You want to walk in remembering what she works on, when you last talked, and what's still open between you. Here's what you'd type, and what you'd get back.++**You ask:**++> "What do I need to know before my meeting with Alice tomorrow?"++**Most personal-knowledge tools give you back a list of pages.** Something like:++```+1. people/alice — Alice runs engineering at Acme...+2. meetings/2026-03-15-alice-q1 — Q1 product review with Alice...+3. meetings/2026-01-08-acme-kickoff — Kickoff meeting with Acme team...+4. customers/acme — Acme is a series-B fintech we work with...+5. notes/2026-04-22 — Quick chat with Alice about pricing...+```++Five pages you now have to open and read yourself to actually prepare. The tool found the right material, but it didn't do the work.++**GBrain gives you back the answer, with sources:**++```+Alice runs engineering at Acme (a series-B fintech). You last spoke+on April 22 in a quick pricing chat. Three things are still open+from that conversation:++1. She owes you the security review for the new tier+ (deadline was May 1; no update since).+2. You committed to pricing for a 500-seat tier+ (you sent it April 25; no response yet).+3. She mentioned they're hiring a CISO; you said you'd intro+ someone from your network.++Heads up: nothing's been added to the brain about Alice or Acme+since April 22, six weeks ago. She may have replied through email+or Slack DM, channels the brain doesn't see. Worth asking her to+catch up before assuming any of this is still current.+```++Every claim has a source page behind it. The "heads up" at the end tells you what the brain doesn't know yet, so you can ask Alice about it directly instead of being surprised. The brain just did your meeting prep.++This is the difference between a search engine and a brain. Search finds the pages. The brain reads them for you and writes the answer.+## Two ways to query your brainRaw retrieval (what most personal-knowledge tools ship) and a synthesis layer that gives you an actual answer. They serve different jobs.