What
- The internal tool-call ask tracker gains
askSeatWaitMsand asentWithoutAskSeatflag, plus aspeculationparameter and aspeculation.abandon()call threaded through the ask/approve path. This points to a concurrency-limited queue of 'ask seats' controlling how many permission prompts can be in flight (asked) at once. - New functions record when a remote tool call's approval is abandoned (gave up waiting), capturing which input fields described the call, whether it was on the approval leg, and the dispatch epoch.
- New telemetry counters track leg-by-leg timing:
queue_ms,post_ms,reply_wait_ms,total_ms, and posts per leg, plusask_seat_wait_msandsent_without_ask_seat.
Why
This gives more visibility into how long permission prompts wait and whether they get abandoned, which helps diagnose slow or stuck approval flows when many tool calls are requesting permission at once.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding does not say what limit the ask-seat queue enforces or how it visibly changes prompt behavior for a user.