cmux NEXT: a new tab group nobody coloured is grey, not the next palette colour
Leo, 2026-10-31, on an agent chat tab with a salmon underline and an orange dot beside it: "WHY DOES THIS HAVE A LINE AND COLOR?????? / WHERE IS ORANGE COMING FROM?????????? AN ORANGE DOT????"
Leo-ask: ask-88148faefe
What it was
The tab was in an unnamed tab group. Such a group's chip is a bare colour dot (TabGroupChipCell), and the group band draws the underline (TabGroupBandCell). Nobody picked the colour: tabGroup.create (the tab menu's New Tab Group, the palette and the CLI through the app) gave any group created without a colour the next palette colour (TabGroupOrdering.nextColor, from cx-wqn5).
Change
- A tab group created without a colour gets grey, which is the daemon's own default for
create-tab-group. No palette colour shows up that nobody chose. - A colour the caller names (
--color, the group editor) still shows as before. - The chip, the underline geometry and the grouping itself are unchanged. They are just neutral now.
- Out of scope: screen groups and sidebar workspace groups keep their colour walk, since Leo pointed only at the tab.
Tests
TabSelectionActionsTests.thePaletteGroupsTheSameSelectedTabs now also asserts that the new group's colour is grey. The app compile check runs on the fleet.
Small change (one-line default plus a test assertion).
Agent session: agent session
š¤ Generated with Claude Code
![View with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/view-with-codesmith-dark-v3-3x.png)
![Autofix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/autofix-with-codesmith-dark-3x.png)
Need help on this PR? Tag @codesmith-bot with what you need.
Summary by cubic
Tab groups created without a chosen color now get grey instead of the next palette color, so no unintended orange dot and underline appear when nobody picked a color. A color the caller names (via --color or the group editor) still shows as before.