What
When a cloud session is offered this machine's hooks, a stored answer is ignored if the session could write the file holding it. That check can now fail outright, producing a new result telling you the file could not be located to check who can write it and asking you to decide in /hooks.
Details
- Only applies on the cloud-session hooks path.
- The switched-off message is now the actual reason truncated to 200 characters; the previous fixed text about device binding likely being off was removed.
- Registration outcomes
consent_distrusted,dormantandfailedare now reported separately in telemetry. - Answering "not now" now clears the session's pins and standing rather than only disarming.
Evidence
could not be located to check who can write it. Decide for this session in /hooks., consent_distrusted
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.