Claude Code v2.1.55

Released Feb 25, 2026 (6 months ago).

"References this build" means the issue body mentions running 2.1.55 (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.55

Ranked by community engagement (reactions and comments).

• Remote Control session not visible in session list, cannot reconnect after leaving
  Open 💬 20 👍 33 #28402
• [BUG] command 'claude-vscode.editor.openLast' not found
  Resolved 💬 8 👍 3 #28430
• [BUG] VS Code extension v2.1.55 fails to activate on Windows — hardcoded Linux build path
  Resolved 💬 6 👍 3 #28406
• VS Code extension 2.1.55: Activation fails on Windows due to hardcoded Linux CI paths in extension.js
  Resolved 💬 4 👍 3 #28416
• VS Code extension fails to activate on Windows — hardcoded Linux CI path in extension.js
  Resolved 💬 3 👍 3 #28436
• Remote Control fails on Windows npm install: node.exe bad option --sdk-url
  Resolved 💬 6 👍 2 #28401
• [BUG] On click the claude code icon in vs code getting the error command 'claude-vscode.editor.openLast' not found
  Resolved 💬 8 👍 1 #28417
• Confirmed workaround for Windows (no reinstall needed)
  Resolved 💬 3 👍 2 #28432
• claude auth login does not show prompt for authorization code in Docker containers
  Resolved 💬 5 👍 1 #30369
• VS Code extension commands not working - "command not found" errors
  Resolved 💬 7 #28404
• [BUG] `claude rc` / `claude remote-control` crashes with `node: bad option: --sdk-url`
  Resolved 💬 4 👍 1 #28394
• [BUG] Claude Code VS Code extension v2.1.55 - All commands return "not found" error, extension fails to activate
  Resolved 💬 6 #28454
• [BUG] Regression: "command 'claude-vscode.editor.openLast' not found" returns in v2.1.53 and v2.1.55 (fixed in v2.1.52)
  Resolved 💬 3 👍 1 #28421
• remote-control fails with 'bad option: --sdk-url'
  Resolved 💬 3 👍 1 #28413
• VS Code extension v2.1.55 (win32-x64) fails to activate: hardcoded Linux CI path in extension.js
  Resolved 💬 5 #28441
• [Feature Request] Implement sparse checkout for plugin marketplace repositories to reduce clone size
  Resolved 💬 2 👍 1 #28426
• [BUG] PermissionRequest hook `permission_suggestions` inconsistencies with UI
  Resolved 💬 4 #28464
• Bash tool output suppressed when child process spawns `claude -p`
  Resolved 💬 4 #28407
• [Bug] Card code for VS code not executing
  Resolved 💬 4 #28399
• [BUG]
  Resolved 💬 3 #68507
• [Windows] Blank VS Code windows open on startup — missing ELECTRON_RUN_AS_NODE=1
  Resolved 💬 3 #32705
• [Bug] Anthropic API Error: 500 Internal Server Error
  Resolved 💬 3 #28642
• [Bug] Anthropic API Error: Internal Server Error (500)
  Resolved 💬 3 #28640
• [BUG] "mcpServers" yaml frontmatter in Subagent.md don't work when launching with `--agent` cli command
  Resolved 💬 3 #28503
• [BUG] Extension v2.1.55 is not able to open chat window on windows 11
  Resolved 💬 3 #28460
• [BUG] Autocomplete prompt suggestion includes hallucinated non-English text
  Resolved 💬 3 #28452
• VS Code extension v2.1.55 fails to activate on Windows — hardcoded Linux path in build
  Resolved 💬 3 #28433
• [Feature Request] VS Code terminal tab title should display "Claude" instead of version number
  Resolved 💬 3 #28429
• [BUG] claude remote-control fails on Windows: "bad option: --sdk-url"
  Resolved 💬 3 #28425
• VS Code extension v2.1.55 fails to activate on Windows: hardcoded CI build paths in extension.js
  Resolved 💬 3 #28418

Changelog