Mac Codex Desktop misclassifies sessions from different projects under the same remote worktree as a single project

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

26.415.40636 (1799)

What subscription do you have?

chatgpt plus

What platform is your computer?

Darwin 25.4.0 arm64 arm

What issue are you seeing?

Summary

Mac Codex Desktop incorrectly groups sessions from different remote projects under a single project when those projects live under the same git worktree / repository on the remote machine.

In practice, I can start separate Codex sessions from different project directories, but Desktop shows them under one project entry instead of keeping them separated by the actual project they belong to.

Environment

• Mac Codex Desktop: 26.415.40636 (build 1799)
• macOS: 26.4.1 (build 25E253)
• Remote Codex CLI: 0.121.0

What steps can reproduce the bug?

Reproduction Steps

1. On a remote machine, prepare two different project directories, for example:

• /path/to/worktree/project-a
• /path/to/worktree/project-b

1. Make sure these projects live under the same git worktree / repository context on the remote side.
2. Start one Codex session in project-a.
3. Start another Codex session in project-b.
4. Open Mac Codex Desktop and inspect the conversation list / project grouping.

Actual Behavior

Sessions started from project-a and project-b are not displayed under their respective projects.

Instead, Desktop groups them under a single project, often showing both sessions under one of the project names.

What is the expected behavior?

Expected Behavior

Desktop should classify sessions by their actual project directory / workspace root / cwd.

That means:

• sessions started in project-a should appear under project-a
• sessions started in project-b should appear under project-b

Sharing the same remote worktree or repository should not cause sessions from different projects to be merged into the same project grouping.

Additional information

Suspected Cause(Diagnosed by codex)

This looks like the Desktop-side grouping logic may be using git-level identity that is too coarse, such as:

• repo root
• worktree root
• origin URL

instead of prioritizing more specific session context, such as:

• actual workspace root
• session cwd
• remote project path

If project grouping is based primarily on repo/worktree/origin identity, then different projects inside the same remote worktree can be incorrectly treated as a single project.