Describe the Bug
Microsoft python extensions don’t work when disabling Anysphere Cursor Pyright. This may or may not be due to Zscaler or other corporate security settings on this machine, but these issues don’t affect the same extensions in plain VSCode.
Steps to Reproduce
Disable the Anysphere Python extension while having Microsoft’s python extension installed, attempt any language server thing…
workbench.desktop.main.js:12343 [Extension Host] rejected promise not handled within 1 second: ConnectError: [internal] self signed certificate in certificate chain
Thf @ workbench.desktop.main.js:12343
$logExtensionHostMessage @ workbench.desktop.main.js:12343
_doInvokeHandler @ workbench.desktop.main.js:13027
_invokeHandler @ workbench.desktop.main.js:13027
_receiveRequest @ workbench.desktop.main.js:13027
_receiveOneMessage @ workbench.desktop.main.js:13027
(anonymous) @ workbench.desktop.main.js:13027
_deliver @ workbench.desktop.main.js:49
fire @ workbench.desktop.main.js:49
fire @ workbench.desktop.main.js:12360
(anonymous) @ workbench.desktop.main.js:15027
workbench.desktop.main.js:12343 [Extension Host] stack trace: ConnectError: [internal] self signed certificate in certificate chain
at o.from (/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-always-local/dist/main.js:2:835767)
at B (/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-always-local/dist/main.js:2:341125)
at ClientHttp2Session.a (/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-always-local/dist/main.js:2:350072)
at ClientHttp2Session.emit (node:events:519:28)
at emitClose (node:internal/http2/core:1164:10)
at process.processTicksAndRejections (node:internal/process/task_queues:90:21)
Thf @ workbench.desktop.main.js:12343
$logExtensionHostMessage @ workbench.desktop.main.js:12343
_doInvokeHandler @ workbench.desktop.main.js:13027
_invokeHandler @ workbench.desktop.main.js:13027
_receiveRequest @ workbench.desktop.main.js:13027
_receiveOneMessage @ workbench.desktop.main.js:13027
(anonymous) @ workbench.desktop.main.js:13027
_deliver @ workbench.desktop.main.js:49
fire @ workbench.desktop.main.js:49
fire @ workbench.desktop.main.js:12360
(anonymous) @ workbench.desktop.main.js:15027
workbench.desktop.main.js:12357 [anysphere.cursor-always-local][internal] self signed certificate in certificate chain
$onExtensionRuntimeError @ workbench.desktop.main.js:12357
_doInvokeHandler @ workbench.desktop.main.js:13027
_invokeHandler @ workbench.desktop.main.js:13027
_receiveRequest @ workbench.desktop.main.js:13027
_receiveOneMessage @ workbench.desktop.main.js:13027
(anonymous) @ workbench.desktop.main.js:13027
_deliver @ workbench.desktop.main.js:49
fire @ workbench.desktop.main.js:49
fire @ workbench.desktop.main.js:12360
(anonymous) @ workbench.desktop.main.js:15027
workbench.desktop.main.js:12357 ConnectError: [internal] self signed certificate in certificate chain
at o.from (/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-always-local/dist/main.js:2:835767)
at B (/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-always-local/dist/main.js:2:341125)
at ClientHttp2Session.a (/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-always-local/dist/main.js:2:350072)
at ClientHttp2Session.emit (node:events:519:28)
at emitClose (node:internal/http2/core:1164:10)
at process.processTicksAndRejections (node:internal/process/task_queues:90:21)
$onExtensionRuntimeError @ workbench.desktop.main.js:12357
_doInvokeHandler @ workbench.desktop.main.js:13027
_invokeHandler @ workbench.desktop.main.js:13027
_receiveRequest @ workbench.desktop.main.js:13027
_receiveOneMessage @ workbench.desktop.main.js:13027
(anonymous) @ workbench.desktop.main.js:13027
_deliver @ workbench.desktop.main.js:49
fire @ workbench.desktop.main.js:49
fire @ workbench.desktop.main.js:12360
(anonymous) @ workbench.desktop.main.js:15027
workbench.desktop.main.js:55 ERR An unknown error occurred. Please consult the log for more details. {name: ‘ConnectError’, rawMessage: ‘self signed certificate in certificate chain’, code: 13, metadata: {…}, details: Array(0), …}
error @ workbench.desktop.main.js:55
error @ workbench.desktop.main.js:55
error @ workbench.desktop.main.js:14986
handleUnexpectedError @ workbench.desktop.main.js:14983
(anonymous) @ workbench.desktop.main.js:14983
onUnexpectedError @ workbench.desktop.main.js:27
al @ workbench.desktop.main.js:22
$onUnexpectedError @ workbench.desktop.main.js:12357
_doInvokeHandler @ workbench.desktop.main.js:13027
_invokeHandler @ workbench.desktop.main.js:13027
_receiveRequest @ workbench.desktop.main.js:13027
_receiveOneMessage @ workbench.desktop.main.js:13027
(anonymous) @ workbench.desktop.main.js:13027
_deliver @ workbench.desktop.main.js:49
fire @ workbench.desktop.main.js:49
fire @ workbench.desktop.main.js:12360
(anonymous) @ workbench.desktop.main.js:15027
workbench.desktop.main.js:15371 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
Expected Behavior
It should work.
Operating System
Linux
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.2.43 (Universal)
VSCode Version: 1.105.1
Commit: 32cfbe848b35d9eb320980195985450f244b3030
Date: 2025-12-19T06:06:44.644Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0
Does this stop you from using Cursor
Yes - Cursor is unusable