Codex Desktop treats symlinked project paths as separate projects, causing threads to disappear/reappear between restarts

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

26.707.30751

What subscription do you have?

pro

What platform is your computer?

macOS & Linux

What issue are you seeing?

Codex Desktop appears to treat a real project path and a symlinked path to the same directory as two separate project identities.

On my remote Linux server, the project is located on a mounted drive, for example:

/media/<user>/<drive-id>/<project-name>

I also have a convenience symlink under my home directory:

/home/<user>/dev -> /media/<user>/<drive-id>

So the same project can also be accessed as:

/home/<user>/dev/<project-name>

Codex seems to index existing threads under the real /media/... path after restart, but when I open a thread, it moves/disappears from that project list and appears under the /home/... symlinked project entry instead.

The threads are not deleted, but the project sidebar becomes unstable and confusing because the same project is split between two path identities.

What steps can reproduce the bug?

1. On a remote Linux development server, place a project on a mounted drive, for example:

/media/<user>/<drive-id>/<project-name>

1. Create a symlink from the home directory to that mounted drive, for example:

/home/<user>/dev -> /media/<user>/<drive-id>

1. Add/open the same project in Codex Desktop using one or both paths:

/media/<user>/<drive-id>/<project-name>
/home/<user>/dev/<project-name>

1. Create or open several Codex threads for that project.

1. Restart Codex Desktop.

1. Observe that the existing threads appear under the /media/... project entry.

1. Click/open one of those threads.

1. Observe that the thread disappears from the /media/... project list and appears under the /home/... symlinked project entry.

1. Restart Codex Desktop again.

1. Observe that the thread appears under the /media/... project entry again.

What is the expected behavior?

_No response_

Additional information

_No response_