codex - 💡(How to fix) Fix Codex mobile thread list loses visibility after desktop resume on same host

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Root Cause

This does not look like a desktop sidebar/history indexing issue because the desktop app is up to date and shows all sessions correctly. The missing visibility is on mobile only.

RAW_BUFFERClick to expand / collapse

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

0.133.0-alpha.1

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

Codex mobile remote access thread visibility appears to be one-way and can be lost after desktop resume.

Observed behavior:

  • A thread started from Codex mobile appears on Codex desktop.
  • After resuming or sending a message in that same thread from Codex desktop, the thread no longer appears in Codex mobile.
  • New threads started on Codex desktop also do not appear in Codex mobile.
  • Desktop session history itself is current and visible on desktop.

This does not look like a desktop sidebar/history indexing issue because the desktop app is up to date and shows all sessions correctly. The missing visibility is on mobile only.

Relevant feedback/session id:

  • Feedback ID: 019e5fc3-8ad1-76c3-a31b-b9e7d9a43465

Relevant local log signals from ~/Library/Logs/com.openai.codex/2026/05/25/ around the affected activity:

  • Received turn/started for unknown conversation
  • Received turn/completed for unknown conversation

Additional local version note:

  • Shell codex --version: codex-cli 0.128.0
  • Bundled app agent reports: codex-cli 0.133.0-alpha.1

What steps can reproduce the bug?

  1. Connect Codex mobile to the Mac host running Codex desktop using remote access.
  2. Start a new thread from Codex mobile.
  3. Confirm that thread appears in Codex desktop.
  4. Resume that same thread on Codex desktop and send a message.
  5. Check Codex mobile again.
  6. The thread is no longer visible in Codex mobile.
  7. Start a new thread directly on Codex desktop.
  8. Check Codex mobile again.
  9. The desktop-created thread does not appear in Codex mobile.

Repro summary:

  • Mobile-created thread -> visible on desktop.
  • Same thread after desktop activity -> no longer visible on mobile.
  • Desktop-created threads -> not visible on mobile.

What is the expected behavior?

Codex mobile should continue to show and resume threads for the same connected Mac host regardless of whether the latest activity happened on mobile or desktop.

A thread started on mobile should remain visible on mobile after desktop resumes it, and threads started on desktop on the same host/account/workspace should appear on mobile.

Additional information

Already tried uninstall/reinstall, disconnect/reconnect, and similar client-side reset steps.

This appears specific to the mobile remote-access thread list/state sync path rather than account mismatch or missing desktop history.

If helpful, I can provide the exact timestamps from the local log files corresponding to the repro steps.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING