A Hooks settings row lets you decide whether cloud sessions may run this machine's hooks.
A per-machine consent row exists with on/off/undecided states, part of the disabled device-hooks feature.
What's wrong with this entry?
The Hooks settings screen gains a row for deciding whether cloud sessions are allowed to run hooks configured on this machine. The answer is saved on this machine and shown as on, off, or not yet decided. Until you decide, nothing from this machine is offered to a cloud session.
- The saved record holds a version, the choice, when it was decided and the hostname, written with owner-only permissions under the name
device-hooks-consent, either through the shared storage service or the local config directory. - If that consent file itself sits somewhere the cloud session can write to, the saved answer is ignored for that session.
- A separate settings toggle, "Use this machine's settings in cloud sessions", appears in the settings list but refuses to be switched on from there and points you at the
/configpanel that shows what would be sent. - The hooks row appears only when the dialog is given the matching callback, and the settings toggle is behind a condition satisfied when the machine's forwarding mode is
forward. The check that decides overall availability is not resolvable from the build.
device-hooks-consent, Decide whether cloud sessions run this machine's hooks\u2026
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