{"version":"2.1.236","anchor":"the-command-queue-is-now-passed-around-instead-of-being-a-gl","canonical_anchor":"the-command-queue-is-now-passed-around-instead-of-being-a-gl","heading":"The command queue is now passed around instead of being a global","tier":"internal","area":"Session State","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/the-command-queue-is-now-passed-around-instead-of-being-a-gl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### The command queue is now passed around instead of being a global\n\nThe pending command queue is per session now instead of shared across the process.\n\n**What**\n\nPrompt input, queue-edit hotkeys, background loops and agent spawning read the queue of pending commands from an object handed to them rather than from module-level variables, making it per session instead of process-wide. The queue also travels through tool context, and task notifications are enqueued through it.\n\n**Evidence**\n\n`t.messageQueue.enqueuePendingNotification({`\n\n- Area: Session State\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}