Summary
After the Charm TUI ecosystem migration to v2 (#788), running micasa under TERM=tmux-256color produces degraded color output compared to v1. Setting TERM=xterm-256color restores the expected behavior.
Root cause
Lipgloss v2 uses github.com/charmbracelet/x/term for terminal capability detection. It appears tmux-256color is not recognized as truecolor-capable, causing a fallback to a lower color profile (likely 256-color or less).
In lipgloss v1, the same TERM=tmux-256color setting worked correctly with full truecolor output.
Reproduction
- Set
TERM=tmux-256color (e.g. inside tmux)
- Run
micasa --demo
- Observe degraded colors compared to
TERM=xterm-256color
Workaround
Set TERM=xterm-256color in the dev shell or before launching micasa.
Upstream
This likely needs a fix in charm.land/lipgloss/v2 or github.com/charmbracelet/x/term to recognize tmux-256color as truecolor-capable.
🤖 Generated with Claude Code
Summary
After the Charm TUI ecosystem migration to v2 (#788), running micasa under
TERM=tmux-256colorproduces degraded color output compared to v1. SettingTERM=xterm-256colorrestores the expected behavior.Root cause
Lipgloss v2 uses
github.com/charmbracelet/x/termfor terminal capability detection. It appearstmux-256coloris not recognized as truecolor-capable, causing a fallback to a lower color profile (likely 256-color or less).In lipgloss v1, the same
TERM=tmux-256colorsetting worked correctly with full truecolor output.Reproduction
TERM=tmux-256color(e.g. inside tmux)micasa --demoTERM=xterm-256colorWorkaround
Set
TERM=xterm-256colorin the dev shell or before launching micasa.Upstream
This likely needs a fix in
charm.land/lipgloss/v2orgithub.com/charmbracelet/x/termto recognizetmux-256coloras truecolor-capable.🤖 Generated with Claude Code