Detailed Analysis
A bug affecting version 2.1.129 of the Claude Code VS Code extension has prompted community-driven troubleshooting, with users reporting a persistent error message — "command 'claude-vscode.editor.openLast' not found" — accompanied by what appears to be a continuously loading or charging state within the editor. The issue was surfaced on the r/ClaudeAI subreddit, where an affected user documented both the problem and a functional workaround for the Windows platform. The root cause appears to be a regression introduced in the 2.1.129 release that breaks a specific editor command responsible for reopening the last Claude session within VS Code.
The community-identified fix involves downgrading the extension to version 2.1.128, which does not exhibit the broken command behavior. The process requires navigating to the Extensions panel in VS Code, locating the Claude Code extension, accessing its gear icon settings menu, and selecting "Install Another Version..." to manually choose 2.1.128 from the available version history. A subsequent reload of VS Code restores normal functionality. This workflow — while effective — requires a degree of technical familiarity that may present a barrier for less experienced developers relying on the extension in their daily workflows.
The incident highlights a recurring challenge in the rapid release cycles that characterize AI tooling products. Anthropic has been actively developing and updating the Claude Code VS Code extension as part of a broader push to embed AI assistance directly into developer environments, a competitive space that also includes GitHub Copilot, Cursor, and other IDE-integrated tools. Frequent version increments can introduce regressions, particularly in platform-specific environments, with Windows appearing to be the confirmed affected platform in this case — though it is not clear whether macOS or Linux users experienced the same error.
From a broader perspective, the episode reflects the growing dependence of software developers on AI-powered coding assistants and the friction that arises when those tools become unreliable. When a developer's AI extension enters a broken state — especially one that loops or appears to charge continuously — it disrupts workflows in ways that traditional linting or syntax tools typically do not. The fact that the fix was discovered and disseminated through a community forum rather than through an official Anthropic patch or advisory also underscores the degree to which user communities have become first-responders for tooling issues in the fast-moving AI software ecosystem. Official acknowledgment and a patched release in a subsequent version would represent the expected resolution path going forward.
Read original article →