Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
It seems that when an extension fails to install inside the container, the “outer” Cursor process attempts to download it externally rather than installing it within the container. In general, this fallback mechanism works well, but in a specific case it appears to trigger an infinite loop of extensionquery requests, which prevents the extension from being installed.
Steps to Reproduce
When installing anysphere.cursorpyright inside the container, the installation fails (I’ll explain why shortly). As a result, Cursor attempts to resolve all of the extension’s dependencies in order to download them.
The dependency chain looks like this:
When trying to install anysphere.python (which seems to be actually ms-python.python) the dependencies are [ms-python.vscode-pylance, ms-python.debugpy].
When trying to install ms-python.vscode-pylance (which seems to be actually anysphere.cursorpyright) the dependencies are anysphere.python.
This circular dependency (anysphere.python ↔ anysphere.cursorpyright) causes endless manifest requests.
Expected Behavior
Solving the circular dependency, resulting in being able to install the extension.
Screenshots / Screen Recordings
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.5.9
VSCode Version: 1.99.3
Commit: de327274300c6f38ec9f4240d11e82c3b0660b20
Date: 2025-08-30T21:02:27.236Z (3 days ago)
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.2.0
Additional Information
Root cause of the initial failure:
The extension fails to install inside the container because we work behind a corporate proxy, and Cursor doesn’t trust our internal CA. Normally, this isn’t a problem since extensions are installed via the outer Cursor process, which does trust our CA (OS certificate store). However, for extensions that eventually depend on anysphere.python (such as the isort extension), the installation fails.
This setup is usually convenient, since our production image doesn’t require our CA in production—only for local development.
Workaround attempt:
As a patch, we tried to trust the CA certificate inside the container, but we weren’t able to get Cursor to recognize it. Setting Node.js environment variables didn’t help, nor did adding the certificate to the image and updating with update-ca-certificates.
Also tried following the same method specified here - Fiddler Everywhere Setting Up the Root Certificate for Electron Applications on Ubuntu - Progress Telerik Fiddler Everywhere but that didn’t work as well.
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor