Feature request: Make agent team teammate colours configurable

Problem

When using agent teams in split-pane (tmux) mode, each teammate is assigned a bright colour from a hardcoded palette. With multiple agents running simultaneously, the bright ANSI colours on tmux status bars, pane borders, and agent name labels become visually overwhelming — especially on darker terminal themes where the high-saturation colours dominate the UI.

Current behaviour

The teammate colour palette is hardcoded as:

["red", "blue", "green", "yellow", "purple", "orange", "pink", "cyan"]

These map to full-brightness terminal colours in the tmux configuration (e.g. fg=red, fg=blue). There is no way to override or customise these colours.

Agent definition files (.md in agents/ directories) support a color: frontmatter field, but there is no user-facing setting to override the palette globally or per-project.

Custom values are silently ignored

Agent definition files accept a color: frontmatter field, but it only accepts the 8 hardcoded names. Custom values like tmux 256-colour numbers are silently dropped and the agent falls back to the default palette.

Tested with three agents configured as:

color: colour243   # intended: medium grey
color: colour109   # intended: muted steel blue
color: colour139   # intended: dusty mauve

All three were assigned bright defaults (blue, green, yellow) instead. No warning or error was shown.

Visual comparison

Preview in a 256-colour terminal:

Current bright palette:

for c in 1 4 2 3 5 208 13 6; do printf "\e[38;5;${c}m  ████████ colour%-3s \e[0m\n" "$c"; done

Example muted alternative:

for c in 243 245 109 139 144 180 248 67; do printf "\e[38;5;${c}m  ████████ colour%-3s \e[0m\n" "$c"; done

The muted palette maps to: medium grey, light grey, steel blue, dusty mauve, olive/khaki, warm sand, pale grey, slate blue — enough contrast to distinguish agents without dominating the terminal.

Proposal

Add a teammateColors setting to settings.json (user-level and/or project-level) that allows overriding the default colour palette.

Example configuration

{
  "teammateColors": ["colour243", "colour245", "colour247", "colour249", "colour109", "colour139", "colour144", "colour180"]
}

This would allow users to specify:

• Named ANSI colours: "red", "green", "cyan", etc.
• tmux colour numbers: "colour237", "colour109", etc. (256-colour palette)
• Hex values (if supported by the terminal): "#6c7086", "#89b4fa", etc.

Alternative: colour scheme presets

If a fully custom palette is too complex, a simpler option would be a teammateColorScheme setting with built-in presets:

{
  "teammateColorScheme": "muted"
}

Possible presets:

• "bright" — current default (full-saturation ANSI colours)
• "muted" — desaturated/grey-leaning tones (e.g. tmux colour numbers in the 237–249 range)
• "pastel" — softer pastel variants

Both options could coexist, with teammateColors taking precedence over teammateColorScheme when both are set.

Use case

Users running 3+ agent teammates in tmux split-pane mode on dark terminal themes find the default bright colours distracting. A muted palette (using tmux 256-colour numbers like colour237–colour248) integrates much better with typical developer terminal setups while still providing enough contrast to distinguish between agents.