codex - 💡(How to fix) Fix Mobile remote-created worktree thread is not associated with project in Codex Desktop sidebar [2 comments, 3 participants]

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…
GitHub stats
openai/codex#23418Fetched 2026-05-20 03:50:22
View on GitHub
Comments
2
Participants
3
Timeline
7
Reactions
0
Author
Timeline (top)
labeled ×4commented ×2cross-referenced ×1

A thread created from ChatGPT mobile through Codex remote access exists locally and can be opened by deeplink, but it does not appear in the Codex Desktop project sidebar.

This looks like a project/thread association issue rather than data loss.

Root Cause

A thread created from ChatGPT mobile through Codex remote access exists locally and can be opened by deeplink, but it does not appear in the Codex Desktop project sidebar.

This looks like a project/thread association issue rather than data loss.

Fix Action

Fix / Workaround

This is not a request for a local workaround. The expected product behavior is that threads created through mobile remote access remain visible in the corresponding Desktop project sidebar.

Code Example

codex://threads/<redacted-thread-id>

---

id=<redacted-thread-id>
archived=0
cwd=/Users/<user>/.codex/worktrees/<worktree-id>/<repo-name>
thread_source=NULL

---

/Users/<user>/.codex/sessions/<date>/rollout-<timestamp>-<redacted-thread-id>.jsonl

---

/Users/<user>/<projects>/<repo-name>
RAW_BUFFERClick to expand / collapse

Summary

A thread created from ChatGPT mobile through Codex remote access exists locally and can be opened by deeplink, but it does not appear in the Codex Desktop project sidebar.

This looks like a project/thread association issue rather than data loss.

Environment

  • Codex Desktop: 26.513.31313, build 2867
  • Codex CLI: 0.131.0-alpha.9
  • OS: macOS
  • Flow: ChatGPT mobile app -> Codex remote connection -> local Desktop host
  • Thread mode: worktree

Steps to Reproduce

  1. On ChatGPT mobile, connect to a local Codex Desktop host through remote access.
  2. Open an existing project from that host.
  3. Start a new thread in worktree mode.
  4. Let the thread run normally.
  5. On the Desktop app, open the same project sidebar.
  6. Try to find the newly created thread.

Expected Behavior

The thread created from mobile remote access should appear in the same project sidebar on Codex Desktop.

Actual Behavior

The thread does not appear in the Desktop project sidebar.

However, the thread is present in local state and can be opened directly via deeplink:

codex://threads/<redacted-thread-id>

Local Evidence

The thread exists in the local SQLite state:

id=<redacted-thread-id>
archived=0
cwd=/Users/<user>/.codex/worktrees/<worktree-id>/<repo-name>
thread_source=NULL

The rollout JSONL also exists locally:

/Users/<user>/.codex/sessions/<date>/rollout-<timestamp>-<redacted-thread-id>.jsonl

The issue appears to be that the thread is not associated with the canonical project root:

/Users/<user>/<projects>/<repo-name>

In this case, the thread was created under a temporary Codex worktree path, but the Desktop sidebar did not map it back to the original project.

Related Issues

Possibly related:

Notes

This is not a request for a local workaround. The expected product behavior is that threads created through mobile remote access remain visible in the corresponding Desktop project sidebar.

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