{"version":"2.1.271","anchor":"task-queue-dispatch-gains-a-deferredtoolusepending-hook-and","canonical_anchor":"task-queue-dispatch-gains-a-deferredtoolusepending-hook-and","heading":"Task-queue dispatch gains a deferredToolUsePending hook and startGate.admits check","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/task-queue-dispatch-gains-a-deferredtoolusepending-hook-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Task-queue dispatch gains a deferredToolUsePending hook and startGate.admits check\n\nTask queue dispatch gains internal hooks for deferred tool use and a new admission gate\n\n**Unclear.** The finding does not say what triggers deferredToolUsePending or startGate.admits to actually withhold something in practice.\n\n**What**\n\nThe internal coordinator that decides which queued tasks to run next has two new controls:\n\n- a `deferredToolUsePending` callback, which can report whether a tool call is being held back (it defaults to always answering no)\n\n- a `startGate.admits` check, which now filters the list of follow-up tasks before they are added to the next batch to run\n\n**Why**\n\nThis is internal plumbing for how Claude Code schedules and dispatches queued work. It does not change what users see directly, but it gives the scheduler finer control over when queued tool calls and follow-up tasks are allowed to proceed.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}