Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.242 ·

Per-machine decision about whether cloud sessions may run your hooks

A Hooks settings row lets you decide whether cloud sessions may run this machine's hooks.

Nothing to try yet In Development
JSON All of v2.1.242
Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
HooksArea: what it touches
In DevelopmentKind: in v2.1.242,
What probably matters to youSection of the release

A per-machine consent row exists with on/off/undecided states, part of the disabled device-hooks feature.

What

The Hooks settings screen gains a row for deciding whether cloud sessions are allowed to run hooks configured on this machine. The answer is saved on this machine and shown as on, off, or not yet decided. Until you decide, nothing from this machine is offered to a cloud session.

Details
  • The saved record holds a version, the choice, when it was decided and the hostname, written with owner-only permissions under the name device-hooks-consent, either through the shared storage service or the local config directory.
  • If that consent file itself sits somewhere the cloud session can write to, the saved answer is ignored for that session.
  • A separate settings toggle, "Use this machine's settings in cloud sessions", appears in the settings list but refuses to be switched on from there and points you at the /config panel that shows what would be sent.
  • The hooks row appears only when the dialog is given the matching callback, and the settings toggle is behind a condition satisfied when the machine's forwarding mode is forward. The check that decides overall availability is not resolvable from the build.
Evidence

device-hooks-consent, Decide whether cloud sessions run this machine's hooks\u2026

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundle/hooks
Since it was published

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
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up /hooks, on Configure auto mode.

See this entry in the whole of v2.1.242 →

Feedback