Sidebar: optional grouping by device and visible device names on project threads

[JayHopsHQ]

When the same repository is open on a Mac and a remote server, its threads can use different branches, credentials and test environments. Users need to see which environment owns each thread without renaming every project or inspecting tooltips.

The earlier discussion #7836 was closed after #21039 added project folders. This is a narrower follow-up: device/environment identity, which grouping by project does not solve.

Proposed scope

• An opt-in Group by device preference that keeps each environment’s threads together within the existing sidebar sections, preserving their current order inside each device.
• An independent Show device names preference that displays the environment name on project threads and search results while keeping branch names visible. Threads without a project already expose this useful identity.
• Both default off. Use existing environment IDs and labels, with no changes to projects, checkouts, API settings, server grouping projections or polling.
• The prototype covers web/desktop’s shared sidebar and the mobile sidebar. Device grouping takes precedence over project folders only while explicitly enabled.

Prototype and validation

Public branch based on official pingdotgg/t3code main at 2a738273e74e:
https://github.com/JayHopsHQ/t3code/tree/feat/sidebar-device-grouping

vp run check:changed passes, including 249 tests, affected-package type checks, lint and formatting. The production web build passes. Browser integration tests exercise enabling/disabling both options, visible machine names and retained branch text; grouping and keyboard tests cover distinct devices, pinned/shelf boundaries and skipping headings. An isolated local instance was also checked in light and dark mode. Native iOS/Android and an installed Electron build have not been tested.

Before/after screenshots are generated by the browser test and configured for CI artifact upload; image binaries are not committed to the feature branch.

Would maintainers accept this focused scope for a PR, or prefer a different way to expose environment grouping and machine labels? This proposal requests direction before opening a feature PR, as required by CONTRIBUTING.md.

Posted by Codex (gpt-6.1-sol, T3 Code harness) on behalf of @JayHopsHQ. Implementation and test report are agent-generated.