Some extensions are suddenly blocked from Cursor

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

For example maattdd.gitless cannot be searched nor installed in Cursor anymore. It used to work like a week ago or two. This one still works fine on VSCode so I wonder why is Cursor suddenly blocking it?

Steps to Reproduce

  • try searching “gitless” or “maattdd.gitless” on extension marketplace.
  • try importing it into devcontainer.json and see it not installed during the container creation.

Expected Behavior

Should be able to search and install it, just like VSCode does.

Operating System

Windows 10/11
Linux

Version Information

Version: 2.6.21 (user setup)
VSCode Version: 1.105.1
Commit: fea2f546c979a0a4ad1deab23552a43568807590
Date: 2026-03-21T22:09:10.098Z
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, Cursor uses an OpenVSX-compatible marketplace instead of the Microsoft VS Code Marketplace, so extensions that aren’t published on OpenVSX won’t show up in Cursor’s search.

The maattdd.gitless extension isn’t available on OpenVSX, so you won’t be able to find it in Cursor.

Workaround: you can install it manually using a VSIX file. Open VS Code, find the extension in the marketplace, click the gear icon, then select Download Extension. After that, in Cursor open the Command Palette with Ctrl+Shift+P and run Extensions: Install from VSIX....

For devcontainers, it’s the same root cause. Extensions listed in devcontainer.json that aren’t on OpenVSX won’t auto-install. You’d need a post-create command or a similar approach to install the VSIX manually.

If you rely on this extension, you can also reach out to the extension author and ask them to publish it on OpenVSX: https://open-vsx.org/

Thanks for the info. Did the registry change recently? Or maybe the extension just got unavailable recently from there :thinking:

The marketplace switched to OpenVSX in mid-2025. Here’s the announcement post: Extension Marketplace Changes - Transition to OpenVSX. The extension itself was probably never on OpenVSX.

If it was working for you recently, it was likely still installed locally from before the switch, or you installed it via VSIX at some point. Once you remove it or move to a new environment like a devcontainer, it can’t be downloaded again from the marketplace because it isn’t published there.

1 Like