A consent screen explains what letting cloud sessions run your local hooks means.
A three-answer consent screen for forwarding hooks is built as part of the disabled device-hooks feature.
What's wrong with this entry?
A new screen asks whether hooks from your own settings (user settings.json, a checkout's settings.local.json, or a --settings file) may run on this machine when a cloud session asks for them. It offers three answers and explains that whatever a hook returns, such as a block reason or added context, becomes part of the cloud session's transcript.
- The answer is stored per machine; other
claude --cloudterminals already running keep the answer they started with. - Hook forwarding itself shipped in 2.1.241, with
CLAUDE_CODE_DISABLE_HOOK_FORWARDINGto turn it off and a server-side flag path that reportshook_forwarding_disabled: flag_off. This build adds the consent dialog on top. - No slash command in this build opens the screen, and the code that builds its rows passes a placeholder session identifier, so how a user reaches it is unclear.
Yes, run this machine's hooks for cloud sessions
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