[Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"

What version of the Codex App are you using (From “About Codex” dialog)?

• Installed Codex Desktop Windows package: 26.903.9818.0, verified locally with Get-AppxPackage.
• The executable used by the currently running Codex backend reports codex-cli 0.153.4 via --version.

These were collected on September 11, 2026. The Desktop version above is the Windows package version; the version shown in the About Codex dialog was not separately inspected.

What subscription do you have?

ChatGPT Pro 20x, confirmed by the reporter.

What platform is your computer?

Windows, Codex desktop app.

What issue are you seeing?

Editing and resending a queued follow-up message causes the app to display this error:

创建聊天时出错
App-server queued follow-up no longer exists

The Chinese heading means “Error creating chat.”

The reporter can reproduce this through the queued-message editing workflow. Switching to a different conversation thread in the app makes the error disappear.

What steps can reproduce the bug?

1. Open a conversation in the Codex desktop app and start a task.
2. While it is running, send another instruction so that the new message is queued.
3. Choose Edit message on that queued message.
4. Resubmit the message from the editor.
5. Observe “创建聊天时出错” / “App-server queued follow-up no longer exists”.
6. Switch to a different conversation thread in the app; the error disappears.

What is the expected behavior?

Editing and resubmitting a queued message should update/requeue it successfully without a missing-follow-up error. The UI should remain usable without requiring a switch to another conversation thread to clear the error.

Additional information

• Workaround observed by the reporter: switch to a different conversation thread to clear the visible error. This specifically means navigating between conversation threads, not switching arbitrary app pages.
• It has not been confirmed whether the edited instruction is ultimately delivered, remains queued, or is lost. Clearing the error is not evidence that message delivery succeeded.
• These are user-reported reproduction steps; no independent automated reproduction or root-cause investigation was performed for this report.

Related reports found during duplicate search:

• #22895 concerns a queued message moving to the end of the queue after editing.
• #14213 concerns the CLI/TUI failing to remove a queued message when opening it for editing.
• #37974 concerns TUI queued inputs becoming stranded after a failed prompt-edit branch.

Those reports describe different errors or outcomes. No existing report with this exact error and desktop edit/resubmit workflow was found.

No file or test is named in the report. Start by reproducing the queued-message edit and resubmit workflow in Codex Desktop, then trace the queued follow-up lifecycle through the desktop and app-server components. Done means editing and resubmitting succeeds without the missing-follow-up error and the instruction remains correctly queued or delivered.