A planner decides which of your hooks a cloud session gets, with a /hooks panel to review it.
Per-hook cloud offer decisions with digest pinning and a /hooks cloud panel belong to the disabled device-hooks path.
What's wrong with this entry?
New 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.
- 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".
- 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.
- None of these strings exist in 2.1.241.
event_container_internal
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
SessionEnd hooks lose the
bypass_permissions_disabledreasonBoth mention hook
-
v2.1.236
Hooks and Ctrl-C go quiet once shutdown has started
Both mention hook
-
v2.1.236
Shutdown seals transcript writes and gives SessionEnd hooks more time
Both mention hook