Hooks are looked up per session rather than from global state; your hooks fire the same.
What's wrong with this entry?
Hook presence checks, SessionEnd dispatch, stop-prompt registration, the permission-request check and the StopFailure dispatcher all now query a per-session hook registry rather than reading hooks out of global app state. No change to how your configured hooks fire.
- The hook runner takes a
sessionHooksargument with ahas(id, event)lookup. - Tool aliases used for matcher filtering come from an optional
getToolAliases()callback instead of the tool permission context. - Teammate setup registers its Stop hook via
addFunctionHookrather than a global registration helper. - A React error was added for using the registry hook outside its provider.
useSessionHooksRegistry cannot be called outside of an <AppStateProvider />, hook_event_name: "StopFailure", addFunctionHook
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