{"version":"2.1.236","anchor":"queued-commands-passed-explicitly-instead-of-read-from-a-glo","canonical_anchor":"queued-commands-passed-explicitly-instead-of-read-from-a-glo","heading":"Queued commands passed explicitly instead of read from a global","tier":"internal","area":"Session State","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/queued-commands-passed-explicitly-instead-of-read-from-a-glo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Queued commands passed explicitly instead of read from a global\n\nPending commands are handed to the input directly, and the status line reads queue depth properly.\n\n**What**\n\nThe queue of commands waiting to run is now handed to the input handlers and prompt components directly rather than fetched from a global, and the task and status display reads its depth from a dedicated queue-length call. One fewer piece of ambient state.\n\n**Evidence**\n\n`getMainThreadQueueLength`\n\n- Area: Session State\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}