openai / openai/codex

[Bug] Active Desktop task updates without rendering progress in main chat

Open
#43,620 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug
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)?

Codex Desktop 26.818.22352

What subscription do you have?

Not disclosed for privacy

What platform is your computer?

macOS 26.5.1 (25F80)

What issue are you seeing?

A long-running task remains active and its backend task state continues to receive newer update timestamps, but the main conversation pane renders no new progress or commentary. The model-visible thread state can report an in-progress turn while its visible item list is empty.

This makes a healthy active task appear stalled or abandoned. The user cannot distinguish ongoing work from a hung task and may repeatedly request status or duplicate coordination.

What steps can reproduce the bug?
  1. Start a long-running task in Codex Desktop.
  2. Let the turn remain active while background work continues.
  3. Open or remain on the task in the main conversation pane.
  4. Observe that no progress/commentary appears even while the task state update timestamp advances.
What is the expected behavior?

An active task should render new progress items as they arrive. If no displayable progress item is available, the UI should at least show an explicit working indicator and the latest activity time so the user can distinguish ongoing work from a stall.

Additional information

Observed on 2026-09-07. In one occurrence, the current turn began at approximately 19:12 EDT and the task state updated through approximately 19:24 EDT, while no progress items appeared in the main chat.

Possibly related but not an exact duplicate: #24263 and #40342. This report contains no transcript, repository details, credentials, private paths, account identifiers, or task/thread IDs.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the long-running task in Codex Desktop on macOS and compare advancing backend task timestamps with the main conversation pane's visible items. Trace the task-state and progress-rendering entry points; done means active progress appears, or an explicit working indicator and latest activity time are shown when no displayable item exists.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, rust
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.