Microsoft C/C++ Extension Breaks Support for VS Code Forks like VSCodium and Cursor

Here's a summary of the situation described in the article from The Register regarding Microsoft's C/C++ extension for VS Code and its impact on forks like VSCodium and Cursor:

• Issue: As of early April 2025, Microsoft's C/C++ extension for Visual Studio Code (VS Code) no longer works with derivatives such as VSCodium (an open-source fork of VS Code) and Cursor (a commercial AI code editor based on the VS Code codebase). When users of these forks try to install the extension, they receive an error stating it can only be used with Microsoft products.
• Technical Background: The C/C++ extension provides language support (Intellisense, debugging, etc.) for C and C++ in VS Code. The enforcement change occurred with version 1.24.5 (April 3, 2025), which began checking the application environment and enforcing Microsoft's license terms. These terms have restricted extension usage to Microsoft products since September 2020, but only recently have they been technically enforced for the C/C++ extension.
• Similar Precedent: Microsoft's Pylance extension for Python has enforced similar restrictions for years.
• Impact: This move breaks workflows for developers using VS Code forks, making it harder for non-Microsoft editors to support C/C++ out of the box and arguably limiting competition.
• Community and Developer Response:
• Cursor's CEO stated that they are developing and bundling open-source alternatives to Microsoft's closed extensions in response.
• Cursor previously bypassed extension repo restrictions using a reverse proxy, while most forks use Open VSX (an alternative marketplace).
• Some developers have complained to regulators, alleging anti-competitive behavior and self-preferencing by Microsoft.
• VSCodium and Cursor users are seeking open-source, "free as in freedom" alternatives.
• Broader Context: The extension lockout comes amid Microsoft's rollout of competing AI-coding features (Copilot "Agent Mode") bundled with their own ecosystem, further solidifying vendor lock-in concerns.

For more details and current discussion, you can read the full article at The Register

---

Source: The Register https://www.theregister.com/2025/04...9AF6BAgGEAI&usg=AOvVaw0FtJfHMX6k8Q29I7RYXuc2/