{"version":"2.1.242","anchor":"a-planner-deciding-hook-by-hook-what-a-cloud-session-gets-pl","canonical_anchor":"a-planner-deciding-hook-by-hook-what-a-cloud-session-gets-pl","heading":"A planner deciding, hook by hook, what a cloud session gets, plus a \/hooks panel for it","tier":"soon","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/a-planner-deciding-hook-by-hook-what-a-cloud-session-gets-pl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### A planner deciding, hook by hook, what a cloud session gets, plus a \/hooks panel for it\n\nA planner decides which of your hooks a cloud session gets, with a \/hooks panel to review it.\n\n**What**\n\nNew code decides for each locally configured hook whether it is offered to a cloud session driven from this machine, and `\/hooks` gained a cloud-session panel to review the decisions. Command hooks are pinned by digest and refused when their script sits somewhere the cloud session can write; HTTP hooks have no script to pin.\n\n**Details**\n\n- A new table classifies each hook event that is not forwarded, surfacing as \"this event happens on this machine, not in the cloud\" or \"this event is not forwarded yet\".\n- No feature flag for this appears in the bundle; the only visible condition is that a cloud-session panel exists, so what makes that panel appear is decided elsewhere.\n- None of these strings exist in 2.1.241.\n\n**Evidence**\n\n`event_container_internal`\n\n- Area: Hooks\n- Names: `\/hooks`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}