[BUG] Claude code 2.0.2 can't type input

Open 💬 22 comments Opened Oct 1, 2025 by GWJian

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] I am using the latest version of Claude Code

What's Wrong?

Claude code 2.0.2 can't type input

<img width="1893" height="315" alt="Image" src="https://github.com/user-attachments/assets/2c7af418-02fd-4f16-8632-0398b04ee961" />

What Should Happen?

able type in box

Error Messages/Logs

Steps to Reproduce

  1. Run claude in therminal

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.0.1 (Claude Code)

Claude Code Version

2.0.2 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_

View original on GitHub ↗

22 Comments

olalinde · 9 months ago

workaround is to add a command as a parameter. E.g., "claude /status".
Then you will be able to type again.

flowerwOw0316 · 9 months ago

Claude is entering a peak period of bug growth.

liveaffiliates · 9 months ago

Same, rendered program unusable. How do we go back versions.

liveaffiliates · 9 months ago

Did you find a way around this? Cause I'm totally stuck now.

olalinde · 9 months ago
Did you find a way around this? Cause I'm totally stuck now.

It worked to do a claude update, then it went back from 2.0.2 to 2.0.1.
Else, try to add a parameter e.g., "claude /status" then it worked as well in 2.0.2
.

Kaltern75 · 9 months ago

Use 'claude update' - it will automatically downgrade from 2.0.2 to 2.0.1 - presumably this has been added as a workaround for now.

anortham · 9 months ago

Tried the parameter option, tried going back to 2.0.1, neither worked. Unusable on windows now.

aguyinmontreal · 9 months ago

same here

JoMiPeCa · 9 months ago

Mention that there also new reports:

#8657
#8658

gunpal5 · 9 months ago

What a Joke! sonnet 4.5 works great but claude code freezes to make you unproductive.

anortham · 9 months ago

This is still an issue in 2.0.5. Started a new session this morning (windows 10, windows terminal, powershell 7). Worked for about 30 min in that session without a problem. Finished that feature and exited Claude Code. Started claude again to start new work a few min later (same terminal window as before) and I can't type into the new session. Tab doesn't work, starting with claude /status doesn't work. Starting a new terminal window doesn't work.

robsonalvesdevbr · 8 months ago

I have the same issue on Ubuntu 25.10 using the Ptyxis terminal. Interestingly, it was working fine before, but even after rolling back to previous versions, the problem persists. I'm getting really frustrated because I can't use Claude Code. I also tried installing GNOME Terminal, but it had the same issue.

<img width="1554" height="705" alt="Image" src="https://github.com/user-attachments/assets/e5d8ab7d-a6fc-40b7-8bc7-d45ce4e9d9cb" />

bzbetty · 8 months ago

Have this in windows in 2.0.34 on a specific project. Hitting enter after opening makes it work.

zerobell-lee · 8 months ago
Have this in windows in 2.0.34 on a specific project. Hitting enter after opening makes it work.

Thanks a lot. It worked for me.

matburnicki · 7 months ago

I'm observing this issue on Claude code 2.0.47 on Windows 11 with PowerShell 7.5.4 and Windows Terminal 1.23.12811.

Sometimes hitting enter doesn't help, but then hitting TAB does make it work again.

I think it mostly happens when I resume a conversation with hundreds of messages.

github-actions[bot] · 6 months ago

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

fsayfitdinov · 6 months ago

Still has it in 2.0.75

sselvanathan · 6 months ago

the issue persists in 2.0.76

KeremKahraman9 · 6 months ago

I can't add "@" sign to claude code line. has anyone else encountered this problem? my current version is v2.1.2.

MarcoLuthi · 6 months ago

Have this issue with macOS v2.1.6 (It's only on the one computer and it's been persisting since v2.0.2)

asumaran · 5 months ago

it just happened to me on 2.1.39 can't do anything

strawhatmaceo · 1 month ago

it happens in 2.1.153