From cdf0e71d871626d6e1869e06a3ae628586d92592 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 9 Oct 2026 09:51:57 +0200 Subject: [PATCH] Issue 340: removing from or restoring to the operator's own home is refused too --- .../01-diagnosis.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/04-ISSUES/340-an-agent-can-plant-a-hook-in-every-agent-session-on-the-mesh/01-diagnosis.md b/04-ISSUES/340-an-agent-can-plant-a-hook-in-every-agent-session-on-the-mesh/01-diagnosis.md index f0828ac3..c883c468 100644 --- a/04-ISSUES/340-an-agent-can-plant-a-hook-in-every-agent-session-on-the-mesh/01-diagnosis.md +++ b/04-ISSUES/340-an-agent-can-plant-a-hook-in-every-agent-session-on-the-mesh/01-diagnosis.md @@ -81,6 +81,8 @@ The fix, in the module: - a home item on the bus is never placed in the operator's own home, whoever put it there, and what the module placed there before is taken back unless the person changed it; - every node a call names is judged before anything is put, and a list naming one refused node is refused whole. +- removing an item of the home, or putting one back (`claude_code_home_remove`, `claude_code_home_restore`), is + refused the same way wherever the home is the operator's own, because an agent could remove a rule that constrains it. Until ADR 0266's account is switched on, no node has an agent account of its own, so the home scope is refused everywhere. Nothing is registered at the home scope today.