Mobile shows Codex thread as “Thinking” while desktop is waiting for approval
Open 💬 2 comments Opened Jun 8, 2026 by ulrich-rgb
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
Summary
A Perplexity pilot user reported that Codex on mobile remained stuck in the Thinking state while the same thread in the desktop app was blocked waiting for user approval.
User-visible behavior
- On phone: Codex thread appears to still be
Thinking. - On desktop: the same thread is waiting for the user's approval.
- The screenshots were taken from phone and desktop within ~10 seconds of each other, so this appears to be a cross-client state sync/rendering issue rather than a stale historical view.
Repro / evidence
- Reported in Slack: https://openai.enterprise.slack.com/archives/C04DYHSQ1HT/p1780927776781109?thread_ts=1780764473.698189&cid=C04DYHSQ1HT
- Codex thread/run ID shared by Jerry:
019e9dbc-04a5-7f70-a564-c6d3273bfb87 - Original report: “Seeing a bug where Codex on phone is stuck in ‘Thinking’ mode but when I check my desktop app I see the thread is waiting for my approval. The screenshots are from my phone and desktop within the same 10 seconds.”
Expected behavior
Mobile should surface the pending approval/blocking state for the thread, matching desktop, instead of continuing to show Thinking.
Impact
This makes the run look like it is still progressing on mobile when it is actually blocked on user action, which can cause users to wait indefinitely or miss required approvals.
Notes
The report was marked not urgent, but it is a clear UX/state consistency bug for Codex mobile.
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Independent reproduction on August 4, 2026, with a specific connector approval:
Environment
What happened
github.create_issuetool.Expected behavior
Either surface the connector approval controls on mobile, or clearly show “Waiting for approval on desktop” with instructions to open the host. The mobile task should not appear to be actively running while it is blocked.
I have two contemporaneous screenshots showing the iOS and desktop states and can attach them here.