[BUG] Terminal Input and Visual Bugs with python's Textual Library

Resolved 💬 10 comments Opened Jun 30, 2025 by maltseasy Closed Aug 20, 2025

Environment

  • Platform (select one):
  • [X] Anthropic API
  • [ ] AWS Bedrock
  • [ ] Google Vertex AI
  • [ ] Other: <!-- specify -->
  • Claude CLI version: 1.0.35
  • Operating System: macOS 15.5
  • Terminal: Warp with zsh

Bug Description

Terminal inputs and display gets irreversibly messed up when claude runs a python file which launches a textual app. The display leaves fragments of the application after claude has finished executing it. Additionally, mouse movements over the terminal now input characters.

Steps to Reproduce

  1. Make any textual app with python in a project folder.
  2. Start claude code in that folder, go through all init steps.
  3. Ask claude to run the app.

Expected Behavior

It will run successfully, claude should be able to parse what it saw on the terminal app it ran, then once it's done we should be able to use claude code normally.

Actual Behavior

It ran it, not sure if claude was able to properly parse the app, but once it was done running it the terminal was completely messed up.

Additional Context

<img width="1509" alt="Image" src="https://github.com/user-attachments/assets/e4100e03-f266-4cc5-826e-ea6f71de1f8e" /> The text in the input box was created, at a very fast rate, when mouse movements over the terminal happened. Typing and input still works fine.

View original on GitHub ↗

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