anthropics
[Bug] SHOW-STOPPER: Claude Code 2.0.1 CLI Terminal UI Rendering Corrupted + Scrolling Instability + Completely Unusable
Bug Description
Claude Code CLI v2.0.1 exhibits severe display corruption that renders the application unusable. Every character typed causes the display to scroll upward and/or status line to scroll right-wards; and terminal output becomes misformatted and corrupted.
Environment
Version: Claude Code CLI v2.0.1 OS: Reproducible on both macOS and Windows API Status: Claude works normally in browser and via API with same credentials
Steps to Reproduce
- Launch Claude Code CLI v2.0.1
- Begin typing any character input
- Observe display behavior
Expected Behavior
- Terminal display should remain stable with properly formatted text as characters are typed.
- Claude Code narrative should remain displayed above prompt box
Actual Behavior
- Display scrolls upward with each character input
- and/or status Line scrolls rightward with every character
- Terminal output becomes misformatted and corrupted
- Claude Code narrative stacks vertically with every update
- UI becomes unusable despite Claude functionality working correctly (browser, API, same account)
Additional Context
- This appears to be a pure UI/display rendering issue
- Claude backend functionality is unaffected (confirmed by normal operation in browser and via API)
- Issue consistent across Windows and macOS
Impact
Severity: Critical - Application is completely unusable in its current stateRetry
Environment Info
- Platform: darwin
- Terminal: Apple_Terminal
- Version: 2.0.1
- Feedback ID: 11bd2495-b360-4efb-ad28-4934daa9a1d3
I have the issue that my mouse wheel only scrolls through the command history and not the claude code output window. I tried to use shift, arrow up and down, shift arraws up and down and page up and page down. all only scroll through the chat history. Not sure if that is related to this bug. Also enlarging the terminal window doesn't help. That only renders the window in the same way as mentioned above.
I'm running claude code in vscode on windows 11.
I have the same issue with wezterm on Linux Mint. The terminal state seems to persist through to the actual shell after exiting Claude Code. I need to open a completely new tab/window to get rid of the issue and not use claude --continue either.
Seems this is fixed in 2.0.5 and 2.0.8 Nice work @bcherny @catherinewu if it's you people behind it.
I have this issue in 2.0.5, actually. Just sporadic, I cannot put my finger on when it happens and what triggers it.
Here is explanation https://github.com/anthropics/claude-code/issues/10472#issuecomment-3467247238
I've cancelled my subscription today. Not saying this to be "that guy" or expecting it will make a difference but I just can't use claude code anymore. Plan mode causes this for me 9/10 times (Windows/WSL). Normal modes tend to be OK with careful management but it's not a guarantee.
I've tried OpenCode with my Max subscription, and while it is beautiful - it's just doesn't get the same results that claude code does.
I was willing to wait and see if a fix was forthcoming but seeing that this issue has existed for literally months and seems to be getting worse sealed the deal for me.
Please make this issue a priority! Looking at the numerous duplicate issues on this problem, I'd say this is affecting alot more people than you realise.
Same issue here. The bug is nauseating, dizzying, and can cause seizure. This bug causes a major health problem.
This bug is still present in the current version (2.0.42, native build).
- OS: Windows 11
- Terminal: Windows Terminal (also tested in VSCode integrated terminal, Git Bash, CMD, PowerShell -> same issue in all)
Happening to me on the current version, both on system terminal and iterm2, regardless of font and utf-8 settings:
╭─── Claude Code v2.0.55 ────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │ Tips for getting started │
│ Welcome back Taylor! │ Run /init to create a CLAUDE.md file with instructions for Claude │
│ │ ───────────────────────────────────────────────────────────────── │
│ ▐▛███▜▌ │ Recent activity │
│ ▝▜█████▛▘ │ No recent activity │
│ ▘▘ ▝▝ │ │
│ │ │
│ Opus 4.5 · Claude Max │ │
│ /…/homebrew/Library/Taps │ │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
> Try "create a util logging.py that..."
─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
? for shortcuts Thinking off (tab to toggle)
edit: This turned out to be caused somehow by nushell in a way that I fixed. My zshrc was something like this:
if command -v nu; then
export SHELL=nu
exec nu
fi
so that I can have nushell as my main shell, but still benefit from zsh as my login shell for startup and compatibility purposes. But when I changed my zshrc to this:
# Launch nushell automatically for interactive shells
# Conditions: nu exists, shell is interactive, not invoked from within nushell
if [[ $- == *i* ]] && command -v nu > /dev/null 2>&1; then
export SHELL=nu
exec nu
fi
It stopped happening and is fixed. The interactive shell check is what fixes it. I'm not sure exactly why, but it seems that claude code runs zsh in a way that zshrc runs, but it's still not considered an interactive shell.
If you are:
- In a VM
- seeing a little tearing in other windows also but it goes really nuts in claude code. Try disabing GPU acceleration in Vmware settings
v2.0.73 Regression Report
This bug has regressed in v2.0.73 (released today, Dec 18, 2025).
Environment:
- OS: Windows 11
- Terminal: PowerShell 7.5.4
- Version: 2.0.73
Reproduction:
- v2.0.72 works fine - no rendering issues
- v2.0.73 causes garbled/misaligned text rendering immediately
- Downgrading to v2.0.72 fixes the issue
Workaround:
npm install -g @anthropic-ai/[email protected]
The 2.0.73 changelog includes TUI changes (improved theme picker UI, unified SearchBox component) which may have introduced this regression.
actually there are so many glitches in that version that I had to downgrade. Very annoying experiance. They relay too much on AI, because I've never seen so much cumulation of glitches in a release, never observed in Codex or Gemini CLI.
v2.0.73 Regression Report
This bug has regressed in v2.0.73 (released today, Dec 18, 2025).
Environment:
- OS: Windows 11
- Terminal: PowerShell 7.5.4
- Version: 2.0.73
Reproduction:
- v2.0.72 works fine - no rendering issues
- v2.0.73 causes garbled/misaligned text rendering immediately
- Downgrading to v2.0.72 fixes the issue
Workaround:
npm install -g @anthropic-ai/[email protected]The 2.0.73 changelog includes TUI changes (improved theme picker UI, unified SearchBox component) which may have introduced this regression.