[BUG] Text Rendering Visual Glitch
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Text is rendered with characters incorrectly split across different colors (e.g., the word "code" displays with "co" in red and "de" in white), which is not the intended behavior. This issue was introduced after the last working version 2.1.2 and has persisted in all subsequent releases up to the latest 2.1.27. The bug is consistently reproducible on Windows 11 when running the application in either cmd.exe or Microsoft Terminal.
<img width="1331" height="701" alt="Image" src="https://github.com/user-attachments/assets/288192b2-6fd1-4bbc-8122-5d519c13a01f" />
What Should Happen?
Text should be rendered as a single continuous string with the correct intended color for the entire word/phrase (no random color splitting of individual characters within a single word). For example, the full word "code" should display in one uniform color (e.g., all red or all white) as designed, with no character-by-character color variation for a single text element.
Error Messages/Logs
Steps to Reproduce
Install the affected version of the application (2.1.3+ up to latest 2.1.27) on a Windows 11 system.
Launch either the native cmd.exe or Microsoft Terminal on the Windows 11 machine.
Run the application via the opened terminal (using the standard launch command for the app).
Trigger the text rendering functionality (e.g., generate/display the content that includes colored text strings like "code").
Observe the incorrect character splitting and mixed-color rendering of single words/phrases.
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.1.2
Claude Code Version
2.1.27
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗