Non-steered queued tasks sometimes randomly spontaneously become "steered", stopping any previously on-going tasks

[korenmic]

What version of the IDE extension are you using?

26.409.20454

What subscription do you have?

Pro 100

Which IDE are you using?

VS Code

What platform is your computer?

Windows 11 25H2 26200.8037

What issue are you seeing?

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?

1. Start a long task via prompt in a thread
2. 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
3. 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.

[github-actions]

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• Queued prompts behave like steer prompts; multiple queued prompts sent simultaneously #17285

Powered by Codex Action

[korenmic]

I also want to add that when this happens, the history would look like this:

• ME: Long prompt A
• Codex: Partial completion, just "run commands" collapsible outputs, no summary
• Codex: Full response to prompt B # The rogue queued task that interrupted prompt A and broke through the queue without steering
• "ME" : prompt B # This appears after its response instead of before.

It looks strange in that order.