[BUG] VS Code extension v2.1.129 - command 'claude-vscode.editor.openLast' not found (regression from v2.1.128)

Resolved 💬 8 comments Opened May 6, 2026 by rakusvn-nvkhanh Closed May 6, 2026

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?

After updating the Claude Code VS Code extension to v2.1.129, clicking the Claude Code icon in the editor toolbar shows the error:

"command 'claude-vscode.editor.openLast' not found"

The extension fails to register its commands and becomes unusable.

Version regression observed:

  • v2.1.52 → works correctly
  • v2.1.128 → works correctly
  • v2.1.129 → broken (this bug)

Rolling back to v2.1.128 immediately resolves the issue, which suggests a regression was introduced between v2.1.128 and v2.1.129.

Note: This appears similar to past regressions reported in #28053 and #28421 (which affected v2.1.51, v2.1.53, and v2.1.55).

What Should Happen?

Clicking the Claude Code icon in the VS Code editor toolbar should open the Claude Code panel/last session without any errors, as it does in v2.1.128.

Error Messages/Logs

Steps to Reproduce

  1. Install Claude Code VS Code extension v2.1.129 on VS Code Insiders (Windows)
  2. Open any workspace
  3. Click the Claude Code icon in the editor toolbar
  4. Error toast appears: "command 'claude-vscode.editor.openLast' not found"

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

v2.1.128 (works)

Claude Code Version

  • OS: Windows - Editor: VS Code Insiders - Claude Code VS Code extension: v2.1.129 (broken), v2.1.128 (works)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Workaround: rolling back to extension v2.1.128 via "Install Another Version..." restores functionality.

View original on GitHub ↗

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