{"version":"2.1.280","anchor":"remote-tool-calls-now-queue-behind-a-per-host-ask-seat-lim","canonical_anchor":"remote-tool-calls-now-queue-behind-a-per-host-ask-seat-lim","heading":"Remote permission requests now queue behind a per-host limit","tier":"notice","area":"Remote Tools","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/remote-tool-calls-now-queue-behind-a-per-host-ask-seat-lim","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Remote permission requests now queue behind a per-host limit\n\nPermission requests to a remote host now queue behind a configurable limit, showing waiting\/sending status instead of firing all at once\n\n**What**\n\nWhen Claude Code needs to ask for permission on a remote host, it no longer fires every request at once. A new gating layer limits how many permission asks can be in flight to a given host at the same time, using a `limits.pending_asks_max` setting you can configure per host.\n\n- New calls that arrive while the limit is reached now wait their turn instead of being sent immediately.\n\n- Two new status messages are shown while a request waits: one while an earlier call to that host still needs a permission answer, and one while the request is actively being sent.\n\n**Why**\n\nThis keeps a remote host (or another agent sharing it) from being hit with a pile of simultaneous permission prompts, and gives you a clear status message explaining why a request is waiting rather than leaving it looking stuck.\n\n- Area: Remote Tools\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}