{"version":"2.1.242","anchor":"hooks-running-on-your-machine-on-behalf-of-a-cloud-session-s","canonical_anchor":"hooks-running-on-your-machine-on-behalf-of-a-cloud-session-s","heading":"Hooks running on your machine on behalf of a cloud session, switched off in this build","tier":"soon","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/hooks-running-on-your-machine-on-behalf-of-a-cloud-session-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Hooks running on your machine on behalf of a cloud session, switched off in this build\n\nCloud sessions could trigger hooks that run on your own machine, but the path is hard-disabled.\n\n**What**\n\nA large new subsystem lets the machine you launch `claude --cloud` from register its local hooks with a cloud session and then run them locally when the cloud session fires them, translating paths between the container and your machine. It cannot run here: the code that creates the session is behind a helper that unconditionally returns false in this build, so none of its notices can appear.\n\n**Details**\n\n- Includes lease-based registration, a servicer that executes hooks locally, replay and dedup caches, and staging of verified copies of hook scripts.\n- Also skipped for view-only sessions even if the gate were on.\n- The worker side of this (`register_device_hooks`) already existed in 2.1.241; the machine-side half is new.\n\n**Evidence**\n\n`[deviceHooks] device hook session created for this attach`\n\n- Area: Hooks\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}