I am an extension author and I have two dependent extensions, “ms-python.python”, “ms-python.debugpy”. When I attempt to install my extension on cursor I am struck in an infinite loop installing the extension. I have tried changing extensionDependencies to extensionPack for my extension and that doesn’t seem to help as well. This thread describe the same issue as mine but was closed because of no activity
but he has the same problem as me.
Any advice on how to add dependencies to the extension such that cursor can install it correctly thanks.
Steps to Reproduce
Please try to install any extension that has dependency on “ms-python.python”,
“ms-python.debugpy”
Hey, thanks for the report. This is a known issue. Cursor remaps some Microsoft extensions (ms-python.python → anysphere.python, ms-python.vscode-pylance → anysphere.cursorpyright), and when it resolves dependencies it can hit a dependency cycle.
As a temporary workaround, try installing ms-python.python and ms-python.debugpy manually before installing your extension. If the dependencies are already installed, the install may succeed without trying to resolve them again.
Hmm is there a plan to add a permanant solution, currently as a workaround I am publishing two different versions of my extension on vscode and open vsx market place but would love to get a long term solution for it.
I’m using Cursor on Windows with the WSL extension enabled.
The installation gets stuck at “Installing”, and in the DevTools Network tab I can see repeated POST requests in a loop to: https://marketplace.cursorapi.com/_apis/public/gallery/extensionquery
(all returning 200 OK).
Even after installing the Python extension (ms-python.python) separately first, attempting to install the Mojo extension still remains stuck at “Installing”.
As a temporary workaround, I built and installed a local .vsix from their repository: https://github.com/modular/vscode-mojo.git
This installs and works correctly, which suggests the issue is related to the marketplace dependency-resolution/install flow rather than the extension package itself.
It would be great if this problem could be investigated and fixed.