Codex mobile cannot resume a blocked goal

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

Current Codex mobile build as of 2026-07-18; exact mobile build number was not captured.

What subscription do you have?

Pro

What platform is your computer?

Mobile client paired with Codex Desktop on macOS (Darwin 25.5.0 arm64 arm).

What issue are you seeing?

A goal that has entered the blocked state cannot be resumed from the Codex mobile UI.

The blocked goal and its thread are visible on mobile, but mobile does not expose the desktop-equivalent Resume goal action. This means the user can inspect or message the thread from the phone but cannot perform the goal lifecycle transition needed to continue it. Recovery requires returning to Codex Desktop.

This is specifically about resuming an already-blocked goal from mobile, not merely stopping the current turn or editing/clearing the goal.

What steps can reproduce the bug?

1. Start a goal in Codex Desktop.
2. Have the goal reach a legitimate blocked state while waiting for user input or an external blocker.
3. Open the same thread in Codex mobile.
4. Resolve the blocker or provide the requested information.
5. Look for a Resume goal action on mobile.
6. Attempt to continue the blocked goal without returning to desktop.

Actual result: mobile does not provide a usable Resume action for the blocked goal, so the goal cannot be resumed from the phone.

What is the expected behavior?

Codex mobile should expose the essential goal lifecycle action for a blocked goal:

• show that the goal is blocked and why;
• allow the user to provide the missing input;
• provide a clear Resume goal action;
• transition the same goal from blocked to active/running;
• keep mobile and desktop goal state synchronized.

The behavior should match the desktop Resume control. If a normal message is intended to resume a blocked goal automatically, mobile should make that contract explicit and update the goal state immediately.

Additional information

Related but not duplicate reports:

• #29370 tracks the underlying blocked-to-active state transition remaining stale after resume on Desktop.
• #28574 includes the broader absence of iOS pause/resume controls after usage-limit recovery.
• #25606 tracks mobile goal-state divergence and Stop affecting only the current turn.
• #23202 requested mobile goal resume support and was closed after goal support reached the desktop app; a later Android report on that issue also notes that mobile offers edit/clear but no resume.

This issue isolates the missing mobile recovery path for an already-blocked goal.