Codex App worktree fork thread hidden under project-sorted sidebar

Open 💬 4 comments Opened Jun 7, 2026 by LGSME

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

26.602.40724

What subscription do you have?

plus

What platform is your computer?

windows11

What issue are you seeing?

Feedback ID: 019ea1b4-58d9-7d60-a174-a66817e0be30

Problem:
After forking a Codex conversation into a new worktree, the forked thread does not appear in the default sidebar project-sorted view. It appears only after switching sidebar sorting to chronological order.

Expected:
Forked worktree threads should remain visible under the original project, or be shown clearly as a worktree child thread.

Actual:
The thread appears hidden/missing in project-sorted sidebar, making it look like the forked conversation was lost.

Environment:
Windows 11
Codex Desktop App
Original project path: D:\codexProjects\worktree_test
Worktree path: C:\Users\Xiao\.codex\worktrees\2103\worktree_test

What steps can reproduce the bug?

Feedback ID / Session ID:
019ea1b4-58d9-7d60-a174-a66817e0be30

Steps to reproduce:

  1. Open Codex Desktop App on Windows.
  2. Open a saved project backed by a Git repository, for example:

D:\codexProjects\worktree_test

  1. Keep the sidebar organization set to:

Organize sidebar -> Sort by -> By project

  1. Start a conversation in that project.
  2. From the conversation, choose to fork/derive the conversation into a new worktree.
  3. Wait until worktree creation completes.
  4. Continue chatting in the forked worktree conversation.
  5. Click the original conversation in the left sidebar, or inspect the project-sorted sidebar.
  6. The forked conversation appears to be missing from the sidebar.
  7. Change sidebar sorting to:

Organize sidebar -> Sort by -> Chronological order

  1. The forked conversation appears again.

Actual result:
The forked worktree conversation is hidden or not discoverable in the default project-sorted sidebar view. It looks like the forked conversation was lost.

Expected result:
A conversation forked into a new worktree should remain visible in the sidebar under the original project, or under a clear worktree child/group entry. It should not disappear from the default project-sorted view.

Notes:
The Git worktree itself is created successfully. The issue appears to be only with sidebar grouping/indexing.

Original project path:
D:\codexProjects\worktree_test

Forked worktree path:
C:\Users\Xiao\.codex\worktrees\2103\worktree_test

Observed Git state:
The forked conversation cwd was:
C:\Users\Xiao\.codex\worktrees\2103\worktree_test

The worktree existed and was listed by git worktree list.

Possible cause:
The project-sorted sidebar may be grouping conversations by physical cwd/project path. Since the forked worktree cwd is under:
C:\Users\Xiao\.codex\worktrees\...
instead of the original saved project path:
D:\codexProjects\worktree_test
the forked thread may not be associated with the original project group.

Code / commands used to create the minimal repo:

mkdir D:\codexProjects\worktree_test
cd D:\codexProjects\worktree_test
New-Item simple1.txt -ItemType File
git init -b main
git add .
git commit -m "Initial commit"

### What is the expected behavior?

_No response_

### Additional information

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗