Non-canceling follow-up messages can cause an active request to be skipped
What version of the IDE extension are you using?
v26.715.31925
What subscription do you have?
pro-20x
Which IDE are you using?
VS Code
What platform is your computer?
Linux 5.15.0-139-generic x86_64 x86_64
What issue are you seeing?
Summary
A short follow-up message with no cancellation or replacement intent can cause Codex to skip a previously submitted implementation request.
What steps can reproduce the bug?
Minimal reproduction
- Send Codex a clear implementation request that requires editing files.
- Before the implementation begins or completes, send a short, unrelated follow-up such as:
``text``
hello
- Observe the response.
Observed behavior
Codex treats the follow-up greeting as if it replaced the active implementation request. The original request is not executed, and the assistant responds only to the greeting.
Expected behavior
A non-canceling follow-up such as hello, a status question, or another brief conversational message should not silently replace an active implementation request.
Codex should either:
- continue the active request while replying appropriately to the follow-up; or
- explicitly state that it is interpreting the new message as a replacement and ask for confirmation if that interpretation is uncertain.
The original task should only be abandoned after an explicit cancellation, replacement, or unambiguous change of scope.
Impact
This can make requested work appear to have been accepted but then silently skipped. In longer implementation workflows, users may not notice the skipped request until later.
Example
An implementation plan to update several repository documentation and contract files was submitted. A subsequent hello message was interpreted as replacing that plan, and no edits or validation were performed.
Additional notes
The underlying cause is not known. The report concerns externally observable conversation/task-routing behavior rather than a confirmed backend implementation detail.
What is the expected behavior?
_No response_
Additional information
_No response_