Garry's Opinionated OpenClaw/Hermes Agent Brain
TypeScript
Correct the several-people CHANGELOG line for the per-harness binding (GST-363)
garrytan51bcd9ec5b79
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 67c45ca46c..419f9aa03e 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -17,7 +17,7 @@ identifiers and attribution are available in the pre-removal Git revision### Itemized changes- `gbrain setup claude-code|codex --serves one|several`, `--members <id,...>`, `--members-file <file>` (`src/commands/setup.ts`, `src/commands/setup-serves.ts`). Setup stays engine-free: the labelling, the serves read and the bound reads run as children of the launcher. An empty roster refuses `access_serves_roster_empty`.-- On a brain that already serves several people (2+ enabled members, or `access.serves = several`; explicit wins), a plain setup refuses `setup_serves_several` and writes nothing unless an existing `mcp.stdio_member` naming an enabled member binds the connection; naming an owner no longer exempts it. Setup never writes `mcp.stdio_member` on its own: it is brain-wide, so it would bind every stdio MCP session on the host, including the shared sessions of OpenClaw or Hermes. `--stdio-member <member>` (with `--serves several`, claude-code or codex on a local PGLite brain) writes it and says so; it refuses where OpenClaw or Hermes is installed and on a Postgres brain other machines can open, and it is never recorded or replayed by a re-run. A brain setup cannot read refuses `setup_serves_unreadable`.+- On a brain that already serves several people (2+ enabled members, or `access.serves = several`; explicit wins), a plain setup refuses `setup_serves_several` and writes nothing unless an existing `mcp.stdio_member` naming an enabled member binds the connection; naming an owner no longer exempts it. Setup never writes `mcp.stdio_member`, because that key is brain-wide and would bind every stdio MCP session on the host, including the shared sessions of OpenClaw or Hermes. The per-harness `--stdio-member` binding described below takes its place. A brain setup cannot read refuses `setup_serves_unreadable`.- `gbrain access serves` (read-only view) and `gbrain access serves several --members ... [--yes]` (`src/commands/access-serves.ts`): the labelling on its own, preview first. Keys are idempotent on the member id (token `member-<id>`); a key whose file is gone is reported with the revoke step, never re-minted on its own. Key files never go inside a git work tree, symlinks resolved (`access_serves_key_dir_in_git`); a kept key file must hold the live key, and a minted key whose file cannot be written is revoked. An existing rule on `people/<member>/` that anyone else reads is BLOCKED, and the receipt lists people folders no rule covers.- `src/core/access/serves.ts` (new): `brainServes(engine)`, the one read of whether a brain serves several people.- `src/commands/auth-mint.ts` (new): the token mint `gbrain auth create` used inline, shared with the labelling; `auth create` output is unchanged.