Garry's Opinionated OpenClaw/Hermes Agent Brain
TypeScript
Shorten the several-people setup paragraph so llms-full.txt stays within its size budget (GST-363)
garrytanb1abb4826476
diff --git a/INSTALL_FOR_AGENTS.md b/INSTALL_FOR_AGENTS.mdindex 1b7d256274..dbca3b46bf 100644--- a/INSTALL_FOR_AGENTS.md+++ b/INSTALL_FOR_AGENTS.md@@ -148,15 +148,12 @@ whenever the user gives one. Capturethem. A coded refusal (`setup_owner_conflict`, `setup_hosted_connection`) meansanother owner or a hosted brain holds the target; follow its `fix`.When the brain will answer several people (a team bot, a shared channel), ask the-user who they are and add `--serves several --members <id,...>`: each person gets-a member, a folder `people/<member>/` only they read and a key bound to them-(`~/.gbrain/member-keys/<member>.key`, 0600; relay paths, never key values), and-the receipt proves no member reads another member's folder.-`setup_serves_several` means the brain already serves several people and the-connection would be bound to nobody: rerun with its fix. Add `--stdio-member <member>`-(claude-code, codex) only when one person alone uses that harness; it binds that entry alone.-Doctor's `unlabeled_people_folders`-names any person's folder still without a rule.+user who they are and add `--serves several --members <id,...>`: each gets a member,+a folder `people/<member>/` only they read and a bound key+(`~/.gbrain/member-keys/<member>.key`; relay paths, never keys). On+`setup_serves_several`, rerun with its fix. Add `--stdio-member <member>`+(claude-code, codex) only for a harness one person uses. Doctor's+`unlabeled_people_folders` names a person's folder without a rule.`--remove` undoes only what setup wrote. Guide:[docs/guides/setup.md](docs/guides/setup.md). Otherwise:diff --git a/llms-full.txt b/llms-full.txtindex f6e1a961bb..232a42fe1e 100644--- a/llms-full.txt+++ b/llms-full.txt@@ -2840,15 +2840,12 @@ whenever the user gives one. Capturethem. A coded refusal (`setup_owner_conflict`, `setup_hosted_connection`) meansanother owner or a hosted brain holds the target; follow its `fix`.When the brain will answer several people (a team bot, a shared channel), ask the-user who they are and add `--serves several --members <id,...>`: each person gets-a member, a folder `people/<member>/` only they read and a key bound to them-(`~/.gbrain/member-keys/<member>.key`, 0600; relay paths, never key values), and-the receipt proves no member reads another member's folder.-`setup_serves_several` means the brain already serves several people and the-connection would be bound to nobody: rerun with its fix. Add `--stdio-member <member>`-(claude-code, codex) only when one person alone uses that harness; it binds that entry alone.-Doctor's `unlabeled_people_folders`-names any person's folder still without a rule.+user who they are and add `--serves several --members <id,...>`: each gets a member,+a folder `people/<member>/` only they read and a bound key+(`~/.gbrain/member-keys/<member>.key`; relay paths, never keys). On+`setup_serves_several`, rerun with its fix. Add `--stdio-member <member>`+(claude-code, codex) only for a harness one person uses. Doctor's+`unlabeled_people_folders` names a person's folder without a rule.`--remove` undoes only what setup wrote. Guide:[docs/guides/setup.md](docs/guides/setup.md). Otherwise: