Cloud sessions can run your local hooks once you agree on this machine; run /hooks to decide.
What's wrong with this entry?
A new headless path can forward the hooks configured on your machine to a cloud session, but only after you have explicitly accepted on this machine. If the machine is unbound, or consent is declined, unset or unreadable, hook forwarding reports off with a reason. With no stored consent at all, the report tells you to run /hooks locally to decide. Forwarding also requires the feature's own enabled check to pass.
- Turning off emits
tengu_device_hooks_headless_offwith the reason and whether this was a reattach. - Consent in the "unset" state falls back to off rather than prompting.
Hooks from this machine are not used in cloud sessions yet: run /hooks in claude on this machine to decide.
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