[Bug]: New thread from a grouped repository opens the oldest sub-folder checkout, not the repository root #36296

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

1. Have one git repository with a remote, for example owner/workspace, containing several sub-folders.
2. Over a few weeks, add several of those sub-folders as projects, for example workspace/_archive/old-tool, then workspace/app-a, then workspace/app-b.
3. Later, add the repository root workspace/ itself as a project.
4. In the sidebar or new-thread picker, choose the grouped entry owner/workspace and start a thread.

Expected behavior

When the repository root is one of the grouped checkouts, a thread started from the group entry runs in the repository root. Or the picker asks which folder to use, or lets me choose a default checkout for the group.

Actual behavior

The thread starts in workspace/_archive/old-tool, which looks like the earliest-added checkout. The repository root, added last, is never chosen. Nothing in the new-thread UI shows which folder was picked, so the agent works in the wrong directory and the thread is filed under that sub-folder's project.

Every thread I start from the group lands in the same archived sub-folder, including threads started from the iOS app.

Impact

Major degradation or frequent failure

Version or commit

0.1.7 (desktop app, macOS)

Environment

macOS, desktop app. 19 checkouts share one repository identity: the repository root plus 18 sub-folders.

Workaround

Set each sub-folder checkout to Keep separate in Settings, or pick the root checkout by its own name. Both work, but you only find them once threads have already landed in the wrong folder.

Related

#10930 and #19024 were closed because grouping is intended and Keep separate exists. This report is narrower: which checkout the group entry picks. When the repository root is a member of the group, choosing the oldest sub-folder looks like the wrong default.