Unclear It is not clear whether this dialog is shown to everyone or only when a separate setting allows it.
What
Hooks are commands that run automatically at certain moments, such as when Claude uses a tool. Claude Code can run your machine's hooks for cloud sessions, sessions running on a remote machine, and several messages about this changed:
- Consent dialog: the title is now "Run this machine's hooks for cloud sessions?", where it used to be "Let cloud sessions started from this machine run its hooks?". The answers are "Yes, run hooks for cloud sessions", "No, don't run hooks for cloud sessions" and "Not now". It points to
/hooksfor changing your choice, and warns that hooks run here only while Claude Code stays connected and answers in time, and that a hook which blocks a command here won't block it there. - Older copies: the warning for a hook that is an older copy now ends "the cloud will not run it. Update it." instead of "Update it from dotfiles." This case may now be reported the same way as hooks that run on this machine instead.
- Hooks that would run in the cloud session: this warning is shorter and no longer gives a hook count or a long explanation.
- Changed hook files: the warning now reads "changed since it was registered for this cloud session, so it won't run. If you edited it, restart claude --cloud. If not, check the file."
/hooks: hooks that are not currently registered show "not registered right now; reopen /hooks to check again".
Why
The wording is shorter and spells out that local hooks are best effort for cloud sessions: they may not run, and they cannot block a command in the cloud.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not clear whether this dialog is shown to everyone or only when a separate setting allows it.