You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
SSH: adding a repo through a symlinked path creates a duplicate project for the same repository #29637
On an SSH host, adding a repository through a symlinked path creates a second project for the same repository. Adding the canonical path a second time is correctly deduplicated: Orca just selects the existing project. The symlinked path is not resolved before that duplicate check, so the alias gets through.
Add /tmp/soak-a43/home/repo on an SSH host as a Git project.
On the host, run ln -s /tmp/soak-a43/home/repo /tmp/soak-a43/home/repo-link.
Add project → pick that host → type /tmp/soak-a43/home/repo-link in Host path → Add Git Project.
The sidebar now has two projects, tmp/soak-a43/home/repo and repo-link. Both list a main worktree whose id ends in ::/tmp/soak-a43/home/repo, and each has its own terminals.
For comparison, adding /tmp/soak-a43/home/repo again just selects the existing project.
Expected
The alias resolves to the same repository and selects the existing project, or the dialog says the project already exists. It should not create a duplicate project on the same host.
Notes
Terminals opened in the alias project start in the canonical directory (~/repo), so they are working on the same checkout.
Fix is in #29651: the host that owns the path now compares real paths, so adding a symlink alias selects the existing project, while separate checkouts stay separate. Verified live on a Linux managed host. This issue will close when that PR merges.
Activity
nwparker commentedon Oct 16, 2026
Fix is in #29651: the host that owns the path now compares real paths, so adding a symlink alias selects the existing project, while separate checkouts stay separate. Verified live on a Linux managed host. This issue will close when that PR merges.