{"version":"2.1.246","anchor":"headless-runs-no-longer-report-themselves-busy-while-blocked","canonical_anchor":"headless-runs-no-longer-report-themselves-busy-while-blocked","heading":"Headless runs no longer report themselves busy while blocked on a prompt","tier":"notice","area":"Headless Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/headless-runs-no-longer-report-themselves-busy-while-blocked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Headless runs no longer report themselves busy while blocked on a prompt\n\nHeadless runs waiting on a permission prompt no longer falsely report themselves as busy.\n\n**What**\n\nIn print mode, the loop that drains queued work used to transition the session to `running` even when it was sitting in `requires_action` with a permission or dialog request outstanding. It now skips that transition and instead clears turn-scoped metadata once per drain, so stale post-turn summary and recap data goes away without the session falsely reporting as busy.\n\n**Details**\n\n- The blocked condition is state `requires_action` plus at least one pending permission or user-dialog request.\n- The same drain now also hands the dequeued batch to the queue as the in-flight batch, which previously happened only on the interactive path.\n\n**Evidence**\n\n`requires_action`\n\n- Area: Headless Mode\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}