[BUG] Windows Terminal/WSL: tui input box rendering corrupted - extends beyond terminal width boundaries

Resolved 💬 2 comments Opened Sep 11, 2025 by salah9003 Closed Sep 11, 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?

Terminal input box rendering is corrupted - the input prompt extends beyond the terminal width boundaries and appears visually broken. The input area does not respect terminal column limits and overlaps with terminal edges.

<img width="1103" height="344" alt="Image" src="https://github.com/user-attachments/assets/3c9f28a4-511f-41f0-acfa-789191aca639" />

What Should Happen?

Input box should be properly contained within terminal width boundaries

Error Messages/Logs

strace output shows duplicate ANSI cursor control sequences:
write(20, "\33[?25h", 6) = 6        # Show cursor
write(20, "\33[?25h", 6) = 6        # Show cursor AGAIN (duplicate)

v1.0.110 working version shows:
write(20, "\33[?25h", 6) = 6        # Show cursor once (clean)

Steps to Reproduce

  1. Open PowerShell in Windows Terminal
  2. Run claude command
  3. Observe the welcome screen and input box rendering

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

1.0.110

Claude Code Version

1.0.111

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Root cause:

Terminal state management regression in v1.0.111. strace analysis shows duplicate ANSI cursor control sequences (\33[?25h sent twice) causing corruption. this breaks width boundary calculations for input box rendering.

technical details: trust dialog introduced synchronized output mode (\33[?2026h) combined with duplicate cursor commands corrupts terminal state restoration.

retelated issues: #7435, #5679, #1509, #4897

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗