[BUG] Prompt input displays corrupted characters in Windows Terminal (v2.0.73)

Status Fixed / completed
Reported on v2.0.73
Maintainer reply None cached
Activity 3 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?

The prompt input line displays corrupted/missing characters at the beginning of the input. For example, > Work #442 displays as ]Work #442 with a missing or garbled character at the start.

<img width="1901" height="1023" alt="Image" src="https://github.com/user-attachments/assets/881c0f3c-3d7e-4be8-bffd-d396ffa6126b" />

What Should Happen?

Prompt input should display correctly with proper characters (e.g., > Work #442)

Error Messages/Logs

Steps to Reproduce

Install Claude Code 2.0.73
Open Windows Terminal (either Git Bash or PowerShell profile)
Run claude
Type any text in the prompt input
Observe corrupted character at the beginning of the input line

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

v2.0.72

Claude Code Version

v2.0.73

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

Workaround:
Downgrading to version 2.0.60 (or 2.0.72) resolves the issue.

View original on GitHub ↗

3 Comments

github-actions[bot] · 10 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/14556
  2. https://github.com/anthropics/claude-code/issues/14440
  3. https://github.com/anthropics/claude-code/issues/8618

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

rubrical-worker · 10 months ago

#14556 is the same issue.

github-actions[bot] · 9 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.