What version of the Codex App are you using (From “About Codex” dialog)?
Frequency observed: failed twice, succeeded on the third attempt
What subscription do you have?
n the Codex desktop app on macOS, messages sent while a task is still running are not reliably delivered through the “Steer” action. When Codex asked me for a short confirmation, I entered my response and clicked “Steer.” The message failed and changed to a “Retry” state. Clicking “Retry” repeatedly did not send it. I had to delete the failed message and enter the same response again. This happened twice in the attached recording. The message was only accepted on the third attempt, after which Codex resumed the task normally. Expected behavior:Clicking “Steer” should immediately deliver the queued message to the active task. Actual behavior:The message becomes stuck in a failed “Retry” state, and retrying does not recover it. The user must delete and resubmit the message multiple times.
What platform is your computer?
n the Codex desktop app on macOS, messages sent while a task is still running are not reliably delivered through the “Steer” action. When Codex asked me for a short confirmation, I entered my response and clicked “Steer.” The message failed and changed to a “Retry” state. Clicking “Retry” repeatedly did not send it. I had to delete the failed message and enter the same response again. This happened twice in the attached recording. The message was only accepted on the third attempt, after which Codex resumed the task normally. Expected behavior:Clicking “Steer” should immediately deliver the queued message to the active task. Actual behavior:The message becomes stuck in a failed “Retry” state, and retrying does not recover it. The user must delete and resubmit the message multiple times.
What issue are you seeing?
n the Codex desktop app on macOS, messages sent while a task is still running are not reliably delivered through the “Steer” action.
When Codex asked me for a short confirmation, I entered my response and clicked “Steer.” The message failed and changed to a “Retry” state. Clicking “Retry” repeatedly did not send it. I had to delete the failed message and enter the same response again.
This happened twice in the attached recording. The message was only accepted on the third attempt, after which Codex resumed the task normally.
Expected behavior:Clicking “Steer” should immediately deliver the queued message to the active task.
Actual behavior:The message becomes stuck in a failed “Retry” state, and retrying does not recover it. The user must delete and resubmit the message multiple times.
What steps can reproduce the bug?
n the Codex desktop app on macOS, messages sent while a task is still running are not reliably delivered through the “Steer” action.
When Codex asked me for a short confirmation, I entered my response and clicked “Steer.” The message failed and changed to a “Retry” state. Clicking “Retry” repeatedly did not send it. I had to delete the failed message and enter the same response again.
This happened twice in the attached recording. The message was only accepted on the third attempt, after which Codex resumed the task normally.
Expected behavior:Clicking “Steer” should immediately deliver the queued message to the active task.
Actual behavior:The message becomes stuck in a failed “Retry” state, and retrying does not recover it. The user must delete and resubmit the message multiple times.
What is the expected behavior?
n the Codex desktop app on macOS, messages sent while a task is still running are not reliably delivered through the “Steer” action.
When Codex asked me for a short confirmation, I entered my response and clicked “Steer.” The message failed and changed to a “Retry” state. Clicking “Retry” repeatedly did not send it. I had to delete the failed message and enter the same response again.
This happened twice in the attached recording. The message was only accepted on the third attempt, after which Codex resumed the task normally.
Expected behavior:Clicking “Steer” should immediately deliver the queued message to the active task.
Actual behavior:The message becomes stuck in a failed “Retry” state, and retrying does not recover it. The user must delete and resubmit the message multiple times.
Additional information
n the Codex desktop app on macOS, messages sent while a task is still running are not reliably delivered through the “Steer” action.
When Codex asked me for a short confirmation, I entered my response and clicked “Steer.” The message failed and changed to a “Retry” state. Clicking “Retry” repeatedly did not send it. I had to delete the failed message and enter the same response again.
This happened twice in the attached recording. The message was only accepted on the third attempt, after which Codex resumed the task normally.
Expected behavior:Clicking “Steer” should immediately deliver the queued message to the active task.
Actual behavior:The message becomes stuck in a failed “Retry” state, and retrying does not recover it. The user must delete and resubmit the message multiple times.
What version of the Codex App are you using (From “About Codex” dialog)?
Frequency observed: failed twice, succeeded on the third attempt
What subscription do you have?
n the Codex desktop app on macOS, messages sent while a task is still running are not reliably delivered through the “Steer” action. When Codex asked me for a short confirmation, I entered my response and clicked “Steer.” The message failed and changed to a “Retry” state. Clicking “Retry” repeatedly did not send it. I had to delete the failed message and enter the same response again. This happened twice in the attached recording. The message was only accepted on the third attempt, after which Codex resumed the task normally. Expected behavior:Clicking “Steer” should immediately deliver the queued message to the active task. Actual behavior:The message becomes stuck in a failed “Retry” state, and retrying does not recover it. The user must delete and resubmit the message multiple times.
What platform is your computer?
n the Codex desktop app on macOS, messages sent while a task is still running are not reliably delivered through the “Steer” action. When Codex asked me for a short confirmation, I entered my response and clicked “Steer.” The message failed and changed to a “Retry” state. Clicking “Retry” repeatedly did not send it. I had to delete the failed message and enter the same response again. This happened twice in the attached recording. The message was only accepted on the third attempt, after which Codex resumed the task normally. Expected behavior:Clicking “Steer” should immediately deliver the queued message to the active task. Actual behavior:The message becomes stuck in a failed “Retry” state, and retrying does not recover it. The user must delete and resubmit the message multiple times.
What issue are you seeing?
n the Codex desktop app on macOS, messages sent while a task is still running are not reliably delivered through the “Steer” action.
When Codex asked me for a short confirmation, I entered my response and clicked “Steer.” The message failed and changed to a “Retry” state. Clicking “Retry” repeatedly did not send it. I had to delete the failed message and enter the same response again.
This happened twice in the attached recording. The message was only accepted on the third attempt, after which Codex resumed the task normally.
Expected behavior:Clicking “Steer” should immediately deliver the queued message to the active task.
Actual behavior:The message becomes stuck in a failed “Retry” state, and retrying does not recover it. The user must delete and resubmit the message multiple times.
What steps can reproduce the bug?
n the Codex desktop app on macOS, messages sent while a task is still running are not reliably delivered through the “Steer” action.
When Codex asked me for a short confirmation, I entered my response and clicked “Steer.” The message failed and changed to a “Retry” state. Clicking “Retry” repeatedly did not send it. I had to delete the failed message and enter the same response again.
This happened twice in the attached recording. The message was only accepted on the third attempt, after which Codex resumed the task normally.
Expected behavior:Clicking “Steer” should immediately deliver the queued message to the active task.
Actual behavior:The message becomes stuck in a failed “Retry” state, and retrying does not recover it. The user must delete and resubmit the message multiple times.
What is the expected behavior?
n the Codex desktop app on macOS, messages sent while a task is still running are not reliably delivered through the “Steer” action.
When Codex asked me for a short confirmation, I entered my response and clicked “Steer.” The message failed and changed to a “Retry” state. Clicking “Retry” repeatedly did not send it. I had to delete the failed message and enter the same response again.
This happened twice in the attached recording. The message was only accepted on the third attempt, after which Codex resumed the task normally.
Expected behavior:Clicking “Steer” should immediately deliver the queued message to the active task.
Actual behavior:The message becomes stuck in a failed “Retry” state, and retrying does not recover it. The user must delete and resubmit the message multiple times.
Additional information
n the Codex desktop app on macOS, messages sent while a task is still running are not reliably delivered through the “Steer” action.
When Codex asked me for a short confirmation, I entered my response and clicked “Steer.” The message failed and changed to a “Retry” state. Clicking “Retry” repeatedly did not send it. I had to delete the failed message and enter the same response again.
This happened twice in the attached recording. The message was only accepted on the third attempt, after which Codex resumed the task normally.
Expected behavior:Clicking “Steer” should immediately deliver the queued message to the active task.
Actual behavior:The message becomes stuck in a failed “Retry” state, and retrying does not recover it. The user must delete and resubmit the message multiple times.