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
[Bug]: A project grouped on one paired Orca shows outside that group on the other Orcas #29876
Two Orca desktops paired with each other (Orca A and Orca B).
The same project, the same Git repository, is added on both machines. Each sidebar shows it as one project with a row from each host.
Steps
On Orca A, move the project into a group (Move to group or New group from project).
Look at the same project on Orca B.
Actual
On Orca A the project is inside the group. On Orca B the group header shows with nothing under it, and the project sits outside it at the top level. Orca B has the group and the moved row, so this is not a sync delay. Reloading does not change it.
Cause
A project set up on several hosts is drawn as one section. The section is anchored on whichever of its rows comes first in the viewing Orca's own catalog order (getManualOrderAnchorRepo in src/shared/project-section-order.ts). Each Orca usually lists its own host's row first.
The section is placed in a Project Group by the anchor's projectGroupId only (appendProjectGroupSections in worktree-list/grouping/project-group-sections.ts, and the reveal path in build-rows.ts).
Move to group on Orca A changes Orca A's row, which is the anchor there. On Orca B the anchor is Orca B's own row, which has no group, so the section lands at the root.
Expected
The project is drawn inside the group on every Orca that shows it.
Related: #29536 folds same-named groups from different hosts into one header. This issue is about a group that exists on only one host, so the two fixes don't overlap in logic, though both touch the sidebar's project-group placement.
#29877 is rebased onto current main. The list builder moved to src/shared/sidebar-list in #29906, so the fix now lives there and every list built from it (desktop sidebar, Cmd+1–9 order, reveal, and the phone's host list) places the project the same way.
Still reproducing on a Windows 11 desktop paired with two remote Orca runtimes (one Ubuntu VM, one Windows server).
The same project (project-a, same GitHub remote) is set up on all three computers, so the sidebar shows one project header with three main rows (Local Windows / vm / server). Each copy has its own repo id.
I created a local group and moved the local copy into it. The persisted state is correct: the local repo row has projectGroupId set to the local group, and right-clicking the project shows it as already in that group. But the project header still renders at the root, and the group header is empty. The anchor row is one of the remote copies, which are ungrouped.
The same happens for a second project (project-b) set up on the same three computers. #34720 looks like exactly the fix needed here. It would be great to see it reviewed and merged.
Activity
AmethystLiang commentedon Oct 18, 2026
looking into it
jbamlee commentedon Oct 19, 2026
Related: #29536 folds same-named groups from different hosts into one header. This issue is about a group that exists on only one host, so the two fixes don't overlap in logic, though both touch the sidebar's project-group placement.
#29877 is rebased onto current main. The list builder moved to
src/shared/sidebar-listin #29906, so the fix now lives there and every list built from it (desktop sidebar, Cmd+1–9 order, reveal, and the phone's host list) places the project the same way.fix(sidebar): place a multi-host project in the group any of its rows…
fix(sidebar): place a multi-host project in the group any of its rows…
fix(sidebar): place a multi-host project in the group any of its rows…
hybrid2102 commentedon Nov 3, 2026
Still reproducing on a Windows 11 desktop paired with two remote Orca runtimes (one Ubuntu VM, one Windows server).
The same project (
project-a, same GitHub remote) is set up on all three computers, so the sidebar shows one project header with threemainrows (Local Windows / vm / server). Each copy has its own repo id.I created a local group and moved the local copy into it. The persisted state is correct: the local repo row has
projectGroupIdset to the local group, and right-clicking the project shows it as already in that group. But the project header still renders at the root, and the group header is empty. The anchor row is one of the remote copies, which are ungrouped.The same happens for a second project (
project-b) set up on the same three computers. #34720 looks like exactly the fix needed here. It would be great to see it reviewed and merged.