{"version":"2.1.242","anchor":"a-cloud-field-on-hooks-and-rules-for-which-hooks-a-cloud-ses","canonical_anchor":"a-cloud-field-on-hooks-and-rules-for-which-hooks-a-cloud-ses","heading":"A cloud field on hooks, and rules for which hooks a cloud session may use","tier":"soon","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/a-cloud-field-on-hooks-and-rules-for-which-hooks-a-cloud-ses","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### A `cloud` field on hooks, and rules for which hooks a cloud session may use\n\nHook entries accept a cloud setting deciding whether a cloud session may run them.\n\n**What**\n\nHook entries in settings can carry `cloud: \"device\"` or `cloud: \"skip\"`. A hook whose script lives somewhere the cloud session can write, such as the checkout or a synced directory, is withheld unless the entry is explicitly marked `cloud: \"device\"`; `cloud: \"skip\"` keeps it local. Part of the device-hooks subsystem that is switched off in this build.\n\n**Details**\n\n- A `cloud: \"device\"` mark is ignored when it comes from `.claude\/settings.local.json` inside the checkout.\n- Forwarded scripts are pinned by SHA-256 and re-checked before every run; a script that changed, moved or has multiple hard links is refused with a stated reason.\n- Limits: 128 forwarded hook entries, a 180 second registration lease, and roughly 1 MiB of hook input before a PreToolUse call is denied.\n\n**Evidence**\n\n`is marked cloud: \"skip\" (or a value this version does not recognise) and stays on this machine.`\n\n- Area: Hooks\n- Names: `cloud`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}