Version 2.0.73: Text rendering bug - lines dropped and garbled output
Status Fixed / completed
Reported on v2.0.73
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 5 comments · opened Dec 19, 2025 · closed Dec 19, 2025
Description
Version 2.0.73 has a severe text rendering bug where assistant text output is garbled:
- Lines are randomly dropped (consistently the 4th line in test messages)
- Left side of text is cut off
- Large gaps appear where text should be
Tool output renders correctly - only the assistant's direct text responses are affected.
Environment
- OS: Windows 11 (10.0.26200)
- Terminal: Windows Terminal and cmd.exe (both affected)
- Node: v22.x
- Claude Code Version: 2.0.73
Steps to Reproduce
- Install claude-code 2.0.73
- Start a session
- Observe that assistant text responses are garbled/incomplete
Expected Behavior
All text should render completely and correctly.
Actual Behavior
Text is garbled with:
- Missing lines (4th line consistently dropped in tests)
- Left portions of lines cut off
- Irregular spacing
Workaround
Rolling back to version 2.0.72 resolves the issue:
npm uninstall -g @anthropic-ai/claude-code
npm install -g @anthropic-ai/claude-code@2.0.72Additional Context
- Issue persists across terminal restarts and machine reboots
- Issue persists in both Windows Terminal and cmd.exe
- Disabling Norton antivirus did not resolve the issue
- Fresh sessions (not resumed) also exhibit the bug
- Only affects 2.0.73; 2.0.72 works correctly
5 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
For workaround
To prevent immediate reupdating from claude-code@2.0.72
to the version that has garbled output (claude-code@2.073)
Add this to ~/.claude/settings.json:
{
"env": {
"DISABLE_AUTOUPDATER": "1"
}
}
Confirmed: Rollback to 2.0.72 fixes the issue
Rolled back from 2.0.73 to 2.0.72 using:
npm install -g @anthropic-ai/claude-code@2.0.72
Rendering now works correctly in Windows cmd. The bug is specific to 2.0.73.
Environment:
Upgrading to 2.0.74 fixes the issue.
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.