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

Open
#35,099 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reproducing the stale Stop-button state in the Windows packaged desktop app on version 26.721.3404.0, then trace how the composer reflects an idle task after completion, restart, and fork. Done means an idle task shows the normal send state and Stop either cancels an active task or clears stale UI state; no source files or tests are named in the report.

Written by the indexing model from the issue text.

Description

app bug session windows-os
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.

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

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.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.