VS Code extension was silently failing to load on Windows (hardcoded SDK path); now fixed. Mantle endpoint x-api-key auth also restored.
Changes
2
Total Changes (vs Average)
0.2×
Version Type
Patch
Release Focus
Bug Fixes
Days Since Prior Release
0
Release # This Month
#4 of 4
Bug Fix Ratio
100%
Post-Release Edits
—
Change Category
Ecosystem Impact
Windows and VS Code have each appeared in 6 of the last 10 releases — a sustained focus on cross-platform IDE reliability that's been a consistent thread through this sprint.
Key Themes
1Windows + VS Code Activation Blocked|1SDK Authentication Patch
May Help If You've Noticed
VS Code extension is installed on Windows but stays completely inactive — no tools, no suggestions
API requests fail with authentication errors even though credentials haven't changed
The VS Code extension worked fine before but stopped responding after a recent Claude Code update on Windows
Changes in Claude Code v2.1.131
Fixed2 changes
•Fixed VS Code extension failing to activate on Windows due to a hardcoded build path in the bundled SDK (createRequire polyfill bug)
•Fixed Mantle endpoint authentication failing with missing x-api-key header