fix: unset COLORTERM to fix xterm.js rendering issues #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
COLORTERMin all PTY spawns to fix rendering issues in xterm.jsProblem
When
COLORTERM=truecoloris inherited from the outer terminal (e.g., Ghostty, iTerm2), Claude Code's Ink UI tries to use truecolor mode. However, xterm.js doesn't handle this correctly, causing rendering issues like gray/white backgrounds appearing where they shouldn't.Solution
Unset
COLORTERMin the environment when spawning PTY processes so applications fall back to standard 256-color mode which xterm.js fully supports.Changes
screen-manager.ts: Addunset COLORTERMto screen session environmentsession.ts: AddCOLORTERM: undefinedto all PTY spawn env objectsRelated
🤖 Generated with Claude Code