Codex App: plan/checklist panel gets stuck on the first step and does not reflect completed tasks

Resolved 💬 3 comments Opened Mar 11, 2026 by Afur Closed Jun 22, 2026

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.305.950 (863)

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.3.0 arm64 arm

What issue are you seeing?

In the macOS Codex app, the visible task plan/checklist often stops updating even though the conversation continues and later work is clearly completed.

Typical symptom:

  • The plan header stays at something like 0 out of 5 tasks completed
  • Step 1 remains shown as active/incomplete
  • In the assistant responses below, Codex has already completed step 1 and is working on or has completed later steps
  • The plan UI appears stale/desynchronized from the actual turn/session state

This makes the plan panel unreliable as progress feedback. In some cases, other UI state in the same area also appears stale.

What steps can reproduce the bug?

  1. Open the Codex macOS app.
  2. Start a task that causes Codex to create a multi-step plan/checklist.
  3. Let Codex continue working through multiple steps.
  4. Observe the checklist panel while reading the actual assistant responses.
  5. After some turns, the checklist may stop updating and remain stuck on an earlier step even though the conversation shows later steps completed.

I see this frequently rather than as a one-off failure.

What is the expected behavior?

The plan/checklist UI should stay synchronized with the actual task state.
When Codex marks a step completed in the underlying session state, the visible checklist should update accordingly instead of remaining stuck on an earlier step.

Additional information

Potentially related, but not exact duplicates:

  • #11000
  • #12321
  • #13659
  • #14251
  • #7525

This looks like a desktop app state reconciliation issue where the visible progress panel is not receiving or applying later plan/task updates consistently.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗