mirror of
https://github.com/Ark0N/Codeman.git
synced 2026-10-20 09:09:35 +02:00
21 lines
1.2 KiB
Markdown
21 lines
1.2 KiB
Markdown
|
---
|
||
|
|
"aicodeman": patch
|
||
|
|
---
|
||
|
|
|
||
|
|
fix(terminal): let Claude use truecolor so its themed backgrounds render
|
||
|
|
|
||
|
|
Claude draws the user's own messages as a block of background color, and inside a Codeman
|
||
|
|
pane that block was invisible. tmux hands each pane `TERM=screen`, which supports-color reads
|
||
|
|
as 16 colors, and the registry entry for Claude deleted `COLORTERM` on top of that. Claude
|
||
|
|
therefore quantized every RGB color its theme asked for down to the basic palette, where
|
||
|
|
`rgb(55, 55, 55)` and every other dark background becomes `ESC[40m` — the terminal's own
|
||
|
|
black. A custom Claude theme could change the color and nothing on screen moved.
|
||
|
|
|
||
|
|
Claude now exports `COLORTERM=truecolor` and unsets `NO_COLOR`, which is what codex, gemini,
|
||
|
|
antigravity, pi, grok and omp already do. `CLAUDECODE` stays unset, because Claude reads it
|
||
|
|
as a signal that it is running nested inside itself.
|
||
|
|
|
||
|
|
PR #3 introduced the `unset COLORTERM` in February, citing xterm.js#484 for the claim that
|
||
|
|
xterm.js mishandles truecolor. xterm.js closed that issue in April 2019, Codeman now depends
|
||
|
|
on `@xterm/xterm` 6, and `TmuxManager` sets `terminal-overrides ",*:Tc"` on its own tmux
|
||
|
|
server, so 24-bit color already reaches the browser for the six CLIs that ask for it.
|