Optional per-environment colors in the thread sidebar

[Oghara]

I regularly switch between local and remote environments in T3C, and it can be hard to tell which environment each thread belongs to.

Would you be open to optional per-environment colors in the thread sidebar?

I built a local desktop prototype to test the idea.

• Choose a color for each environment under Settings / Connections.
• Show it as a narrow marker on each environment's thread rows.
• Leave the existing styling unchanged.
• Store the choice locally on the client, keyed by environment ID.

Here are some screenshots

I found a few related proposals. #6875 tackles the same environment-identification problem with custom machine icons and notes that color alone is less accessible. #6705 suggests a similar color marker for projects, while #7836 explores grouping threads by environment.

I can share the implementation details if useful.

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Issue #8479 adds a mobile destination-identification case that belongs with this color proposal.

The current mobile new-task composer includes a selectable on <environment> control. The reported problem occurs earlier in the flow: one project group contains three rows with the same project name and absolute path, but each row points to a different environment. The user cannot identify the destination before choosing a row. The smaller request is to show the environment name prominently on each project row and keep the destination clear in the composer. The report also asks for a more prominent, desktop-style selector presentation. That is a UI proposal, not evidence that mobile has no selector.

The same report asks for optional environment colors on project rows, active-session rows, and the composer. The color can be automatic with an override or fully opt-in. Text labels still matter because color alone must not carry the identity. The screenshot and exact three-row reproduction remain in the source report.