What
The warning shown when your stored decision about this machine's hooks is set aside, because the cloud session can write to the files involved, is now a shorter sentence pointing you at /hooks.
Details
- Classifying a hook script now goes through one helper returning unverifiable, reachable by the session, or outside its reach, replacing inline path and digest checks.
- The consent telemetry event name is unchanged.
Evidence
The saved answer about this machine's hooks is ignored here: this cloud session can itself write
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle/hooks
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Choose a sandbox environment touched a line naming /hooks after this was published.
* [MCP](/docs/en/mcp) servers and [command hooks](/docs/en/hooks#command-hook-fields) are separate processes that run unconstrained on the host.sandbox-environments see the edit
Confirmed since
Anthropic's documentation has since written up /hooks, on Configure auto mode.
Two other places on screen that report denials leave out the command or URL: the notice near the input box, such as `bash denied by auto mode · [Data Exfiltration] · /permissions`, gives the tool and the reason, and the **Recently denied**…auto-mode-config see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /hooks, on Configure auto mode.