From 55290e908842dcd7aec8e5222299d5bafa4029f1 Mon Sep 17 00:00:00 2001 From: Garry Tan Date: Wed, 22 Jul 2026 11:10:47 -0700 Subject: [PATCH] docs(tutorial): drop dead --remote flag from company-brain search examples MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit With unknown op flags now a hard error (this PR), the tutorial's `gbrain search ... --remote` invocations would fail: no code path ever read a --remote flag — thin-client installs route shared ops through the remote MCP server automatically. Update the three examples to the flagless form and explain the automatic routing. Co-Authored-By: Claude Fable 5 --- docs/tutorials/company-brain.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/tutorials/company-brain.md b/docs/tutorials/company-brain.md index b2dc98b00..e0d7c1613 100644 --- a/docs/tutorials/company-brain.md +++ b/docs/tutorials/company-brain.md @@ -223,14 +223,16 @@ export GBRAIN_REMOTE_CLIENT_ID= export GBRAIN_REMOTE_CLIENT_SECRET= export GBRAIN_REMOTE_MCP_URL=https://brain.acme-co.com/mcp -gbrain search "performance review" --remote +gbrain search "performance review" ``` +(On a thin-client install every shared op routes through the remote MCP server automatically — no flag needed. The env vars select whose credentials the call uses.) + Alice should see results only from `customers` and `shared`. The performance-review notes live in `internal`, which she's not scoped to read. She shouldn't see them. ```bash # Terminal 2, as Bob (export his credentials similarly) -gbrain search "performance review" --remote +gbrain search "performance review" ``` Bob should see the performance-review notes from `internal`, plus anything related from `shared`. He shouldn't see anything that lives only in `customers`. @@ -514,7 +516,7 @@ The first sync embeds every page, which takes time. Check `gbrain sources status ### "I see a page I shouldn't see" -This shouldn't happen, but if you suspect it, run `gbrain search --remote --json` as the constrained client and inspect the `source_id` field on every returned result. Every row should be in the client's `--federated-read` set. If one isn't, file an issue with the exact slug and source IDs. +This shouldn't happen, but if you suspect it, run `gbrain search --json` as the constrained client (thin-client install, with the client's `GBRAIN_REMOTE_*` env exported) and inspect the `source_id` field on every returned result. Every row should be in the client's `--federated-read` set. If one isn't, file an issue with the exact slug and source IDs. ### "The synthesized answer is wrong"