Describe the Bug
Since updating to Cursor 1.2, the option to use Pylance has been lost and I have been relying on the Anysphere Python type checking extension.
I have 3 extensions installed (anysphere.cursorpyright, ms-python.python and ms-python.debugpy) after wiping all local Cursor settings (using rm -rf ~/Library/Application\ Support/Cursor and rm -rf ~/.cursor) and installing Cursor 1.2 fresh.
I have tried varying Theme, playing around with the settings files, installing basedpyright, changing marketplace to VScode, turning type checking mode to off etc.
Nothing seems to work to have proper Python syntax highlighting. How is this possible?
Steps to Reproduce
Wipe your local settings and install Cursor 1.2 fresh on Mac Darwin arm64
Expected Behavior
Python type checking
Screenshots / Screen Recordings
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.2.2
VSCode Version: 1.99.3
Commit: faa03b17cce93e8a80b7d62d57f5eda6bb6ab9f0
Date: 2025-07-07T06:08:52.104Z (2 days ago)
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 23.2.0
Does this stop you from using Cursor
Yes - Cursor is unusable
Anyone from Cursor able to look? Pretty disappointing.
Bumping this again - anyone from Cursor able to have a look?
I have met same issue as yours. Is there any solutions or methodologies could fix it.?
ChatGPT said:
The issue seems to stem from the missing Pylance extension after upgrading to Cursor 1.2.2. To restore proper Python type checking and syntax highlighting, manually install the Pylance extension by downloading it from the Visual Studio Code Marketplace as a .vsix file, then run cursor --install-extension <path-to-pylance.vsix> in the terminal. This bypasses the Cursor marketplace limitation and restores full Pylance functionality.
Hey, I’m running into the same issue. I keep hitting Python type checking errors with the new version of Cursor, even though the exact same code runs perfectly fine in VSCode. It’s frustrating—it really feels like the update introduced something that’s breaking type checks unnecessarily. I was hoping this update would improve the experience, but instead it’s just getting in the way of my workflow. If anyone’s found a workaround or fix, I’d really appreciate any help.
I got this error when trying to use the suggested method.
Hi @mako284, thanks for sharing this issue and appreciate your patience with this issue.
From your screenshot it looks like builtin imports, but not third party imports, are being resolved. Could you double check that the correct Python interpreter is set for the workspace? You can change the interpreter via this command:
@FarihaAnis – you can set the setting cursorpyright.analysis.typeCheckingMode to “off” to suppress all type errors:
.
Due to restrictions on third party extensions, Pylance is not supported within Cursor. As such, we have released the Python plugin by Anysphere.
