{"version":"2.1.242","anchor":"plain-language-reasons-why-a-local-hook-is-not-offered-to-a-","canonical_anchor":"plain-language-reasons-why-a-local-hook-is-not-offered-to-a-","heading":"Plain-language reasons why a local hook is not offered to a cloud session","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/plain-language-reasons-why-a-local-hook-is-not-offered-to-a-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Plain-language reasons why a local hook is not offered to a cloud session\n\nLocal hooks held back from a cloud session now tell you in plain words why.\n\n**What**\n\nWhen your local hooks are forwarded to a cloud session, each one that is held back now says why in prose rather than being quietly dropped.\n\n**Details**\n\n- Reasons include: after-edit hooks stay on this machine; only command and http hook types can be forwarded; a matcher written as a pattern rather than a plain list is refused; a script living somewhere the cloud session can write on this machine is held unless pinned; duplicates and registrations past the cap are dropped; an entry marked `cloud: \"skip\"` is skipped.\n- Standing states get their own wording too: paused, declined, disabled, unsupported, invalid and stale registrations.\n\n**Evidence**\n\n`only command and http hooks can run for a cloud session`\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}