Skip to content

Garry's Opinionated OpenClaw/Hermes Agent Brain

TypeScript
1.9 KB
Raw Blame

On a brain that serves several people (two or more enabled members, or config access.serves = several; a brain pinned access.serves one never does), a remote read through a connection bound to no member (an access token, an OAuth client, or a stdio server with no member binding) is now refused with requester_scope_required before any work; whoami, get_brain_identity, get_status_snapshot, search_modes, get_health and a non-admin key's own get_job / wait_job still answer. A connection that existed when the brain started serving several people (config access.serves_since, set once, or this upgrade) reads for 14 more days with _meta.access.requester_scope naming the date and the fix; one created later is refused at once. Bind each connection to the person it serves: gbrain auth rescope --token <name>|--client <id> --member <id>; a stdio harness only one person uses, gbrain setup claude-code|codex --stdio-member <id>; a harness several people talk to, one --member key per person over gbrain serve --http. A shared agent names the person per call (--may-act-for), and --reads-unscoped --yes marks one credential to read unscoped on purpose. gbrain auth create and gbrain auth register-client refuse an unbound credential on such a brain (credential_scope_required); gbrain doctor fails unscoped_shared_reads per unbound credential and gbrain post-upgrade lists them. gbrain doctor also fails shared_stdio_binding when mcp.stdio_member is set on a host where OpenClaw or Hermes is installed and the brain serves several people; a hermes on PATH counts as Hermes only when it is a script. Hosted brains set access.requester_scope_enforce false, which turns every refusal into the notice. Member-bound credentials (the owner's included), attested calls, a one-person brain and the local CLI see no change; writes are not affected.