Old Codex App task hangs and even “hello” gets no response
What version of the Codex App are you using (From “About Codex” dialog)?
26.727.51351
What subscription do you have?
plus
What platform is your computer?
24.6.0 arm64 arm
What issue are you seeing?
On macOS, one existing Codex task repeatedly becomes unresponsive. Even sending “hello” gets no response. Restarting the app does not restore the old task. A new task can respond normally, but the old task remains stuck. The feedback upload in the old task also keeps spinning.
Affected old session ID:
019fc58f-8eff-7eb0-813e-deeea258353c
Reproduction:
- Open the existing Codex task.
- Send a simple message such as “hello”.
- The task keeps spinning and does not respond.
- The feedback/upload flow in the old task also keeps spinning.
- A new task works normally.
Expected:
The existing task should resume and accept messages after restarting the app.
Additional checks:
- Terminal commands work normally.
- The project directory and git status return immediately.
- The problem is not limited to Git, website code, or image generation.
What steps can reproduce the bug?
Feedback ID: 019fc68a-a374-7263-97fa-24509d095056
What is the expected behavior?
After restarting the Codex desktop app, the existing task should reopen normally, accept a new message, and continue from its previous state.
Additional information
Codex App version: 26.727.51351
Platform: macOS 24.6.0 arm64 arm
Terminal commands work normally, including pwd and git status in the project directory. The issue is not caused by Git, the website project, or a terminal command.
The old task became very large after repeated image-generation operations. A new task works, but the original task cannot be recovered.
File upload was not included because the upload control itself keeps spinning.
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I reviewed the suggested duplicate issues, but my issue appears to be different.
This is not a crash. The historical session can be opened successfully, but after resuming an existing session, sending any new message gets no response.
New sessions work normally. The problem only happens when continuing a previous session from history.
Steps to reproduce:
This seems related to session resume/continuation rather than long context, compaction, or task serialization.
Update: This is not an isolated one-time failure. I have reproduced the same behavior repeatedly in the same existing Codex task. The old task becomes unresponsive after handling larger/longer data, while starting a new task works normally, including for the same work. This suggests the issue is related to the state of that existing task rather than one specific input. Please investigate whether a long-running or resumed task can enter a state where new messages are accepted but no response is returned.