iOS Codex can view existing worktree threads but cannot create or select permanent worktree threads

Summary

ChatGPT iOS 1.2026.160 can view existing Codex worktree threads created from Desktop, including the worktree indicator/chevron, but it cannot create or select a worktree-backed thread from the iOS new-thread flow.

Permanent worktrees also do not appear as separate/selectable entries on iOS. Threads started from a permanent worktree on Desktop are visible on iOS, but they are grouped under the original project directory rather than under the permanent worktree.

Environment

| Surface | Version / context |
| --- | --- |
| ChatGPT iOS / Codex Mobile | 1.2026.160 |
| Codex Desktop | Latest available version at time of filing |
| Host platform | macOS Codex Desktop host |
| Project type | Local Git-backed project with Codex-created worktrees |

What works

• Codex Desktop can create worktree-backed threads for the project.
• ChatGPT iOS can see those Desktop-created worktree threads.
• ChatGPT iOS shows the worktree indicator/chevron for existing worktree threads.

What does not work

• ChatGPT iOS cannot create a new worktree-backed thread for the same project.
• A Desktop-created permanent worktree does not appear as a separate/selectable project or workspace entry on iOS.
• A thread started from that permanent worktree on Desktop appears on iOS, but is grouped under the original project directory.

Steps to reproduce

1. On Codex Desktop, open a local Git-backed project.
2. Create a worktree-backed thread from Desktop.
3. Open ChatGPT iOS 1.2026.160 > Codex and connect to the same Desktop host.
4. Confirm that iOS can see the existing Desktop-created worktree thread and shows the worktree indicator/chevron.
5. From iOS, try to start a new thread for the same project in a new worktree.
6. Observe that iOS does not provide a reliable way to create/select a worktree-backed thread from the new-thread flow.
7. On Desktop, create a permanent worktree for the same project.
8. Open iOS Codex again and inspect project/thread creation entry points.
9. Observe that the permanent worktree does not appear as its own selectable project/workspace entry.
10. On Desktop, start a new thread from the permanent worktree.
11. Observe on iOS that the thread appears, but is grouped under the original project directory rather than the permanent worktree.

Expected behavior

For a Git-backed project where Desktop can create worktree-backed threads, iOS should expose the same effective target selection before the first prompt, including one or more of:

• create a new Codex-managed worktree for the thread;
• select an existing/permanent worktree as the execution target;
• show the effective checkout/worktree path and branch before submission.

Permanent worktrees should either appear as addressable workspaces/projects in iOS, or iOS should clearly show the thread's actual cwd / worktree path instead of grouping it ambiguously under the original repo.

Actual behavior

The iOS surface can display existing worktree metadata after a thread exists, but it does not expose the worktree as a first-class execution target for new thread creation. Permanent worktree threads are also grouped under the original project directory, making the actual execution target ambiguous from iOS.

Why this matters

The iOS surface is useful for starting or supervising work while away from the host. For coding tasks, the execution target is a safety boundary: users need to know before the first prompt whether Codex will edit the primary checkout, a Codex-managed worktree, or a permanent worktree.

When iOS groups worktree threads under the original project and does not expose worktree selection/creation, it is easy to start edits in the wrong checkout or lose confidence about where a mobile-started task will run.

Workaround

Create the worktree-backed thread from Desktop first, then continue it from iOS. This works for supervision, but it does not solve mobile-first thread creation.