You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Non-steered queued tasks sometimes randomly spontaneously become "steered", stopping any previously on-going tasks #17876
Spontaneous unprovoked undesired unallowed steering of queued tasks - forcefully stops ongoing tasks, forcing its way through the queue even without me clicking on "Steer" at all
What steps can reproduce the bug?
Start a long task via prompt in a thread
Add to the Codex built in queue of the same thread another prompt while previous task is still running, as expected it is not given any attention because it was successfully queued and I did not click on Steer
After some time, sometimes spontaneously the queued task would become steered even if I did not click on steer, causing an unexpected stop to the previous on-going task in the middle of work, leaving its progress in unknown state of completion possibly corrupt (ungraceful stop)
What is the expected behavior?
If a queued prompt is queued, it should remain queued until previous work has been done and not randomly force its way through the queue, and even if that is done the previous queued work that got interrupted should not stop.
Additional information
While this is relatively rare (not super rare, it happens multiple time in an hour of work), it does reproduce significantly more often when multiple VS Code instances running Codex extension thread doing work in parallel.
This also reproduce more often when nearing the auto-compacting stage
This started recently, I don't remember this always being the case, but may be related to the fact that I started working with parallel codex threads on the same machine doing work at the same time at once.
Activity
github-actions commentedon Apr 15, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
korenmic commentedon Apr 15, 2026
I also want to add that when this happens, the history would look like this:
It looks strange in that order.