Codex desktop: editing a steered message prevents sending with an API error

What version of the Codex App are you using?

Codex desktop app on macOS. Exact About-dialog version has not been captured.

What subscription do you have?

Not included in this initial report.

What issue are you seeing?

After steering a message into an active task, returning to edit that message can leave the composer unable to send. An API error appears at the top of the app. The edited message cannot be submitted through the normal flow.

This is a user-reported observation from an ongoing session on September 14, 2026. The reporting assistant has not independently reproduced the failure. The exact error text is not yet available.

What steps can reproduce the bug?

1. Start a task and allow the assistant to continue working.
2. Submit a follow-up using the steering flow.
3. Return to that message and choose Edit.
4. Change the message and try to send it.
5. Observe that sending fails and an API error banner appears at the top.

What is the expected behavior?

Editing and resubmitting a steered message should succeed, or the app should clearly explain any restriction and preserve a usable composer without requiring navigation away.

Additional information

The user's workaround is to remove the failed draft, switch to another chat, return to the original chat, paste the message again, and send. That restores sending.

This report intentionally contains only the reproduction and workaround. No private conversation, project data, credentials, or logs are attached.

Start by reproducing the reported steering, Edit, and resend sequence in the Codex desktop app on macOS, while capturing the exact app version and API error text. Then trace the steering/edit/send flow and its composer state. Done when the edited steered message sends successfully, or any restriction is clearly explained while preserving a usable composer.