Codex App: current thread messages are missing from the chat UI
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)?
Unknown (not available from the affected UI)
What subscription do you have?
Unknown
What platform is your computer?
macOS on Apple Silicon
What issue are you seeing?
Messages entered by the user in the current Codex task are not displayed in the chat UI. The agent still receives and processes the messages, but the conversation pane appears empty. This makes it impossible for the user to review what they entered or what the agent replied.
No conversation text, contact information, logs, screenshots, or session identifiers are included in this report.
What steps can reproduce the bug?
- Open a Codex task in the desktop app.
- Send messages and receive responses in that same task.
- Observe that the task's conversation pane shows none of the messages exchanged during the day, even though the agent continues responding with the current context.
The issue was observed on September 8, 2026 (KST).
What is the expected behavior?
All messages sent and received in the current task should remain visible in that task's conversation pane.
Additional information
The problem appears to be a UI display or synchronization issue rather than a loss of task context.
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 issue in a Codex task on macOS by sending messages and observing the conversation pane. Trace the desktop app's current-task conversation display or synchronization path, then verify that sent and received messages remain visible in the task pane while the agent continues responding.
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