{"version":"2.1.242","anchor":"consent-screen-explaining-what-forwarding-your-hooks-to-a-cl","canonical_anchor":"consent-screen-explaining-what-forwarding-your-hooks-to-a-cl","heading":"Consent screen explaining what forwarding your hooks to a cloud session means","tier":"soon","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/consent-screen-explaining-what-forwarding-your-hooks-to-a-cl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Consent screen explaining what forwarding your hooks to a cloud session means\n\nA consent screen explains what letting cloud sessions run your local hooks means.\n\n**What**\n\nA new screen asks whether hooks from your own settings (user `settings.json`, a checkout's `settings.local.json`, or a `--settings` file) may run on this machine when a cloud session asks for them. It offers three answers and explains that whatever a hook returns, such as a block reason or added context, becomes part of the cloud session's transcript.\n\n**Details**\n\n- The answer is stored per machine; other `claude --cloud` terminals already running keep the answer they started with.\n- Hook forwarding itself shipped in 2.1.241, with `CLAUDE_CODE_DISABLE_HOOK_FORWARDING` to turn it off and a server-side flag path that reports `hook_forwarding_disabled: flag_off`. This build adds the consent dialog on top.\n- No slash command in this build opens the screen, and the code that builds its rows passes a placeholder session identifier, so how a user reaches it is unclear.\n\n**Evidence**\n\n`Yes, run this machine's hooks for cloud sessions`\n\n- Area: Hooks\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}