Progress panel often stays stale after task completion, leaving items spinning or unchecked

Open 💬 1 comment Opened Jun 3, 2026 by GGBondBlueWhale

Codex app version

Desktop Codex: 26.601.21317 — released Jun 2, 2026

Platform

  • macOS Tahoe 26.5.1
  • Apple Silicon MacBook Pro
  • Pro plan

Related feedback ID

019e8c8a-f381-7272-b203-5409ebb9a1d1

Summary

Codex Desktop's built-in Progress panel often does not update promptly or accurately after a task has already completed.

I frequently see cases where the main task output indicates that the task has finished, but the Progress panel still shows some steps as incomplete, still spinning, or not checked off.

Observed behavior

After a Codex task reaches a completed/final state:

  • The main conversation/result indicates that the task is done or the user has stopped after a completed phase.
  • The Progress panel still shows one or more steps as unfinished.
  • Some progress items may remain in a loading/spinning state.
  • Some steps that appear to have already been completed are still not checked off.
  • The Progress panel can therefore present a stale or misleading task state.

Expected behavior

The Progress panel should stay synchronized with the actual task state. When a task completes, stops, or reaches a final result, the progress checklist should be updated promptly and consistently.

At minimum:

  • completed steps should be marked complete,
  • currently running steps should stop spinning when no longer running,
  • unfinished steps should accurately reflect remaining work,
  • the panel should not continue to display a stale in-progress state after the task is already done.

Actual behavior

The Progress panel can lag behind the real task state. Even after the task appears complete, the Progress area may still show unfinished checkboxes or a spinner, making it look like Codex is still working on steps that are no longer active.

Why this matters

The Progress panel is meant to help users understand what Codex has completed, what is still running, and what remains. If it is stale after task completion, it becomes unreliable and confusing.

This is especially disruptive for long-running tasks where users rely on the Progress panel to monitor work without reading the entire transcript. A stale progress state can make users think Codex is still working, stuck, or failed to complete a step, even when the task output says otherwise.

Request

Please improve synchronization between Codex's internal task state and the visible Progress panel. The progress checklist should update reliably when the task completes, stops, or transitions to a final response, and it should not leave stale spinning or unchecked items after completion.

<img width="2048" height="458" alt="Image" src="https://github.com/user-attachments/assets/c01dd9da-c8ce-4ecf-9ce4-d98e01df5ea6" />

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗