Desktop task becomes unsendable and cannot be stopped until app restart

Open
#38,422 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Reproduce the stuck task behavior using the affected task ID and the reported macOS desktop environment. Start by tracing client/task-state synchronization and stale session metadata, then verify that an idle task accepts messages, clears the thinking state, and recovers without restarting the application.

Written by the indexing model from the issue text.

Description

app bug session
Summary

A Codex task became stuck in a client state where I could not send new messages and could not stop the apparent thinking state. The same task was unusable from both Work and Codex. Quitting and restarting the application restored normal behavior.

Affected task

019fc246-0b10-75e2-acfe-d666c96cd246

Observed behavior
  • New messages could not be sent to the task.
  • The apparent thinking state could not be stopped.
  • The agent was actually idle, so the client state did not match backend activity.
  • The problem affected the same task in both Work and Codex.
  • There was no effective recovery action within the task UI.
Expected behavior
  • Sending a message should work whenever the task is idle.
  • The UI should not show an active thinking/stop state when no agent work is running.
  • If task state becomes stale, the client should reconcile it automatically or provide an effective retry/reconnect action without requiring a full application restart.
Workaround

Quit the application completely and restart it. Messaging worked again after restart.

Environment
  • macOS: 26.5.2 (build 25F84)
  • ChatGPT desktop: 26.803.81509 (build 6415)
  • Date observed: 2026-08-13, Pacific Time
Possible area to investigate

Inference: client/task-state synchronization or stale session metadata, because the agent was idle while the client would not accept messages or clear the apparent thinking state.

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.