›_ Codex Issues
Codex Issues / #30386

ChatGPT iOS Codex remote access does not show existing macOS Codex Desktop project thread

Open 💬 3 comments Opened Jun 27, 2026 by davidronquillo
💡 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)?

26.623.42026 (build 4514); bundled codex-cli 0.142.3

What subscription do you have?

Pro 20x

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

A Codex Desktop thread is visible in the macOS Codex app for a local project, but the same thread does not appear in ChatGPT iOS Codex remote access for the same connected Mac host/project.

Codex session/thread ID: 019f0aac-b526-70b2-8e8c-0b85edcdb9c0

The thread exists locally, is not archived, and remote control is enabled on the Mac host. The Mac host appears to be paired/enrolled for remote access, but iOS cannot discover this specific thread.

What steps can reproduce the bug?

  1. On macOS, open Codex Desktop.
  2. Open an existing local project thread on the connected Mac host.
  3. Confirm the thread is visible in macOS Codex Desktop.
  4. Confirm the thread/session ID is:

019f0aac-b526-70b2-8e8c-0b85edcdb9c0

  1. Open ChatGPT iOS -> Codex.
  2. Select the connected Mac host and the same project.
  3. Search/browse for the same thread.

Observed: the thread does not appear on iOS.

Already tried:

  • Force-quitting and reopening ChatGPT iOS.
  • Searching by thread title/context.
  • Checking archived/filter views.
  • Checking Codex Desktop Settings > Connections.
  • Rechecking/re-pairing mobile setup.
  • Confirming the thread exists locally and is not archived.

What is the expected behavior?

ChatGPT iOS Codex remote access should show existing threads from the connected macOS Codex Desktop host, so I can continue the same host/project thread from iOS.

Additional information

Local metadata found for the missing thread:

  • Session/thread ID: 019f0aac-b526-70b2-8e8c-0b85edcdb9c0
  • Local status: present in Codex local state, not archived
  • Originator: Codex Desktop
  • Source metadata: vscode
  • Thread source: user
  • Last local update observed: 2026-06-27 22:36:23 UTC
  • Remote control enrollment: enabled on the Mac host

One suspicious detail: the session header says originator: Codex Desktop, but the local metadata marks source: vscode. Since the thread appears in Codex Desktop but not in ChatGPT iOS remote access, it may be getting filtered or omitted by mobile remote thread indexing.

I can provide logs privately if needed, but I am not attaching raw local session/log files publicly because they may contain prompts, project paths, or other sensitive local output.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 2 months ago

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

  • #29617
  • #30385
  • #30245
  • #30123

Powered by Codex Action

marcplotkin · 1 month ago

I am seeing what looks like the same issue on another active thread, with an extra signal that the Mac-side/iOS-facing list handler can now see the thread but the ChatGPT iOS Remote app still does not render it.

Environment / client evidence:

  • ChatGPT iOS Remote client in local logs: codex_chatgpt_ios_remote v1.2026.188
  • Mac remote host is online and other active threads on the same host/project are visible in iOS Remote.
  • Target thread ID: 019f62f9-2f25-7b92-8f4a-a0950fe32c03
  • Target title: Build account and billing - active
  • Status: active/not archived locally; pinning it succeeds.

What I see:

  • The thread is not visible in the ChatGPT iOS Remote list, even though other active threads from the same Mac host are visible.
  • Force-refreshing / reopening iOS still does not show it.
  • Searching the normal title phrase (Build account) does not find it in the app-side search path I can inspect, although searching billing does find it locally.

Host-side evidence after repair attempts:

  • codex_app.list_threads(limit: 25) includes the target thread in the normal recent-thread list.
  • codex_app.list_threads(query: "019f62f9-2f25-7b92-8f4a-a0950fe32c03") returns the target.
  • codex_app.list_threads(query: "billing") returns the target.
  • codex_app.read_thread(threadId: "019f62f9-2f25-7b92-8f4a-a0950fe32c03", turnLimit: 1, includeOutputs: false) now succeeds.
  • Local app-server logs show the iOS client making a thread/list request and scanning the target rollout successfully:
app_server.client_name="codex_chatgpt_ios_remote" app_server.client_version="1.2026.188"
otel.name="thread/list" rpc.method="thread/list"
Resumed rollout with 91961 items, thread ID: Some(ThreadId { uuid: 019f62f9-2f25-7b92-8f4a-a0950fe32c03 }), parse errors: 0

This makes it look like the remaining failure is no longer local thread existence or rollout parsing. The thread is present, readable, and scanned by the iOS-facing thread/list request, but the iOS Remote app still omits it. My current guess is a mobile-side list render/cache/filter issue, possibly triggered by very large active rollouts or by title/search indexing differences.

I have screenshots of the iOS Remote list showing the same host/project with other active threads visible but this thread absent. I can provide private logs/screenshots if useful; not attaching raw local session/log files publicly because they can contain prompts and project output.

marcplotkin · 1 month ago

Follow-up with new evidence after local repair attempts on July 21, 2026 around 7:15 PM ET.

The target thread is still not visible in the ChatGPT iOS Remote list on the phone. This now looks less like a local archive/title/catalog problem and more like a mobile cache/render/filter problem.

Evidence:

  • Target thread ID: 019f62f9-2f25-7b92-8f4a-a0950fe32c03
  • Target display title: Build account and billing - active
  • Other active threads from the same Mac host/project are visible in iOS Remote.
  • The local live Codex state row now has archived = 0 and the internal title matches the app-facing display title.
  • codex_app.list_threads(limit: 12) returns the target as active near the top of the unfiltered list.
  • codex_app.read_thread(threadId: "019f62f9-2f25-7b92-8f4a-a0950fe32c03", turnLimit: 1, includeOutputs: false) succeeds and returns the active in-progress turn.
  • Recent app-server log from 7:16 PM ET: thread/read resumed the rollout with 92226 items, the expected thread ID, and parse errors: 0.
  • Earlier iOS-facing app-server logs showed codex_chatgpt_ios_remote v1.2026.188 making a thread/list request and scanning the same target rollout with parse errors: 0.

Remaining observed behavior:

  • iOS Remote still omits the thread from the rendered list.
  • Searching billing finds the target in the app-side list path I can inspect.
  • Searching Build account or the UUID does not find it there.

So the Mac host and list/read APIs can see and read the thread, but the iOS Remote UI still does not render it. The thread is very large and active, around 92k rollout items, so one guess is that large active rollouts or a stale mobile-side filter/cache path are involved.