Claude Code v2.1.53
Released Feb 25, 2026 (6 months ago).
40 issues reference this build
0 still open
40 resolved (100%)
"References this build" means the issue body mentions running 2.1.53 (from the
bug-report template). It reflects report volume, not a proven defect count — an issue may mention a
version without being caused by it. First-party data from the anthropics/claude-code tracker.
Top issues reported on v2.1.53
Ranked by community engagement (reactions and comments).
- [Bug] Bash tool execution failing or non-functional
- [Bug] EINVAL on Windows: Bash commands fail - cannot open task output file
- [BUG] GitHub Issue: Bash tool EINVAL on Windows
- remote-control fails: node: bad option: --sdk-url
- VS Code Extension: command 'claude-vscode.editor.openLast' not found when clicking Extension UI button
- [BUG] Bash tool EINVAL on Windows persists in v2.1.53 — stdio fd regression from v2.1.45 not fully fixed
- WorktreeRemove hook not invoked for subagent worktrees (isolation: worktree)
- [BUG] Bash tool EINVAL on Windows when project path generates long temp directory name
- [BUG] android mobile app, overlabs issue
- [BUG] Effective usable context window is significantly reduced by infrastructure overhead
- Custom statusLine command stopped working in 2.1.53+
- [BUG] extension.js contains hardcoded CI/CD Linux paths causing activation failure on Windows x64 with Node.js 24 / VS Code 1.109+
- [BUG] `claude remote-control` fails with "node: bad option: --sdk-url"
- [BUG] CLI v2.1.55 fails to connect to VS Code extension WebSocket server (regression from v2.1.53)
- Bash tool fails with EINVAL on Windows (v2.1.53)
- [Bug] Bash tool fails on Windows 11 with EINVAL when writing temp output files
- [BUG] Bash tool fails with EINVAL on Windows - cannot open task output file
- [BUG] tasks/ directory not created automatically on Windows (v2.1.53)
- [BUG] Claude Code 2.1.53 fails to activate on Windows - hardcoded Linux path in extension.js
- remote-control: child process spawn missing cli.js script path
- [BUG] Bash tool returns EINVAL on all commands for specific project directory (Windows)
- [Feedback] Degraded model reasoning and proactive behavior since mid-February
- [BUG] I installed the latest version 2.1.53 in vscode, but it doesn't work. It prompts "command 'claude-vscode.editor.openLast' not found". The version 2.1.49 works fine
- [Bug] Security prompt repeatedly appears despite folder being untrusted
- [BUG] VS Code Claude Code Extension Stopped Working. (TypeError: The argument 'filename' must be a file URL object, file URL string, or absolute path string...)
- [DOCS] Symlinked skill directories under ~/.claude/skills/ work — please document the support level (cf. #41451)
- [BUG] Opus automatically activated in VS Code
- [BUG] The Claude Code Extension for VS Code (v2.1.61) freezes on Windows 11 ARM64.
- File descriptor leak: settings.json opened but never closed on each tool call
- [Bug] Anthropic API Error: KERNEL32.DLL access violation
Changelog
What's changed
- Fixed a UI flicker where user input would briefly disappear after submission before the message rendered
- Fixed bulk agent kill (ctrl+f) to send a single aggregate notification instead of one per agent, and to properly clear the command queue
- Fixed graceful shutdown sometimes leaving stale sessions when using Remote Control by parallelizing teardown network calls
- Fixed
--worktreesometimes being ignored on first launch - Fixed a panic ("switch on corrupted value") on Windows
- Fixed a crash that could occur when spawning many processes on Windows
- Fixed a crash in the WebAssembly interpreter on Linux x64 & Windows x64
- Fixed a crash that sometimes occurred after 2 minutes on Windows ARM64