Cloud sessions could trigger hooks that run on your own machine, but the path is hard-disabled.
A complete device-hook subsystem with path translation exists; its session creator returns false unconditionally.
What's wrong with this entry?
A large new subsystem lets the machine you launch claude --cloud from register its local hooks with a cloud session and then run them locally when the cloud session fires them, translating paths between the container and your machine. It cannot run here: the code that creates the session is behind a helper that unconditionally returns false in this build, so none of its notices can appear.
- Includes lease-based registration, a servicer that executes hooks locally, replay and dedup caches, and staging of verified copies of hook scripts.
- Also skipped for view-only sessions even if the gate were on.
- The worker side of this (
register_device_hooks) already existed in 2.1.241; the machine-side half is new.
[deviceHooks] device hook session created for this attach
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
SessionEnd hooks lose the
bypass_permissions_disabledreasonBoth mention hook
-
v2.1.236
Hooks and Ctrl-C go quiet once shutdown has started
Both mention hook
-
v2.1.236
Shutdown seals transcript writes and gives SessionEnd hooks more time
Both mention hook