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
- On ChatGPT mobile, connect to a local Codex Desktop host through remote access.
- Open an existing project from that host.
- Start a new thread in worktree mode.
- Let the thread run normally.
- On the Desktop app, open the same project sidebar.
- 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.
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
Steps to Reproduce
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:
Local Evidence
The thread exists in the local SQLite state:
The rollout JSONL also exists locally:
The issue appears to be that the thread is not associated with the canonical project root:
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.