Terminal Pro ships four statusline themes. The theme travels as a single field in your exported config — "theme": "catppuccin" — and the local runtime maps it to the colors you see. Here is each one rendered with the default segment set, live from the real renderer:
M Opus 4.8 | E high | ctx 26%/1M | 5h 42% 2h24 | 7d 36% 5d5hM Opus 4.8 | E high | ctx 26%/1M | 5h 42% 2h24 | 7d 36% 5d5hM Opus 4.8 | E high | ctx 26%/1M | 5h 42% 2h24 | 7d 36% 5d5hM Opus 4.8 | E high | ctx 26%/1M | 5h 42% 2h24 | 7d 36% 5d5hHow to choose
- Midnight — high-contrast lime on charcoal. The default; reads well on almost any dark terminal background.
- Graphite — cool grays with ice blue. Pick it if your terminal already leans blue (Nord, Tokyo Night) and lime would clash.
- Catppuccin — matches the Mocha palette exactly. If your editor, terminal, and tmux are already Catppuccin, this completes the set.
- Mono — grayscale only. For minimal setups, light-sensitive eyes, and terminals where color carries other meaning.
Where the theme lives in the config
{
"name": "Terminal Pro",
"theme": "catppuccin",
"style": "balanced",
"bars": "auto",
"refreshInterval": 10,
"segments": [ ... ]
}Switching themes is a one-word edit to ~/.claude/terminal-pro/statusline.config.json — no reinstall, the runtime reads the config on each refresh. Valid values: midnight, graphite, catppuccin, mono. Anything else falls back to the default rather than erroring.
Theme vs. terminal palette
A statusline theme can't override your terminal's palette: if your terminal remaps ANSI colors, the rendered result shifts with it. That's a feature — the line inherits your setup's character — but it means you should judge themes in your own terminal, not in screenshots. The fastest way is the builder preview cycling through widths, or the dedicated theme gallery with full palette breakdowns per theme.