[iOS] Plan CTA overlays on top other CTAs and does nothing

Open 💬 1 comment Opened May 22, 2026 by borkedengineer

What issue are you seeing?

System / User information

Extra information if needed about my systems seeing this issue.

Codex info

chat id: 019e3813-9ee0-73c3-bc54-ba891764eeb1

Laptop (macbook pro)

Codex CLI version: codex-cli 0.131.0-alpha.9
Codex binary: /Applications/Codex.app/Contents/Resources/codex

iPhone with ChatGPT app

Phone: iPhone 12 PRO
iOS version: 24.4.2
ChatGPT iOS app version: 1.2026.125 (25565698938)

Description

While using Codex in iOS ChatGPT mode, the menu for accepting/executing a plan that was created earlier in the conversation keeps showing up. When clicking on the buttons to execute it does nothing. Leaving the chat and coming back still shows the screen as Codex progresses doing it's task.

Sometimes Codex will prompt to accept/execute something but the accept plan CTA overlays ontop making Codex chat not progress in its task. You can only progress the task by going to desktop and seeing what Codex really wants you to do.

What steps can reproduce the bug?

Pre-reqs

Configuration of codex with a computer (macbook in my case) and iOS ChatGPT app

Steps
  1. In a project, use plan mode and make some plan.
  2. Execute the plan in codex (in the iOS ChatGPT app)
  3. The app may have not progressed or got stuck but approve an action/request on the computer for the same chat running the plan.
  4. Wait for plan to finish.
  5. Execute a new prompt in the same chat where the plan was executed (in the iOS ChatGPT app)
  6. Observe the CTA to execute the plan that was executed in step 2

What is the expected behavior?

When I'm using codex on iOS via ChatGPT I should be able to prompt and execute actions when codex prompts me to do so. I shouldn't see a execute plan screen even though the plan was already executed earlier in the conversation.

It also shouldn't be frozen and blocking my task with codex that is prompting me to accept/do an action to carry on the task.

Additional information

_No response_

View original on GitHub ↗

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