What issue are you seeing?

This is a serious issue in how steering works (for comparison, this is exactly the opposite of how it works in Claude Code).

What steps can reproduce the bug?

• You give Codex some complicated work to perform, such as a bug fix. It's in the middle - half way through.
• Codex is working and producing thinking tokens
• You notice it pointing out something you did not expect to find in your code, such as a dependency in a Gemfile for a rails app, and so you say:
• I don't think we even use gem xyz in code
• Codex COMPLETELY steers off - it should take my comment as an addendum to current work, not a 'Oh - I've been asked to do something COMPLETELY different'
• Codex then begins to discover and answer your question - it then ends with
• Yes you're right, we don't use this... and nothing. It just stops.
• I then have to say Continue finishing the work and remove this gem then

What is the expected behavior?

I expect codex to take my commentary as extra information, additional work, hints, suggestions etc - not as a new thread of work. It should infer that we want to remove this gem as part of the current work.

It wasn't like this earlier as far as I can tell when it was in beta. I think in a recent commit I saw this behavior change into 'separating threads for steering' and that may have broken intended behavior.

Additional information

Claude Code for instance will always take your steer as a 'by the way' or 'check this too..' and you can see it at times responding back as You're absolutely right, I'll look into this. Let me first finish XYZ and I'll look into this.... In the above example, it would infer that we should also remove this gem as part of the bug fix.