{"version":"2.1.280","anchor":"permission-prompt-queueing-gets-an-explicit-ask-seat-wait","canonical_anchor":"permission-prompt-queueing-gets-an-explicit-ask-seat-wait","heading":"Permission-prompt queueing gets an 'ask seat' wait budget and richer telemetry","tier":"internal","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/permission-prompt-queueing-gets-an-explicit-ask-seat-wait","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Permission-prompt queueing gets an 'ask seat' wait budget and richer telemetry\n\nTool-call approval tracking now measures how long requests wait for a limited 'ask seat' and whether they gave up\n\n**Unclear.** The finding does not say what limit the ask-seat queue enforces or how it visibly changes prompt behavior for a user.\n\n**What**\n\n- The internal tool-call ask tracker gains `askSeatWaitMs` and a `sentWithoutAskSeat` flag, plus a `speculation` parameter and a `speculation.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.\n\n- 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.\n\n- New telemetry counters track leg-by-leg timing: `queue_ms`, `post_ms`, `reply_wait_ms`, `total_ms`, and posts per leg, plus `ask_seat_wait_ms` and `sent_without_ask_seat`.\n\n**Why**\n\nThis 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.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}