{"version":"2.1.242","anchor":"hooks-can-opt-in-or-out-of-running-for-cloud-sessions-per-en","canonical_anchor":"hooks-can-opt-in-or-out-of-running-for-cloud-sessions-per-en","heading":"Hooks can opt in or out of running for cloud sessions, per entry","tier":"use","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/hooks-can-opt-in-or-out-of-running-for-cloud-sessions-per-en","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Hooks can opt in or out of running for cloud sessions, per entry\n\nEach hook can carry a cloud field choosing whether cloud sessions may run it.\n\n**What**\n\nEach 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`.\n\n**Details**\n\n- The setting applies only to that one hook entry in that one settings scope, not to hooks generally.\n- The message that forwards a hook to a cloud session now carries a matching `author_opt_in` flag recording that the hook was explicitly opted in.\n- The description of pinning changed: the machine re-verifies the script's bytes before every run, rather than capturing them once.\n- 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`.\n\n**Evidence**\n\n`'skip': never offer it to cloud sessions.`\n\n- Area: Hooks\n- Names: `cloud`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}