{"version":"2.1.246","anchor":"cloud-sessions-can-run-this-machine-s-hooks-once-you-have-ag","canonical_anchor":"cloud-sessions-can-run-this-machine-s-hooks-once-you-have-ag","heading":"Cloud sessions can run this machine's hooks, once you have agreed locally","tier":"use","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/cloud-sessions-can-run-this-machine-s-hooks-once-you-have-ag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Cloud sessions can run this machine's hooks, once you have agreed locally\n\nCloud sessions can run your local hooks once you agree on this machine; run \/hooks to decide.\n\n**What**\n\nA new headless path can forward the hooks configured on your machine to a cloud session, but only after you have explicitly accepted on this machine. If the machine is unbound, or consent is declined, unset or unreadable, hook forwarding reports off with a reason. With no stored consent at all, the report tells you to run `\/hooks` locally to decide. Forwarding also requires the feature's own enabled check to pass.\n\n**Details**\n\n- Turning off emits `tengu_device_hooks_headless_off` with the reason and whether this was a reattach.\n- Consent in the \"unset\" state falls back to off rather than prompting.\n\n**Evidence**\n\n`Hooks from this machine are not used in cloud sessions yet: run \/hooks in claude on this machine to decide.`\n\n- Area: Hooks\n- Names: `\/hooks`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 4\/5"}