Windows app: completed task remains stuck showing Stop (■) after restart and fork

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

Codex app version

26.721.3404.0 (Windows packaged desktop app)

Platform

Windows desktop app

What issue are you seeing?

A task completed, and its backend state was verified as idle with the latest turn completed, but the composer permanently continues to show the square Stop button () instead of returning to the normal send state.

There was no running terminal or background task. Clicking had no effect.

Recovery attempts that did not fix it

  1. Clicked Stop repeatedly.
  2. Switched to another task and back.
  3. Paused the task and submitted a new prompt.
  4. Fully exited Codex, verified the old app processes stopped, and relaunched it.
  5. Forked the affected task while preserving the original. The fork was created successfully and was idle, but the UI still showed .

Expected behavior

When a task is idle and its latest turn is completed, the composer should reconcile to the normal send state. If Stop is shown, clicking it should either cancel the actual task or clear a stale UI state.

Additional information

The stale Stop state persisted across a verified full app restart and a successful fork. No project files or private paths are included in this report.

Similar symptom: #14094. That issue is closed, but this occurred on the newer app version above.

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.

  • #34026

Powered by Codex Action

Laydan-Skilton · 17 days ago

I'm occasionally experiencing this issue too