[Bug] Syntax Highlighting Glitch with Think Keywords Causing Color Bleed
Status Fixed / completed
Maintainer reply None cached
Activity 6 comments · opened Oct 2, 2025 · closed Oct 7, 2025
Bug Description
When editing text containing the keywords think, hard think, or ultrathink, the highlight color “moves” with the cursor. As the cursor passes over characters, the color is applied to other words. The terminal sometimes prints raw SGR fragments like \[7m … \[27m (seen as [7m … [27m), breaking usability when editing already typed text after writing said keywords.
Environment Info
- Platform: linux
- Terminal: ghostty
- Version: 2.0.1
- Feedback ID: bc6df741-eec8-49c6-893b-2d31a819b79e
Errors
[]
6 Comments
Same issue
Same terminal
Same Claude Code version
But on MacOS 26
Reference:
<img width="1624" height="1060" alt="Image" src="https://github.com/user-attachments/assets/0446e6ab-01cd-4a0c-986c-fdfadc38199b" />
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
same here using WSL in VSCode Integrated Terminal.
Another example:
<img width="629" height="440" alt="Image" src="https://github.com/user-attachments/assets/3c6f2d1c-8213-4798-9e9d-19f93e522467" />
This happens when the caret moves over Ultrathink or one/or two chars are edited inside or around it.
This should be fixed in v2.0.8.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.