›_ Codex Issues
Codex Issues / #38889

iOS cannot load messages from CLI 0.147.0 paginated threads

Open 💬 3 comments Opened Aug 16, 2026 by 0x7067
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

  • ChatGPT desktop app on the host Mac: 26.810.52044 (build 6662)
  • Standalone Codex CLI: codex-cli 0.147.0
  • ChatGPT iOS app: exact installed version is not visible in the screenshot

What subscription do you have?

Paid ChatGPT subscription; exact tier was not available from the local diagnostic state.

What platform is your computer?

Darwin 25.6.0 arm64 arm

The client showing the failure is ChatGPT/Codex on iOS.

What issue are you seeing?

Threads started with Codex CLI 0.147.0 appear in the mobile thread list and open far enough to show their title, host/account row, and composer, but the message list does not load.

The iOS client displays:

Error loading messages: Codex server returned an error.

The same thread remains usable from the CLI and desktop app. Threads started from the desktop app can be opened normally on mobile. The failure has only been observed with CLI-started threads.

What steps can reproduce the bug?

  1. On macOS, run Codex CLI 0.147.0.
  2. Start a new thread from the CLI and complete one or more turns.
  3. Open ChatGPT/Codex on iOS while connected to the same host/account.
  4. Select the CLI-started thread.
  5. Observe that the thread metadata renders, but the message list is replaced by the server error above.
  6. Open a desktop-app-started thread on the same mobile client and observe that its messages load normally.

What is the expected behavior?

CLI-started threads should load their messages on iOS just like desktop-app-started threads. The client should hydrate recent messages incrementally and allow the thread to be read and continued from mobile.

Additional information

Read-only local inspection found a strong format/version correlation:

  • Affected CLI 0.147.0 threads use history_mode = paginated.
  • Older CLI threads and desktop-app-started threads use history_mode = legacy.
  • The affected transcript remains valid locally and has no recorded turn errors.
  • Desktop-app-started legacy threads open normally on the same mobile client.

This suggests a mobile/app-server compatibility regression in the paginated history hydration path introduced for CLI-started threads, rather than local transcript corruption.

Related issues:

  • #22705 reports the same metadata-load/message-hydration split on an older release, but not the CLI 0.147.0 / paginated correlation.
  • #38653 reports mobile timeouts for a very large paginated thread. This report differs because the visible error is the generic server error and the failure is consistently scoped to CLI-started 0.147.0 threads.

Private thread IDs, project paths, repository names, prompts, command output, and screenshots containing account/project metadata are intentionally omitted.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 11 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #38653

Powered by Codex Action

shleder · 11 days ago

The fact that local transcript/state appears valid while iOS message hydration fails makes this another useful control case for codex-rescue. I’m field-testing whether it can distinguish a healthy persisted session from a remote/UI retrieval problem instead of producing false recovery findings.

If the relevant CLI thread is still local, could you run:

pipx install codex-rescue
codex-rescue sessions
codex-rescue doctor --latest

A healthy/no-damage result is useful here. The tool does not fix iOS pagination or server hydration; it only inspects the local Codex session and keeps the source rollout read-only.

Please share sanitized output, versions and exit codes only—no raw JSONL/SQLite, prompts, credentials, thread IDs, or unredacted paths. Repo: https://github.com/shleder/codex-rescue

nardovibecoding · 11 days ago

I can reproduce this exact failure with a fresh CLI-started thread.

  • Codex CLI: 0.147.0
  • ChatGPT desktop app: 26.810.41047
  • macOS: 26.3.1
  • Mobile behavior: the thread appears in Remote after /app, but opening it shows Error loading messages / Codex connection was invalidated.
  • Local deterministic rollout scan: clean; the thread remains usable in CLI and desktop.
  • Remote was re-paired and the desktop app restarted, with no change.

Diagnostics were uploaded through /feedback. Uploaded thread ID for maintainers: 01a00e58-329a-74a3-a386-add19aa514c0.

Observed at 2026-08-17T06:21:23Z. No raw transcript or private project data is included here.