[BUG] Cant type anymore in claude code

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/7485
2. https://github.com/anthropics/claude-code/issues/7755
3. https://github.com/anthropics/claude-code/issues/2034

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

Same, for now uninstall it and install v2.0.1:

npm i -g @anthropic-ai/claude-code@2.0.1

And make sure to turn off auto updates temporarily until the issue is fixed. You can set this in the settings.json, usually found at ~/.claude/settings.json or Drive/Users/Name/.claude. This is the env var:

  "env": {
    "DISABLE_AUTOUPDATER": "1"
  },

Claude Code oncall here. I can reproduce this issue on Windows preliminarily. Looking into it.

Claude Code oncall here. I can reproduce this issue on Windows preliminarily. Looking into it.

Same. Only on Windows is this a problem for me. On Ubuntu it works fine, haven't tried MacOS yet: https://github.com/anthropics/claude-code/issues/8571

Same problem. I also am using VS Code on Windows 11. Claude Code v2.0.2.

same issue for me, im on windows

same problem, i'm on windows 11 claude 2.0.2

For those of you who encountered the issue, are you:

1. Running through PowerShell, GitBash, the terminal in VSCode, or some other place?
2. Are you running the npm-based Claude Code or the native one (claude.exe)?

My repro has been inconsistent. Thanks for your reports!

For those of you who encountered the issue, are you: 1. Running through PowerShell, GitBash, the terminal in VSCode, or some other place? 2. Are you running the npm-based Claude Code or the native one (claude.exe)? My repro has been inconsistent. Thanks for your reports!

1. Powershell 7
2. npm based Claude Code

1. Terminal in VSCode
2. npm base claude code

Same. Windows 11. Failure happens in vscode, powershell, and bash terminals for me.

npm Claude in each instance.

Same.
Windows 11, powershell, npm 22
It eventually starts responding, but takes about 5 minutes.
I actually did also see this in 2.0.0 and 2.0.1

1. Windows 10, PowerShell, JetBrains WebStorm
2. npm based Claude Code

1. Windows 10, PowerShell, JetBrains WebStorm 2. npm based Claude Code

Surely v2.0.2 is the cause of this problem. I uninstalled CC and reinstalled v2.0.1, and now it's working.

vscode

Rolling back to 2.0.1 fixed this for me. I'm running on Powershell 7 and using npm 11.6.0 to install claude.

I was having luck with Claude a few hours ago, not sure if that was on 2.0.2 though. I remember some can't-type-on-windows issues in the past mentioned the issue could be affected by how clause was exited (ctrl-c vs typing 'exit' vs closing the console) so that might be a variable to experiment with when trying to reproduce the error.

For those of you who encountered the issue, are you: 1. Running through PowerShell, GitBash, the terminal in VSCode, or some other place? 2. Are you running the npm-based Claude Code or the native one (claude.exe)? My repro has been inconsistent. Thanks for your reports!

1. PowerShell, Windows 11
2. npm-based

For me the issue seems to happen when:
Issue #7530 occurs, and I follow the workaround given in this reply. I then cannot type in Claude Code when relaunching, though this seems to be limited to the project folder where #7530 occurred. Opening Claude in my C drive works fine.

I simply stopped working on it yesterday when this occurred as it was already late, and when powering on my computer today it functioned properly. So when it then occurred again today, I attempted to restart my computer but this did not fix it.

Also can confirm, downgrading to 2.0.1 solves it. Going back to 2.0.2 breaks it again.

In version 2.0.3 of New Discovery, if the terminal freezes upon startup, pressing Enter will allow you to type; otherwise, the window remains frozen, preventing any input.

I disabled Malwarebytes and it appears to solve the keyboard input issue somewhat. I noticed that the mba service gets VERY busy. Just a data point.

Specifically, the Malware and PUP protection.

Windows 11, Powershell 7, npm 22

Hi all, v2.0.5 is out now. Please let me know if you still see the same issues from v2.0.2 in this new version. Thanks!

Hi all, v2.0.5 is out now. Please let me know if you still see the same issues from v2.0.2 in this new version. Thanks!

Well, I'm on 2.0.8 and the issue still exists. I can't type anything.

Windows 11 Powershell 7 claude v2.0.8:

I've observed that if I run "claude --continue" or "claude --resume" that the keyboard is unresponsive until I press enter. I did report this issue before and can't be sure if I tried pressing enter previously. Nothing about the screens indicate I should press enter.

@mackcoding can you describe _in a new issue_ more about the setup where you're seeing this in? (which OS, which terminal, a screenshot, whether this is from claude --resume or claude --continue) Thanks!

@howtobearealprogrammer can you file a separate issue for what you describe? It's unrelated to this issue.

@fschwiet I can reproduce what you report. I believe it's related to https://github.com/anthropics/claude-code/issues/6844.

@mackcoding can you describe _in a new issue_ more about the setup where you're seeing this in? (which OS, which terminal, a screenshot, whether this is from claude --resume or claude --continue) Thanks! @howtobearealprogrammer can you file a separate issue for what you describe? It's unrelated to this issue. @fschwiet I can reproduce what you report. I believe it's related to #6844.

The latest (as of Oct 12) seems to fix the issue

@mackcoding can you describe _in a new issue_ more about the setup where you're seeing this in? (which OS, which terminal, a screenshot, whether this is from claude --resume or claude --continue) Thanks! @howtobearealprogrammer can you file a separate issue for what you describe? It's unrelated to this issue. @fschwiet I can reproduce what you report. I believe it's related to #6844.

I am no longer having the issue - I suspect somewhere after 2.0.10 it was resolved

I'm experiencing it in Powershell after I installed the latest Node. It was originally doing alt + m and I wanted to get the shift + tab instead so that's it's uniform across all my machines.

I experienced this issue on my machine:

$ uname -a
Darwin mac.lan 24.5.0 Darwin Kernel Version 24.5.0: Tue Apr 22 19:54:33 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T8122 arm64
$ claude -v
2.0.30 (Claude Code)

I noticed something weird every time I started claude: I would get a prompt to enter my Github username. I'm not sure why this happened. Anyway, I found that I got the ability to type inputs into CC as it should normally function by re-logging into the Github CLI like so:

gh auth login  

And following the prompts to log in (I used an SSH key to get authenticated).

Hope this helps!

Windows 11 Powershell 7 claude v2.0.8: I've observed that if I run "claude --continue" or "claude --resume" that the keyboard is unresponsive until I press enter. I did report this issue before and can't be sure if I tried pressing enter previously. Nothing about the screens indicate I should press enter.

I second this, every input was locked out with no indication When opening claude from new directories but old directories loaded fine. This happened after switching from the node version to the native binary for me. By a stroke of luck I discovered that pressing Enter appears to focus the interface in some way and returns all normal control. As mentioned there's no indication on the screen but pressing enter resolves it completely when it happens.

Often just freezes on macOS in warp too. Sometimes forever, sometimes works after a minute or two

I see the problem when using: Windows 11, Webstorm IDE, Claude Code plugin, native installation.

I just had the same issue with just plain old powershell 7 x64. I was able to type after hitting some keys, seemed to work after pressing the ? on my keyboard and then kept working after each run after that. Windows 11 x64

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.

This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.

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.