{"version":"2.1.293","anchor":"cloud-session-hooks-are-gated-by-an-account-feature-flag","canonical_anchor":"cloud-session-hooks-are-gated-by-an-account-feature-flag","heading":"Sending local hooks to cloud sessions now depends on an account setting","tier":"notice","area":"Hooks","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/cloud-session-hooks-are-gated-by-an-account-feature-flag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Sending local hooks to cloud sessions now depends on an account setting\n\nHooks from your computer are only offered to a `claude --cloud` session when the feature is switched on for your account\n\n**What**\n\nHooks are commands you set up to run automatically at certain points while Claude works. When you start a cloud session with `claude --cloud`, Claude Code can offer the hooks from your computer to that session. It now checks an account-level feature switch first:\n\n- If the answer has not arrived yet, it waits for it.\n\n- If the feature is off for your account, it does not offer your hooks and notes this in its debug output.\n\nThe message reads: \"Hooks from this machine are not offered to this cloud session: the feature is not switched on for your account.\" Before, hooks were offered without any such check.\n\n**Why**\n\nWhether your local hooks reach a cloud session is now decided per account rather than always happening. If your hooks are not running in a cloud session, this switch may be the reason.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}