Under the hood
Useful2 Signal3
Six hook events now wait on a readiness step before running; the rest are unchanged.
What's wrong with this entry?
Anonymous. No account, no email.
What
Six hook events, PreToolUse, PermissionRequest, UserPromptSubmit, UserPromptExpansion, TaskCompleted and TeammateIdle, are handled by a new branch that waits on a readiness step before running hooks. Every other event returns early from that branch and goes through the previous path.
Details
- The split is unconditional; there is no flag selecting between the two paths.
- What the readiness step waits for is not determined by anything in this branch.
Evidence
if (!DIw.has(e.hookInput.hook_event_name)) {
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.238
Reconnecting an SDK host swaps its hooks in and settles the ones left waiting
Both mention hook
-
v2.1.238
Hook callbacks remember which host created them
Both mention hook