fix(web): choose a server for grouped projects

[StiensWout]

Grouped projects can exist on more than one T3 environment, but the new-thread picker only showed the representative server. The sidebar also treated that group as a single choice, so it skipped the picker even though the user still had to choose where the thread should run.

This shows the server count on grouped project rows and opens a Run on list with every server and workspace path. The sidebar button and chat.new shortcut now count server destinations, while single-server projects and the direct-create shortcut keep their existing behavior.

Proof

Before

The grouped project row showed one server with no indication that another copy existed.

After

The row shows 2 servers.

Opening the row shows the full server list. Playwright also selected workbench-01 and confirmed the composer changed its Run on value.

Verification

• Web TypeScript check
• Command palette logic, 17 tests
• Environment grouping, 13 tests
• Sidebar logic, 105 tests
• Playwright pass against two disposable connected environments

Created by GPT-5.6-Sol through the Codex harness in T3 Code.

---

Note

Medium Risk
Changes when new threads are created vs routed through the picker, so a destination-count bug could skip the picker or create threads on the wrong environment.

Overview
New threads for a grouped project now treat each unique environment as a destination, not the group as a single choice.

The command palette “New thread in…” row shows a server count and opens a Run on submenu with every server and workspace path. The sidebar new-thread button and chat.new use the same destination count, so a single grouped project on two servers still opens the picker. Shift-click / chat.newLocal still create in the current project.

Primary environment labels in the palette use resolveEnvironmentOptionLabel instead of a hardcoded “Local”.

^{Reviewed by Cursor Bugbot for commit db5c47c. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Show server destination picker for grouped projects in Command Palette

• Adds countNewThreadDestinations and listNewThreadProjectDestinations to count and list distinct environment destinations across grouped projects
• Command Palette 'New thread in…' section now shows a submenu when a project has multiple server destinations, letting users pick the environment; single-destination projects remain a direct action with an icon and label
• Sidebar 'New thread' button and chat.new shortcut now open the picker based on destination count instead of project group count
• enumerateCommandPaletteItems accepts CommandPaletteSubmenuItem alongside action items
• Primary environment label resolves via resolveEnvironmentOptionLabel instead of a hardcoded 'Local' string
• Behavioral Change: shouldCreateNewThreadInCurrentProject parameter renamed from projectGroupCount to destinationCount; callers in Sidebar.tsx and _chat.tsx now pass distinct environment counts

^{Macroscope summarized db5c47c.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 73e0e5dd-b662-4220-ac5a-23d5e55b323a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Two UI consistency findings in the new "New thread in..." destination rows. Details inline.

^{Posted via Macroscope — UI Consistency}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 399d9c8. Configure here.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — The PR changes new-thread routing across the command palette, sidebar button, and global shortcut, adding a server-selection submenu for grouped projects. Because the selected environment determines where the thread is created, the cross-cutting user-facing behavior warrants human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

One finding: the latest commit drops the local/remote environment icon distinction in the new-thread destination rows.

^{Posted via Macroscope — UI Consistency}