Editing and resending a queued follow-up fails with "queued follow-up no longer exists"
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
Sürüm 26.908.70816
What subscription do you have?
ChatGPT Pro
What platform is your computer?
Microsoft Windows NT 10.0.19045.0 x64
What issue are you seeing?
In the Codex App on Windows, editing an existing queued follow-up and submitting the edited message can fail.
While Codex is actively working, I can queue additional follow-up prompts normally. If I edit one of those queued prompts and submit the edited version, the app displays an error and the edited prompt is not submitted successfully.
The error shown is:
Mesaj gönderilirken hata oluştu
App-server queued follow-up no longer exists
A screen recording reproducing the issue is attached.
https://github.com/user-attachments/assets/2f84b2c9-a4cc-421d-a37e-14c9fa9bc296
What steps can reproduce the bug?
Start a task in a Codex chat and let Codex continue working.
While the task is running, add one or more follow-up prompts to the queue.
Confirm that the queued follow-up prompts appear above the input field.
Select one of the queued prompts and choose Edit.
Modify the prompt.
Submit the edited prompt.
Observe that the submission fails and the app displays:
App-server queued follow-up no longer exists
The attached screen recording shows the reproduction flow.
What is the expected behavior?
Editing a queued follow-up should update or replace that queued item without breaking its association with the active chat.
After submitting the edited prompt, it should remain in the queue and execute normally when its turn is reached.
Additional information
This occurs in the Codex App on Windows.
Normal queued follow-ups can be created successfully. The failure occurs specifically after editing an already queued follow-up and submitting the edited version.
A screen recording showing the complete reproduction is attached.
As a small token of appreciation for reporting and documenting this reproducible issue, a Codex usage reset would be greatly appreciated if that's something the team can offer. 🙂 (@milpescodex)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Windows Codex App flow by queuing a follow-up, editing it, and submitting the edit; use the resulting “queued follow-up no longer exists” error as the entry point. Trace the edit submission and its app-server association, then verify that the edited prompt remains queued and executes normally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100