Codex thread is stuck with a queued user message behind an old completed Copy-Item action.
Open 💬 1 comment Opened Jun 18, 2026 by mythnick
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.602.71036 • Released 8 Jun 2026
What subscription do you have?
GPT-5.5 Pro (5X)
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
Codex thread is stuck with a queued user message behind an old completed Copy-Item action.
Original thread:
- Title: Folo-up.app.v2.0.1beta
- Thread ID: 019ce18c-30aa-7a92-b119-8cb14cd900d0
- CWD: C:\Users\joffr\.codex\worktrees\c891\WebApps\folo-up.app.v2.0
- UI symptom: message stays queued; Retry does not clear it.
- Backend symptom: list/read works, but send_message_to_thread fails with "thread not found".
- Screenshot shows queued message: "Do we know how many recalls are directly related to electrical safety in our database?"
Recovery fork created:
- Title: Folo-up.app.v2.0.1beta RECOVERY
- Thread ID: 019eda4a-3633-7c12-8c29-9c9bfae7f79e
- Follow-up was accepted there.
What steps can reproduce the bug?
N/A
What is the expected behavior?
Not being stuck
Additional information
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗