Headless runs waiting on a permission prompt no longer falsely report themselves as busy.
What's wrong with this entry?
In 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.
- The blocked condition is state
requires_actionplus at least one pending permission or user-dialog request. - 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.
requires_action
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.219
Headless text output recovers the last full assistant message on an incomplete run
Both mention headless mode
-
v2.1.227
Headless mode reports fatal errors instead of dying quietly
Both mention headless mode
-
v2.1.248
Headless loop guards against missing stream event fields
Both mention headless mode