Codex App task remains in Thinking with no first response and cannot be steered

Open 💬 1 comment Opened Jul 13, 2026 by hongjieh

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

26.707.62119 (Codex CLI 0.144.2)

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.3.0 arm64 arm

What issue are you seeing?

A local Codex App task entered Thinking / active but never produced any first response, reasoning item, or tool call. It was not waiting for an approval.

Inspection of the task showed an in-progress turn containing only the user message; activeFlags was empty. Other local tasks and a read-only connector were working normally at the same time.

A recovery/steer prompt was accepted for the task but did not take effect, so the task remained permanently active. This appears to be a local task-dispatch or streaming-state failure rather than slow model reasoning or a remote-host connection issue.

What steps can reproduce the bug?

  1. Use the macOS Codex App with a local task.
  2. In a previous response, select a cited issue reference and add a response annotation.
  3. Submit a short follow-up question (in this case: “Does this have a duplicate?”).
  4. Observe that the UI shows Thinking, but no first response, reasoning summary, tool activity, approval request, or error ever appears.

This is not yet a deterministic reproduction, but the task remained in this state for more than 10 minutes.

What is the expected behavior?

The task should either begin streaming a response promptly, surface an actionable error, or remain interruptible/steerable. A stuck turn should not remain active indefinitely with no output.

Additional information

This was a local session, not a remote-host task. No approval dialog was pending. I am intentionally omitting the task ID and logs because this is a public issue, but can provide redacted diagnostics privately if requested.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗