{"version":"2.1.295","anchor":"session-end-handling-in-queued-batch-start","canonical_anchor":"session-end-handling-in-queued-batch-start","heading":"Fix for queued commands when a session is ending","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/session-end-handling-in-queued-batch-start","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Fix for queued commands when a session is ending\n\nA check that decides whether the first queued command waits before starting no longer breaks when a session end has been requested\n\n**What**\n\nClaude Code keeps a queue of commands waiting to run. Before the first one in line starts, it checks whether that command should wait. When the session had been asked to end, this check pointed at a value that did not exist. It now runs a proper check in that case, and otherwise asks whether the first command should wait before starting, as before.\n\nClaude Code can also now report which commands are parked, meaning set aside and not yet run.\n\n**Why**\n\nThese are internal fixes to how queued commands are handled as a session winds down, mainly in remote sessions or sessions driven by another program through the SDK (the kit developers use to run Claude Code from their own code).\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}