Cursor Pyright automatically installed even I uninstall it

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hey all
I’ve don’t want to use Cursor Pyright at all and use ty as LSP + type checker. You cannot guess how many times I uninstalled Cursor Python extention, but it still auto installed on next Cursor IDE launch.

I’ve tried these multiple times:

  1. Uninstalled it - it reinstalled without permission
  2. Disabled it - it auto enabled without permission
  3. Disabled then uninstalled - same result.

What is correct way to get rid of this extension fully?

Steps to Reproduce

Uninstall Cursor Python extension

Expected Behavior

It’s uninstalled and never installed again without permission

Operating System

MacOS

Version Information

Version: 2.5.17
VSCode Version: 1.105.1
Commit: 7b98dcb824ea96c9c62362a5e80dbf0d1aae4770
Date: 2026-02-17T05:58:33.110Z
Build Type: Stable
Release Track: Default
Electron: 39.3.0
Chromium: 142.0.7444.265
Node.js: 22.21.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, this is by design. Cursor Pyright is a built-in extension that replaces Pylance, which isn’t available in Cursor due to Microsoft licensing. If you remove it, it’ll get reinstalled automatically because ms-python.python depends on it.

The right approach is to disable it, not uninstall it. Like our engineer recommended in a similar thread: The Anysphere Pyright extension is like herpes, how to uninstall it forever?

  1. Disable the Cursor Python extension, don’t uninstall it
  2. In settings.json, set "python.languageServer": "None" so ms-python won’t try to start Pyright
  3. Optional: set "cursorpyright.analysis.typeCheckingMode": "off" to turn off diagnostics

You mentioned that disabling also doesn’t stick and the extension auto-enables after restart. Can you double-check? Disable should persist. If the extension really turns itself back on after restarting Cursor, that’s a bug. Tell me what exactly happens after a restart with the extension disabled.

Thank you for your response. I’ll try disabling again (+ other steps mentioned) and see how that behaves this time

1 Like

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.