iOS mobile thread opens with metadata but message hydration fails: CodexClientError error 11

What version of Codex CLI is running?

Two Codex versions are present on the Mac after the desktop update:

• Desktop app bundled CLI: codex-cli 0.131.0-alpha.9
• PATH/Homebrew CLI: codex-cli 0.130.0

What subscription do you have?

Unknown / not inspected from local context.

Which model were you using?

Observed from the ChatGPT iOS Codex mobile control surface on a thread showing 5.5 High in the composer. The issue appears to happen while opening/hydrating existing threads, before sending a new prompt.

What platform is your computer?

macOS 26.4.1, build 25E253

Codex Desktop app:

• CFBundleShortVersionString: 26.513.20950
• CFBundleVersion: 2816
• Main desktop app-server process observed alive: /Applications/Codex.app/Contents/Resources/codex app-server --analytics-default-enabled

What issue are you seeing?

The ChatGPT iOS Codex mobile control UI can open a local desktop thread far enough to display thread metadata, but fails to hydrate the message list.

The mobile screen displays the thread shell successfully:

• thread title
• account / local Mac host row
• composer
• access mode (Full Access)
• model/reasoning indicator (5.5 High)
• diff summary pill (1 file changed, +112, -33)

But the message area shows this error instead of the conversation messages:

Error loading messages: The operation couldn’t be completed.
(CodexAppServer.CodexClientError error 11.)

Related user-visible behavior observed in the same mobile rollout window:

• Some threads do not load at all from mobile.
• Some completed desktop responses do not appear/update promptly on mobile after the response posts.
• The desktop thread remains usable; this looks like mobile/relay/app-server hydration state rather than a local desktop crash.

Reproduction

1. Update Codex Desktop to 26.513.20950 on macOS.
2. Pair/use ChatGPT iOS Codex mobile control with the Mac.
3. Open an existing active local thread from the mobile app.
4. Observe that thread metadata and controls render.
5. Observe that the message list fails with CodexAppServer.CodexClientError error 11.

This was observed around 2026-05-14 17:43 America/New_York.

Expected behavior

If mobile can list/open the thread and render its shell, it should also hydrate the message list or show a narrower recoverable state such as retry/reconnect/partial-history-unavailable.

Completed desktop turns should also update into the mobile thread reliably after they post.

Actual behavior

The thread shell renders, but messages fail to load with CodexAppServer.CodexClientError error 11. The user cannot read or continue that thread from mobile even though metadata and diff state are visible.

Local desktop log evidence near the failure window

No clean desktop app-server crash was observed. The desktop app-server was alive, and desktop logs showed normal routing for some thread methods, plus repeated turn-state/hydration-looking errors.

Representative log patterns from ~/Library/Logs/com.openai.codex/2026/05/14/codex-desktop-...-t0-i1-204642-0.log:

2026-05-14T21:40:33.889Z info [AppServerConnection] response_routed ... method=thread/list ... errorCode=null
2026-05-14T21:41:41.903Z info [AppServerConnection] response_routed ... method=thread/read ... errorCode=null
2026-05-14T21:41:42.022Z info [AppServerConnection] response_routed ... method=thread/goal/get ... errorCode=-32600
2026-05-14T21:41:42.022Z error [electron-message-handler] Request failed ... method=thread/goal/get ... error={"code":-32600,"message":"goals feature is disabled"}
2026-05-14T21:41:42.022Z warning [electron-message-handler] Failed to hydrate thread goal after resume ... error={"code":-32600,"message":"goals feature is disabled"}
2026-05-14T21:41:42.023Z info [AppServerConnection] response_routed ... method=thread/resume ... errorCode=null

Repeated nearby errors:

2026-05-14T20:51:01.457Z error [electron-message-handler] Item not found in turn state itemId=call_...
2026-05-14T21:15:29.991Z error [electron-message-handler] Item not found in turn state itemId=call_...
2026-05-14T21:19:37.386Z error [electron-message-handler] Item not found in turn state itemId=call_...
2026-05-14T21:40:55.119Z error [electron-message-handler] Item not found in turn state itemId=call_...
2026-05-14T21:45:31.001Z error [electron-message-handler] Item not found in turn state itemId=call_...

Additional context

OpenAI status was showing an active Codex incident around the same time (Codex Cloud and Code Review experiencing high failure rate). That may be separate from mobile local thread hydration, but it is useful launch-day context.

Related but not identical existing issue: #22693 covers a stale Codex run failed banner after bridge restart. This report is focused on message hydration failure where the mobile app loads thread metadata but cannot load messages.