[BUG] PowerShell: Text rendering issues - invisible text and excessive input field height

Status Fixed / completed
Reported on v2.0.73
Maintainer reply None cached
Activity 11 comments · opened Dec 19, 2025 · closed Dec 19, 2025

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Two UI rendering issues when running Claude Code in PowerShell:

  1. Invisible/partial text in Claude's responses
  • Claude's response text is mostly invisible
  • Only some characters appear intermittently
  • Makes responses unreadable
  1. Input field height bug
  • The input field's background/highlight area is excessively tall
  • Even short single-line messages show highlight spanning 2 lines
  • 2-line messages show 4-line highlight, and so on
  • The highlight area is always double the actual text height

What Should Happen?

  1. All of Claude's response text should be fully visible and readable
  2. Input field highlight/background should match the actual text height (1 line of text = 1 line of highlight)

Error Messages/Logs

No error messages. This is a visual/UI rendering issue.

Steps to Reproduce

  1. Open PowerShell on Windows
  2. Run claude to start Claude Code
  3. Type any message and press Enter
  4. Observe:
  • Claude's response text is partially invisible (only some characters visible)
  • The input field's highlight area is twice the height of actual text
  1. Type a 2-line message
  2. Observe: The highlight area spans 4 lines instead of 2

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.0.73

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

  • Windows 11
  • Claude Code version: 2.0.73
  • The issue does NOT occur in Git Bash or VSCode integrated terminal
  • Only occurs in PowerShell
  • Tried both Windows PowerShell and PowerShell 7, same issue

<img width="1111" height="617" alt="Image" src="https://github.com/user-attachments/assets/5bc63702-1b23-40f3-b427-cee264caef66" />

View original on GitHub ↗

11 Comments

angeloprado · 8 months ago

Seeing the same issue - Claude Code completely unusable 2.0.73. Is this not being tested on Windows?

<img width="2457" height="1059" alt="Image" src="https://github.com/user-attachments/assets/e5e699de-cf3c-42e5-9e52-0b50878f7885" />

barturker · 8 months ago

<img width="1329" height="259" alt="Image" src="https://github.com/user-attachments/assets/94e7c0aa-22f8-4aaa-bf35-9ff95fc68d8f" />

same error can't use at the moment on Windows 11

laodouuu · 8 months ago

我也遇到了同样的问题,有时候claude code在使用bash命令的时候,会重复渲染很多行

Haroong · 8 months ago

Same here

<img width="890" height="668" alt="Image" src="https://github.com/user-attachments/assets/432201ff-0dac-476a-b62b-c898cba64c9e" />

gizim79 · 8 months ago

Confirm the same on Win11/PS7

<img width="1405" height="976" alt="Image" src="https://github.com/user-attachments/assets/41ab4dc3-519e-47f6-b7f5-d9fc67985bb3" />

Baldurans · 8 months ago

+1 to this, I have same issue. Had to downgrade to 2.0.72, seems to work fine there.
Windows 11 PRO (with latest updates), UTF-8 language etc.

Seems to be happening with 2.0.73

Can confirm issue seems to be visual as seen from previous screenshots. If I pipe to a file or ask it to write a file, file contents are correct.

Happens in windows powershell / cmd

gizim79 · 8 months ago

Confirm issue persists throughout PS7, CMD, and Git Bash. Will try to downgrade.

Roritharr · 8 months ago

+1 Same issue.

nvi-nsi · 8 months ago

temporary solve the problem:
npm install -g @anthropic-ai/claude-code@2.0.72

108adams · 8 months ago

confirmed on WezTerm Win 11 - exactly the same rendering problems

github-actions[bot] · 8 months ago

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.