Ctrl + Click not working

[mssource]

Type: Bug

Behaviour

Extension Version any greater thatn 2025.4.0: When clicking on a variable or method call with CTRL+LeftClick, nothing happens.

Steps to reproduce:

1. CTRL+LeftClick on any variable or method call

Diagnostic data

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

2025-06-18 06:06:58.769 [error] Failed to initialize deactivate script C:\Program Files\Git\bin\bash.exe [Error: "c:\Users\XY\.cursor\extensions\ms-python.python-2025.6.1-win32-x64\python_files\deactivate\bash\envVars.txt" file not created
	at Timeout.<anonymous> (c:\Users\XY\.cursor\extensions\ms-python.python-2025.6.1-win32-x64\out\client\extension.js:2:310824)
	at listOnTimeout (node:internal/timers:581:17)
	at process.processTimers (node:internal/timers:519:7)]

Extension version: 2025.6.1
VS Code version: Cursor 1.1.3 (979ba33804ac150108481c14e0b5cb970bda3260, 2025-06-15T06:55:04.603Z)
OS version: Windows_NT x64 10.0.26100
Modes:

• Python version (& distribution if applicable, e.g. Anaconda): 3.12.7
• Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Venv
• Value of the python.languageServer setting: Default

User Settings

languageServer: "Jedi"

testing
• unittestArgs: "<placeholder>"
• unittestEnabled: true

Installed Extensions

Extension Name	Extension Id	Version
cursor-always-local	any	0.0.1
cursor-deeplink	any	0.0.1
cursor-retrieval	any	0.0.1
cursor-shadow-workspace	any	1.0.0
cursor-themes	und	0.0.2
cursor-tokenize	any	0.0.1
debugpy	ms-	2025.8.0
githistory	don	0.6.20
gitlens	eam	17.2.0
js-debug	ms-	1.93.0
js-debug-companion	ms-	1.1.3
jupyter-keymap	ms-	1.0.0
pylint	ms-	2025.2.0
python	ms-	2025.6.1
vscode-js-profile-table	ms-	1.0.9

System Info

Item	Value
CPUs	AMD EPYC 7763 64-Core Processor (4 x 2445)
GPU Status	2d_canvas: unavailable_software canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: disabled_software multiple_raster_threads: enabled_on opengl: disabled_off rasterization: disabled_software raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: disabled_software video_encode: disabled_software vulkan: disabled_off webgl: unavailable_software webgl2: unavailable_software webgpu: unavailable_software webnn: unavailable_software
Load (avg)	undefined
Memory (System)	15.95GB (6.34GB free)
Process Argv
Screen Reader	no
VM	0%

[github-actions]

Hi @mssource, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

---

Potential Duplicate Issues – These issues may be duplicates of your report, but may differ in some of the details.

• Go to Definition now only works if open the entire folder – open a single .py file without its containing folder, then Go To Definition stops working. Go to Definition now only works if open the entire folder  pylance-release#1301

---

Potential Workarounds:

• Open the containing folder of your Python file in VS Code. When the workspace includes the folder, Ctrl+Click (Go To Definition) will function as expected.

---

The team will respond to your issue shortly. Please note this is a trial feature and may not be fully accurate. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or was incorrect, please give it a 👎. Your feedback helps us improve!

[debonte]

Transferring back to vscode-python. User is using Jedi, not Pylance.

[anthonykim1]

@mssource Do you get better luck if you change the language server to Pylance?

[ahuigo]

1. I found that my VS-code is very slow and can not show "go to definition" for python project.

2. So I open my monitor, and found a lot of highly cpu consuming bash processes:

3. Then I run print all my process tree via $ pstree | tee ps.txt, this show there is a large number of pyenv processes

$ pstree | tee ps.txt
 |-+- 04249 user3 bash /opt/homebrew/Cellar/pyenv/2.6.2/libexec/pyenv-exec python3.8 -c import json, sys;print(json.dumps({'version': '.'.join(str(n) for n in sys.version_info), 'sys_prefix': sys.prefix, 'executable': sys.executable, 'is64_bit': sys.maxsize > 2**32}))
 | \-+- 27062 user3 bash /opt/homebrew/Cellar/pyenv/2.6.2/libexec/pyenv-which python3.8
 |   \--- 27075 user3 bash /opt/homebrew/Cellar/pyenv/2.6.2/libexec/pyenv-which python3.8

4. I tried to execute pyenv exec python3.8 -c 'print(1)', it's stuck
5. It reminds me that I used to put pyenv initialization commands (eval "$(pyenv init -)") in ~/.profile
6. After I removing pyenv initialization commands in .profile, all things go well.

[github-actions]

Hey @anthonykim1, this issue might need further attention.

@mssource, you can help us out by closing this issue if the problem no longer exists, or adding more information.

[mssource]

I disabled all python extensions, then activated python from cursor. This then wanted the python extension from microsoft and its dependencies. I installed all the newest extensions mentioned. Now it is running fine.