[BUG] Experiencing this same issue on Windows 11.

Resolved 💬 2 comments Opened Feb 6, 2026 by alqode-dev Closed Feb 6, 2026

Preflight Checklist

  • [ ] 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?

Environment

  • OS: Windows 11
  • Affected Claude Code versions: 2.1.31, 2.1.32, 2.1.33, 2.1.34
  • Working version: 2.1.25 (no freeze, but limited to Opus 4.5)
  • Affected editors: Cursor, Windsurf, Antigravity (all VS Code-based integrated terminals)
  • Not affected: Windows Terminal (works perfectly on all versions including 2.1.34)
  • Subscription: Max (paying for Opus 4.6 access but can't use it)

## Steps to Reproduce

  1. Open any VS Code-based editor (Cursor, Windsurf, or Antigravity)
  2. Open the integrated terminal
  3. Run claude
  4. Claude Code UI loads normally — banner, model info, etc. all display
  5. Input is completely frozen — cannot type, cursor doesn't respond
  6. Ctrl+C does not work. Only way out is to kill the terminal

## What I've Tried

  • Reinstalling Claude Code — no fix
  • Clearing cache/config — no fix
  • Pressing Enter immediately after launch — inconsistent results
  • Different VS Code-based editors (Cursor, Windsurf, Antigravity) — all freeze
  • Windows Terminal — works perfectly, confirming this is specific to VS Code integrated terminals
  • Downgrading to 2.1.25 — works, but loses Opus 4.6 access

## Key Observation
This is not a general Windows issue. It is specifically a VS Code integrated terminal issue. The same machine,
same user, same config runs Claude Code flawlessly in Windows Terminal. The regression started exactly at version
2.1.31 — version 2.1.25 has zero issues.

## Impact
I'm forced to use 2.1.25 (which only offers Opus 4.5)
because every version from 2.1.31 onward is unusable in my editor's terminal. This effectively locks me out of a
feature I'm paying for.

A fix or even just a confirmed workaround would be greatly appreciated.

What Should Happen?

Claude Code should load in VS Code-based integrated terminals (Cursor, Windsurf, Antigravity) and accept keyboard
input normally, just like it does in Windows Terminal.

Error Messages/Logs

No error messages are displayed. The UI loads completely (banner, model info, etc.) but the input is silently frozen.
  No crash, no error output. Ctrl+C does not respond. The terminal must be force-killed.

Steps to Reproduce

Steps to Reproduce

  1. Install Claude Code version 2.1.31 or later on Windows 11
  2. Open any VS Code-based editor (Cursor, Windsurf, or Antigravity)
  3. Open the integrated terminal (Ctrl+`)
  4. Run: claude
  5. Wait for the Claude Code UI to fully load
  6. Try to type anything — input is completely frozen, cursor does not respond
  7. Try Ctrl+C — does not work
  8. For comparison, open Windows Terminal and run: claude
  9. Claude Code works perfectly in Windows Terminal with the same version

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.25 — no freeze, input works perfectly in all terminals including VS Code integrated terminals. The regression started at 2.1.31.

Claude Code Version

2.1.25

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Cursor

Additional Information

_No response_

View original on GitHub ↗

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