Fix for Claude VS Code Extension Error: 'command claude-vscode.editor.openLast not found'

The Claude VS Code extension version 2.1.51 has a bug that prevents it from loading properly, causing the error message "command 'claude-vscode.editor.openLast' not found" when users try to interact with it.
What's happening
Version 2.1.51 introduced a breaking bug that causes the extension to crash immediately on startup. This failure prevents the extension from registering its UI commands with VS Code. When users attempt to use the extension, VS Code throws the error because it can't find the registered commands.
The bug appears to be caused by a hardcoded path error in the extension's core files. According to reports, this issue largely affects Windows users.
How to fix it
To restore functionality while waiting for Anthropic to release a patch:
- Open the Extensions tab in VS Code
- Find "Claude Code" and click the gear icon ⚙️
- Click "Install Another Version..."
- Select version 2.1.49 from the dropdown list
- Reload VS Code
This downgrade to version 2.1.49 resolves the issue and returns the extension to normal operation.
📖 Read the full source: r/ClaudeAI
👀 See Also

Maximizing Value in Claude Code Sessions: Token Efficiency Tips
Learn practical token-saving strategies for Claude Code, including /clear and @-mention files, from Anthropic's official guide.

Qwen 3.5 Tool Calling Fixes for Agentic Use: Server Status and Client-Side Workarounds
A detailed analysis identifies four bugs that break Qwen 3.5 tool calling in agentic setups, tracks server fixes as of April 2026, and provides a client-side Python function to parse XML tool calls when servers fail.

OpenClaw Cost Optimization: Five Settings for Continuous Agent Usage
A developer running OpenClaw continuously on a Raspberry Pi identified five configuration settings that significantly reduced agent costs by optimizing for cost rather than default capability.

Qwen 3.5 122B MoE at 35 t/s on a Single 3090 with ik_llama.cpp MTP
A local stack running Qwen 3.5 122B MoE on a single 3090 at 35 t/s using ik_llama.cpp's fused MoE ops for MTP. Stock llama.cpp showed only +4% improvement; ik's fork yields +20%.