{"version":"2.1.236","anchor":"some-hook-events-take-a-separate-dispatch-path","canonical_anchor":"some-hook-events-take-a-separate-dispatch-path","heading":"Some hook events take a separate dispatch path","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/some-hook-events-take-a-separate-dispatch-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Some hook events take a separate dispatch path\n\nSix hook events now wait on a readiness step before running; the rest are unchanged.\n\n**What**\n\nSix 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.\n\n**Details**\n\n- The split is unconditional; there is no flag selecting between the two paths.\n- What the readiness step waits for is not determined by anything in this branch.\n\n**Evidence**\n\n`if (!DIw.has(e.hookInput.hook_event_name)) {`\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}