Each hook can carry a cloud field choosing whether cloud sessions may run it.
What's wrong with this entry?
Each hook entry in settings can now carry a cloud field. device offers that hook to a cloud session even when its script lives somewhere the session could write to or cannot be pinned to fixed contents; skip never offers it. Leaving it out keeps the default, where only pinned, unwritable command hooks are offered. An unrecognised value is read as skip.
- The setting applies only to that one hook entry in that one settings scope, not to hooks generally.
- The message that forwards a hook to a cloud session now carries a matching
author_opt_inflag recording that the hook was explicitly opted in. - The description of pinning changed: the machine re-verifies the script's bytes before every run, rather than capturing them once.
- Forwarding as a whole still depends on a server-side feature flag and on policy; when the flag is off, the reason reported is
hook_forwarding_disabled: flag_off.
'skip': never offer it to 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