Skip to content

lipgloss v2: TERM=tmux-256color not detected as truecolor-capable #789

@cpcloud

Description

@cpcloud

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

  1. Set TERM=tmux-256color (e.g. inside tmux)
  2. Run micasa --demo
  3. 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions