[Bug] Terminal rendering issue in v2.0.73 - display corruption on narrow windows
Status Fixed / completed
Reported on v2.0.73
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 15 comments · opened Dec 19, 2025 · closed Dec 19, 2025
Bug Description
This is a display bug in the Claude Code CLI, not something I can fix from within the conversation. A few things to try:
- Resize your terminal window - sometimes forces a
- Run /clear - clears the screen and may fix rende
- Check terminal width - narrow windows can cause
If it persists, this would be worth reporting at https://github.com/anthropics/claude-code/issues since it's a rendering bug in v2.0.73.
Environment Info
- Platform: win32
- Terminal: windows-terminal
- Version: 2.0.73
- Feedback ID:
Errors
[{"error":"Error\n at Eu (B:/~BUN/root/claude.exe:58:1144)\n at <anonymous> (B:/~BUN/root/claude.exe:59:10093)\n at emit (node:events:92:22)\n at endReadableNT (internal:streams/readable:861:50)\n at processTicksAndRejections (native:7:39)\n at request (B:/~BUN/root/claude.exe:61:2149)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-12-19T07:01:55.059Z"},{"error":"Error\n at Eu (B:/~BUN/root/claude.exe:58:1144)\n at <anonymous> (B:/~BUN/root/claude.exe:59:10093)\n at emit (node:events:92:22)\n at endReadableNT (internal:streams/readable:861:50)\n at processTicksAndRejections (native:7:39)\n at request (B:/~BUN/root/claude.exe:61:2149)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-12-19T07:01:55.873Z"},{"error":"RangeError: stdout maxBuffer length exceeded\n at unknown\n at onData (node:child_process:153:110)\n at emit (node:events:95:22)\n at addChunk (internal:streams/readable:264:47)\n at readableAddChunkPushByteMode (internal:streams/readable:242:18)\n at handleNumberResult (internal:streams/native-readable:79:18)\n at <anonymous> (internal:streams/native-readable:53:68)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-12-19T07:01:56.866Z"},{"error":"Error\n at Eu (B:/~BUN/root/claude.exe:58:1144)\n at <anonymous> (B:/~BUN/root/claude.exe:59:10093)\n at emit (node:events:92:22)\n at endReadableNT (internal:streams/readable:861:50)\n at processTicksAndRejections (native:7:39)\n at request (B:/~BUN/root/claude.exe:61:2149)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-12-19T07:04:54.725Z"}]
15 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Same thing happening for me
Same thing happening for me
## Model-specific rendering issue discovered
I found that this rendering issue is model-specific in v2.0.73:
### Environment
### Key Findings
### What I Tested
Switching between models on the same v2.0.73 installation:
### Attempted Workarounds (No Effect)
alwaysThinkingEnabled: false→ No improvement### Working Solution
Downgrading to v2.0.65 → Works perfectly with both Opus and Sonnet
This suggests the rendering bug is Sonnet-specific in v2.0.73, not a general terminal compatibility issue.
I was experiencing a similar issue. Claude Code's responses appeared blank/empty, showing only the last sentence of the output. I tried various fixes but nothing worked. Eventually, downgrading to v2.0.65 solved the problem.
Is downgrading really the only solution for now? Any ETA on a fix for the latest version?
I have a similar rendering issue too reported in https://github.com/anthropics/claude-code/issues/14613
Maybe you can also reproduce it.
Downgrading to 2.0.70 worked for me.
Worked for me too! I also had to disable the AUTOUPDATER.
Same issue in VS Code terminal. Disabled AutoUpdater and downgraded to 2.0.72.
Same issue - Disabled AutoUpdater and downgraded to 2.0.72.
Yep, same, had to downgrade and disable auto update.
Do you really wanna tell me, that this bug persists since more than 15 hours an there is no fix yet!?
Maintainer Summary (Executive)
v2.0.73 introduces a Sonnet 4.5–specific rendering regression. Opus 4.5 renders correctly under identical conditions. The issue reproduces immediately when switching models on the same install and fully resolves when rolling back to v2.0.72 or v2.0.65. This isolates the defect to Sonnet’s rendering path in v2.0.73, not the terminal, OS, or VM stack.
⸻
Minimal Repro (Actionable)
Expected: Identical rendering across models
Actual: Sonnet 4.5 corrupts display in v2.0.73 only
That worked for me too
Anthropic is doing a great job (overall)!
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.