›_ Codex Issues
Codex Issues / #32704

Codex Desktop: Active plan “Step X / Y” badge disappears after goal continuation or context compaction

Open 💬 2 comments Opened Jul 13, 2026 by jcoble
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

Version 26.707.61608

What subscription do you have?

Pro 20x

What platform is your computer?

Mac

What issue are you seeing?

An active structured plan’s “Step X / Y” badge disappears after an automatic goal continuation or context compaction, even though the goal remains active and the agent still considers the plan active. Calling update_plan again makes the badge reappear.

Goal state persists; visible plan state does not.

What steps can reproduce the bug?

An active structured plan’s “Step X / Y” badge disappears

  1. Create a ooal with a plan.
  2. Start goal.
  3. Wait for a compaction.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #32422

Powered by Codex Action

cryptomasters · 1 month ago

Additional reproduction on Windows x64, Codex Desktop 26.721.3996.0 (Microsoft Store/AppX), with an app update/restart as the state-transition trigger.

This is observable across chats, not only in one particular thread:

  1. Before restart, an active chat automatically shows the structured Steps panel / step sequence.
  2. Update or restart Codex Desktop.
  3. Reopen or resume the same chat.
  4. The work can continue, but the Steps panel is no longer rendered and does not automatically reappear.

The problem is especially noticeable in chats where no persistent goal was set. A long-running chat with an active goal also showed the missing Steps UI after restart, so it is not specific to a single conversation or project.

Expected: the latest structured plan/progress state should be persisted and rehydrated after restart, independently of whether a goal exists.

Actual: the chat survives and continues, but the visible step sequence is lost.

This appears consistent with plan/progress UI state being transient or not being replayed during thread restoration. Private thread content and identifiers are intentionally omitted.