[Bug] ANSI color drift in Windows output since v2.1.14
Bug Description
The ANSI color drift bug (#17314, #14720) on Windows has had a community-identified root cause and a 3-byte fix for over two weeks now, but no official patch has shipped.
This affects every native Windows install since v2.1.14. Random colored text fragments appear in normal prose output, getting progressively worse with longer responses. It's cosmetic but highly visible and erodes confidence — our internal users are reporting it as "Claude is broken."
The root cause (identified by @WargameGPT in #14720) is a gated condition in the Ink word-wrap renderer (IP5/bh0 function). The whitespace position correction block only runs in wrap-trim mode but needs to run in all wrap modes. The fix is removing z&& from if(z&&_.length>0) — literally 3 bytes.
The only community workaround involves hex-patching the Bun-compiled binary, which invalidates Authenticode signatures, breaks auto-update integrity checks, and is not something we can responsibly distribute to our team.
Can this please get prioritized? The diagnosis is complete, the fix is trivial, and it's been sitting for two weeks affecting every Windows user.
Environment Info
- Platform: win32
- Terminal: vscode
- Version: 2.1.45
- Feedback ID: 569c84c1-ed0e-48a5-9362-bcda5e9b5f6a
3 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
This is a known duplicate but since the original bugs aren't being addressed, I was hoping maybe another Issue might raise more attention to the problem affecting corporate Windows users.
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.