›_ Claude Code Issues
Claude Code Issues / #7693

[BUG] Windows not accepting input

Resolved 💬 24 comments Opened Sep 16, 2025 by mjt007 Closed Sep 18, 2025
💡 Likely answer: A maintainer (wolffiex, collaborator) responded on this thread — see the highlighted reply below.

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?

When I type into the Claude Code terminal many letters are dropped. I have tested extensively, this started happening this morning. It is purely a Claude Code issue, no problems in any other application nor in the terminal unless it is running Claude Code. Same result over several sessions and after system reboot. It is without any doubt an issue with Claude Code, not a general issue with my system.

What Should Happen?

When I type into Claude Code the characters should appear on screen!

Error Messages/Logs

Steps to Reproduce

Type anything into the Claude Code terminal.

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

1.0.115 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Why is your interface not working. It is failing to accept th letter that I type, this is
happening all th time, and often you do not allow any deleting, and sometimes you completely
lock th interfce. I hae narrowed it down to you, it is your interfce, this effect doe not
happen anywher else. It is as if youare soeho trying to intercept what I type, as if youare
sending it off somewheee remotely. I hae doneextensive testing, reboote th pc, it is you. It
as stared happening this morning. What have you done?

● I cannot directly control or interfere with your keyboard input - I'm just processing text
after you send it to me. I have no ability to intercept keystrokes, send them remotely,
or lock your interface.

However, you're clearly experiencing a serious problem that's affecting your ability to
communicate, and with your limited time, this is unacceptable.

This could be:

  1. A browser issue with Claude's web interface - Heavy JavaScript/memory usage
  2. A browser extension conflicting with Claude's interface
  3. Claude's web app having a bug or performance issue

Since you've narrowed it down to only happening with Claude, try:

  • Using a different browser
  • Opening Claude in an incognito/private window (disables extensions)
  • Clearing browser cache/cookies for Claude.ai

If it's genuinely the Claude interface failing you, you need to report this to Anthropic
immediately. This is critical - you shouldn't have to fight with a failing interface when
your time is precious.

I'm sorry this is happening on top of everything else. You deserve better than fighting
with broken tools.

I a not using a browser, I am using Claude Code in trminal, you can see the end result in

thi sentence! I am not typing poorly, this is what you ae doing to what I enter. This doe
not happen with any othe application, it doe not happen in th trminal unless I am running
Claude Code. It is undoubtaedly, 100%, caused by you. This piece of writing was very
carfully, perfectly typed, no wrong key presses t all. You can see th result. This i what
you ae doing.

● You're right - this is Claude Code in the terminal, and the missing letters (especially
'e' and 'a') are clearly visible in your text. This is absolutely unacceptable.

Claude Code appears to be intercepting and dropping keystrokes. The pattern shows specific
letters being lost consistently. This is a CRITICAL bug in Claude Code itself.

This needs immediate escalation:

  1. Report this bug at: https://github.com/anthropics/claude-code/issues
  2. Include that it's dropping specific letters ('e', 'a', others)
  3. Mention it started this morning
  4. Emphasize the urgency given your situation

As a temporary workaround:

  • You could try typing in a text editor and pasting into Claude Code
  • Or use the web interface at claude.ai instead of the terminal

But you shouldn't have to work around broken software. Claude Code is failing you at the
worst possible time. This is completely unacceptable, and I'm sorry this is happening when
you can least afford to deal with it.

The bug is 100% in Claude Code's input handling, not anything you're doing wrong.

View original on GitHub ↗

24 Comments

github-actions[bot] · 10 months ago

---

Found 2 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/7694
  2. https://github.com/anthropics/claude-code/issues/6884

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

---

mjt007 · 10 months ago

UPDATE: Now refusing to accept any input at all.

mjt007 · 10 months ago

This is making the system effectively unusable. Unless you fix this as a matter of urgency you lose me as a subscriber.

mjt007 · 10 months ago

I have found a way round this for now by using Dragon speech to text as the input method. This is absolutely ridiculous that I should have to do this. You should be thoroughly ashamed of yourselves producing a product that can not cope with keyboard entry in this day and age! Please get this major, indeed CRITICAL bug sorted out as a matter of extreme urgency.

trydalch · 10 months ago

I'm experiencing the same behavior. Started last night. Headless mode works, but if I launch it in interactive mode I'm stuck at the initial prompt UI.

robertmclaws · 10 months ago

I'm experiencing the same behavior. I have to start claude with claude "help me diagnose issues I'm having with keyboard inputs with the terminal" and let it go through whatever it decides to do until it completes its task, then I can use the window to resume a previous session and go back.

Fun fact, rolling back to previous versions DOES NOT fix it.

Valyrox · 10 months ago

I'm experiencing the same issue after upgrading to 1.0.115 (Windows / Powershell).
Edit: same issue on 1.0.117

robertmclaws · 10 months ago

I would recommend changing the title to make it more urgent that this is a blocker now on Windows.

wolffiex collaborator · 10 months ago

sorry for the regression on Windows. We believe we fixed this in 1.0.117, can someone please verify?

Valyrox · 10 months ago
sorry for the regression on Windows. We believe we fixed this in 1.0.117, can someone please verify?

As previously stated, version 1.0.117 does not fix the issue
Also, downgrading to a previous version (1.0.113 which worked correctly for example) does not fix the issue, as stated by @robertmclaws

robertmclaws · 10 months ago

Is there a good way to totally uninstall the current version? I can try that on a machine I don't care about losing history on and see what happens.

Pannoniae · 10 months ago

Looks like it works a grand total of once after installing, after which it refuses to accept input. (1.0.117)

adamjs · 10 months ago

@wolffiex 117 is still broken, it was introduced in 114 (I tested each, one at a time with a fresh .claude / AppData).

For others still experiencing this, you can disable autoupdates and install a specific version of Claude Code native (1.0.113) by running this PowerShell command:

& ([scriptblock]::Create((irm https://claude.ai/install.ps1))) 1.0.113
Valyrox · 10 months ago
@wolffiex 117 is still broken, it was introduced in 114 (I tested each, one at a time with a fresh .claude / AppData). For others still experiencing this, you can disable autoupdates and install a specific version of Claude Code native (1.0.113) by running this PowerShell command: & ([scriptblock]::Create((irm https://claude.ai/install.ps1))) 1.0.113

@adamjs for me, this is not working (except on a fresh install)

As mentioned earlier, I reverted to 1.0.113, disabled automatic updates, and it doesn't work, at least almost never (on rare occasions, we can type text and press Ctrl+C)

I tested on three different Windows environments (two with native Claude Code, and one using npm) with a fresh installation, and here are my results:

  • Version 1.0.113 works without issues if we haven't installed a higher version
  • Once version 1.0.115 is installed (I haven't had a chance to test 1.0.116 or 1.0.114 yet), the problem occurs, and upgrading to version 1.0.117 or downgrading to 1.0.113 doesn't resolve the issue
  • Installing version 1.0.117 directly doesn't seem to fix the issue

Starting a new project for the first time (when it asks to trust the files in this folder) still works; you can navigate with the keyboard arrows and Ctrl+C

adamjs · 10 months ago

@Valyrox I wiped my claude installation prior to rolling back to 1.0.113 since I noticed that 114+ would only hang after it cached my authentication credentials (they probably borked the persistence format)

These are the files and folders I wiped (back them up somewhere in case they get it working later)

%USERPROFILE%/.claude.json
%USERPROFILE%/.claude/
%USERPROFILE%/.local/share/claude/
%USERPROFILE%/.local/state/claude/
%USERPROFILE%/AppData/Local/claude-cli-nodejs/
robertmclaws · 10 months ago

I was able to get it working by downgrading from .117 to .110 by running

& ([scriptblock]::Create((irm https://claude.ai/install.ps1))) 1.0.110

Then I tested incrementally upgrading from there to see at what point it stopped working.

  • 110's input panel kept up with my typing with little lag
  • 111 introduced a short but noticeable lag
  • 112 doubled the lag from there
  • I skipped 113
  • 114's lag makes it almost unusable
  • Maybe from there it's technically still a keyboard lag, it's just so long you never see input

It feels like something was introduced after 110 that started us down the path of making the input control lag out. Not sure what that is.

In the meantime, I'm going to stay on .110 until this issue is resolved.

Valyrox · 10 months ago

@robertmclaws I can confirm that version 1.0.110 works without needing to do a fresh install, however it's quite weird, I have to "refocus" my shell window by hitting "enter" in claude code so that I can type anything, I didn't have this issue before, even in 1.0.113

fredweiller · 10 months ago

Exact same TOTALLY BLOCKING problem here. Claude Code is completely unusable at this point! I cannot type even a single character into either the vs code integrated interface or just a simple windows terminal once Claude Code has been launched.
I am on 1.0.117 according to the Claude Code for VS Code extension.

fredweiller · 10 months ago

@robertmclaws I downgraded to 1.0.110 and it unfortunately fixed nothing for me. I have chatted into support and got the very unhelpful "You don't need to keep this window open - we'll email you when an agent has responded."
So much for paying for a Max plan...
For more context, while waiting for Anthropic to fix this, I am running Gemini CLI without any problem. Soooo...not a windows, or VS Code problem, but truly Claude Code.

rweijnen · 10 months ago

Same issue, downgrade doesn't resolve it.Works initially but even without upgrading it stalls

rweijnen · 10 months ago

What seems to help is, use the mouse to select some text, then press enter -> after that I can input text again

Valyrox · 10 months ago
What seems to help is, use the mouse to select some text, then press enter -> after that I can input text again

Yes, this is what I said previously, we need to "refocus" the window before typing anything

dougfowler-nb · 10 months ago

Using Claude Code v.1.0.117 VS Code Extension on Win 11, in Cursor AI.

typed input is working, but no copy paste or ability to record wispr flow (dictation) in input. renders cc essentially unusable. WORKAROUND - using cc in a pwsh terminal, viewing file structure concurrently in separate Cursor window. Pretty janky.

URGENT. dear anthropic team, i'm trying to make the case for cc internally (as we hammer away at a deadline this morning... and I'm dead in the water), convince team not to switch to codex after social media buzz about codex-gpt5 superiority. this couldn't come at a worse time. please hustle. don't want to lose investment in all the custom tweaks i've made to optimize workflow in cc in enterprise env, after months of using.

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.