Autocomplete does not work when using Jedi as the Python language server

[Faravah]

Type: Bug

Behaviour

Autocomplete stops working when Jedi is set as the language server

Steps to reproduce:

1. Install Python extension

2. set the language server to Jedi:

{
"python.languageServer": "Jedi"
}

Diagnostic data

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

XXX

Extension version: 2025.12.0
VS Code version: Code 1.103.2 (6f17636121051a53c88d3e605c491d22af2ba755, 2025-08-20T16:45:34.255Z)
OS version: Linux x64 6.12.43+deb13-amd64
Modes:

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

User Settings

languageServer: "Jedi"

Installed Extensions

Extension Name	Extension Id	Version
autopep8	ms-	2025.2.0
black-formatter	ms-	2025.2.0
debugpy	ms-	2025.10.0
EditorConfig	Edi	0.17.4
even-better-toml	tam	0.21.2
flake8	ms-	2025.2.0
isort	ms-	2025.0.0
js-debug	ms-	1.102.0
js-debug-companion	ms-	1.1.3
pylint	ms-	2025.2.0
python	ms-	2025.12.0
shellcheck	tim	0.38.3
vscode-js-profile-table	ms-	1.0.10
vscode-pylance	ms-	2025.7.1
vscode-python-envs	ms-	1.2.0

Related issues:

This issues may be related:

• jedi_language_server: -32603: _pickle.UnpicklingError: could not find MARK pappasam/jedi-language-server#347
• bug: jedi completion does not work in python 3.13 REPL davidhalter/jedi#2069

[eleanorjboyd]

@karthiknadig - do you have context here?

[Kidsunbo]

#25450 maybe this is related to this issue

[eleanorjboyd]

#25450 was just merged yesterday so it wouldn't have been shipped out in time- or are you saying thats the fix?

[Kidsunbo]

#25450 was just merged yesterday so it wouldn't have been shipped out in time- or are you saying thats the fix?

well, according to the context of the bug in Jedi language serve, the bug might be related to the semantic tokens in Jedi language server. #25450 disables semantic tokens like the previous version did, so that might be the fix. Not verified.