claude-code: remove from or restore to only an agent account's own home
mesh/merge-gate pass: builds claude-code → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh, merge-check-typescript.sh): main's version judged it; the change's judges the pull r…
mesh/delivery delivered

Removing a rule from the operator's own home changes what their sessions
obey as surely as placing one: an agent could remove the rule that
constrains it (hq issue 340).
This commit is contained in:
jochen
2026-10-09 09:51:18 +02:00
parent 3677af6079
commit d984eb84d6
5 changed files with 66 additions and 7 deletions
+3 -1
View File
@@ -127,7 +127,9 @@ The home scope is registered through the tools **only where the home belongs to
the home is the operator's own `~/.claude`, whose rules and skills load in every session the operator starts, and
the tool runner cannot tell the operator from an agent: refused there, and for any other node, whose home cannot be
judged from here (call that node's own tool). A home item on the bus is never placed in the operator's own home,
and what the module placed there before is taken back unless the person changed it. Where it is taken:
and what the module placed there before is taken back unless the person changed it. `claude_code_home_remove` and
`claude_code_home_restore` are refused the same way wherever the home is the operator's own: removing a rule changes
what a session obeys as surely as placing one. Where it is taken:
- for each kind — `skill`, `agent`, `command`, `output_style`, `instructions` — `claude_code_<kind>_list`,
`_register`, `_unregister`. A skill is its files (`files`, or `content` for a lone SKILL.md);