Home / Blog / Pricing

Pricing

Codex "Error loading messages": What It Means and How to Fix It

Codex shows "Error loading messages"? What the invalidated-connection and remote-timeout versions mean, and the fixes reported in OpenAI's GitHub issues.

By Engineer Foodie Desk ✓ Sources checked Nov 5, 2026

7 min read

Error strings quoted from OpenAI’s Codex GitHub issues #28340, #38889, #40558 and #28480 (verified Nov 5, 2026). Remote-connection requirements checked Nov 5, 2026 in OpenAI’s remote connections docs. Every source is listed at the bottom. No affiliate links on this page (how we work).

In every open issue checked on Nov 5, 2026, “Error loading messages” is a client-side read failure, not a crashed task. In #38889 the same thread still opens in the CLI and the desktop app. In #40558 the desktop task keeps running while iOS fails to open it. So the task is usually still there; the phone or second client cannot load the conversation. Mark Twain had it right: the reports of this task’s death are greatly exaggerated.

It’s Weekend at Bernie’s, inverted. The body looks dead on your phone. On the host laptop, it’s still typing.

The exact errors

Three on-screen strings, each from its own issue (verified Nov 5, 2026). Do not invent a suffix; if your build shows different wording, it needs its own source.

From #28340 (opened Jun 15, 2026, open; ChatGPT Pro, macOS host, iOS remote):

Error loading messages: Codex connection was invalidated.

The same report also showed MacBook-Pro-4.local is reconnecting while the task was still active (“Pursuing goal — 11h 35m”).

From #38889 (opened Aug 16, 2026, open; desktop 26.810.52044, codex-cli 0.147.0):

Error loading messages: Codex server returned an error.

From #40558 (opened Aug 25, 2026, open; desktop 26.818.61809, runtime 0.149.0-alpha.4.3, Remote app-server 0.149.1) — bare UI string:

Error loading messages.

#28480 (opened Jun 16, 2026, open) is a remote load timeout on long desktop sessions. The on-screen text in that issue is in Chinese; I’m not translating or reconstructing it. Treat it as a remote load timeout and cite the issue URL.

OpenAI has no doc entry titled “Error loading messages” as of Nov 5, 2026. Everything below is labeled with the issue it came from.

By suffix: what each version means

Codex connection was invalidated (#28340)

Remote / mobile load. The iOS client can’t talk to the host session it thinks it has. The task on the Mac was still running in the original report. Comments on the issue describe a recovery path: quit the desktop app and the iOS app, reopen desktop, go to Settings → Connections → Invalidate session, Add, then reconnect iOS. Another commenter said re-pairing from scratch didn’t help. Another: “Fixed it by closing the codex cli session, remote no longer functions if you have both codex and desktop chatgpt opens.” A Sep 14, 2026 comment said CLI-opened chats show “Error loading messages.” with a Retry affordance.

Codex server returned an error (#38889)

CLI-created threads that use paginated history. The reporter’s correlation: affected threads had history_mode = paginated. The same thread remained usable from the CLI and desktop app. “Threads started from the desktop app can be opened normally on mobile.” Re-pair + restart made no change. A Sep 5, 2026 comment said it was still reproducible on codex-cli 0.153.4 after updating and restarting both clients. So this one is about how the thread was created and stored, not about your network being down for five minutes.

Bare Error loading messages (#40558)

Active-writer conflict. Opening a desktop-created active thread on iOS failed. The app-server log showed failed to initialize thread persistence: thread-store conflict: thread <redacted> already has an active writer. codex doctor on the host showed the Remote WebSocket connected (HTTP 101 Switching Protocols). The report says “no evidence that the thread data is missing or corrupt.” Threads created from iOS Remote loaded normally. A version difference between clients was noted; causation was not established. Later comments (Sep 27–Nov 2, 2026) show a clearer on-screen line: Another Codex session is using this task. Finish and close that session, then try again.

Remote load timeout (#28480)

iOS times out loading a long Codex Desktop session. The issue says there is “no clear manual retry path” on iOS. A Sep 24, 2026 comment points at a possible host-side cause tracked in #47842 (hung config/read until the app-server restarts; check the host log for “timed out waiting for connection RPCs to drain”). Fix path from that thread: retry from the host, not from the phone.

What to try, in order

Each step marked with the issue or doc it comes from.

  1. Open the thread on the host first (desktop app or CLI). #38889 and #40558 both show the host still has the conversation when the phone doesn’t. Confirm the task is alive before you panic.
  2. Stop the task writing on the host, then reopen on the phone. #40558’s later UI copy is explicit: finish and close the session that holds the active writer, then try again on iOS.
  3. Quit both apps and re-pair remote control the way #28340 comments describe: Invalidate session on desktop Connections, Add again, reconnect iOS. Also close a competing codex CLI session if both CLI and desktop ChatGPT are open — one #28340 commenter said remote breaks in that combo.
  4. Update the ChatGPT mobile app and the desktop app together. OpenAI’s remote connections docs (verified Nov 5, 2026) say you need the latest mobile app and the latest desktop app on a host that is “awake, online, and signed in to the same account and workspace.” Connections not used since June 8, 2026 should update both apps and pair again. If the remote session disconnects, check whether the host went to sleep, lost network, or closed the app. After Remote Control → Add errors, restart the desktop app.
  5. Match client and host versions when an issue points at a mismatch. #38889 stayed broken across 0.147.0 → 0.153.4 for that reporter, so an update alone is not a guaranteed fix — but the remote docs still want both ends current before you file.
  6. On a long-session timeout (#28480), retry from the host. That issue says iOS has no clear manual retry path. Check the host log for the hung RPC line mentioned via #47842, and restart the app-server / desktop app if it’s stuck.
  7. Run codex doctor on the host the way #40558 did, and confirm the Remote WebSocket is connected, before you assume the thread is gone.

What not to do: don’t delete thread storage. None of the four issues reports that as a fix, and #40558 explicitly said the thread data did not look missing or corrupt. Don’t farm accounts or relay the session through some third-party “remote unlock” tool.

Is it your usage limit?

No. A usage-limit message and “Error loading messages” are different problems. For the limit side, see Codex usage limits and Codex usage limit reached — one line each, different posts. Whether a failed load itself spends Codex credits is not published as of Nov 5, 2026.

When to file an issue

Include what the open issues ask for:

  • Desktop app build string and codex-cli / runtime version (see the version lines in #38889 and #40558).
  • Whether the thread was created on desktop, CLI or iOS.
  • Host connection check from #40558: codex doctor showing the Remote WebSocket connected (or not).
  • The exact on-screen string, copied, not paraphrased.
  • For timeouts, the host log line about connection RPCs if you have it (#28480 / #47842).

File against openai/codex. Don’t name other reporters; link the issue you’re duplicating.

Here’s what I’d do

Open the thread on the machine that started it. If it’s still running, leave it alone and stop fighting the phone. Close the active writer, then try iOS again. If the suffix says the connection was invalidated, invalidate and re-pair once with both apps updated and the host awake. If it’s the paginated CLI-thread case from #38889, keep working on desktop/CLI until OpenAI ships a fix — updating alone didn’t clear it for that reporter. And if you’re mid-flight on a long remote session that won’t load on iOS, retry from the host. The phone is a window, not the only copy of the work.

A capacity message is not a loading failure: see Codex selected model is at capacity.

FAQ

What does Codex Error loading messages mean? A client (often the phone) failed to read an existing conversation; in the open issues checked Nov 5, 2026 the task usually still exists on the host.

Does Codex Error loading messages mean my task is lost? Usually no — #38889 and #40558 both show the same thread still usable on desktop or CLI while iOS fails.

How do I fix Codex Error loading messages on my phone? Open or finish the session on the host, then reopen on iOS; if the connection was invalidated, quit both apps and re-pair Remote Control per #28340.

Does a failed load use Codex credits? Not published as of Nov 5, 2026.

What does Error loading messages: Codex connection was invalidated. mean? The remote client lost a valid connection to the host session; #28340 reports the desktop task can still be running while iOS shows that line.

What does Error loading messages: Codex server returned an error. mean? In #38889 it hit CLI-created paginated threads that still opened fine on desktop and CLI; updating alone did not fix it for that reporter.

Sources

  1. Codex GitHub issue #28340 (Error loading messages: Codex connection was invalidated.; open): https://github.com/openai/codex/issues/28340 (verified 2026-11-05)
  2. Codex GitHub issue #38889 (Error loading messages: Codex server returned an error.; paginated CLI threads; open): https://github.com/openai/codex/issues/38889 (verified 2026-11-05)
  3. Codex GitHub issue #40558 (bare Error loading messages.; active-writer / thread-store conflict; open): https://github.com/openai/codex/issues/40558 (verified 2026-11-05)
  4. Codex GitHub issue #28480 (remote load timeout on long sessions; Chinese on-screen text not translated here; open): https://github.com/openai/codex/issues/28480 (verified 2026-11-05)
  5. OpenAI, Remote connections (latest apps, awake host, same account/workspace, re-pair, disconnect causes): https://learn.chatgpt.com/docs/remote-connections (verified 2026-11-05)

Related reading