Python: Select Interpreter command doesn't work and is not saved

[bitadmiral]

This morning after restarting extensions in my VS Code, my workspace is now broken. It is using the wrong Python interpreter and I cannot change it. I've been using uv to manage my virtual environments in my VS Code workspaces successfully up to now.

I'm trying to reset my Python interpreter for my workspace back to what it was using Python: Select Interpreter. It does not list the .venv folder that is right in the root of my workspace, which is also the root of my git repo. So I must go find it in the filesystem using the system file dialog:

After I change this to the correct .venv folder by "Enter interpreter path...", none of my library references are resolved. So I restart VS Code and reopen my workspace only to find this setting is set back to the system interpreter, /usr/bin/python! I've tried resetting the interpreter at both the workspace level and the individual folder level in the workspace, but they all get reset upon restart.

By the way, after restarting my extensions this morning, this section appeared in an otherwise empty .vscode/settings.json file in the root of my workspace/repo:

{
    "python-envs.pythonProjects": [
        {
            "path": "",
            "envManager": "ms-python.python:system",
            "packageManager": "ms-python.python:pip"
        }
    ]
}

There is no information about how to make this work for uv, and browsing the typescript code in this repo didn't offer any help. Documentation for python.defaultInterpreterPath says we should use VS Code's "internal storage" to set the Python Interpreter using the Python: Select Interpreter command.

My Python extension versions:

• Python (ms-python.python): 2026.0.0
• Python Environments (ms-python.vscode-python-envs): 1.17.10221016

VS Code Version:

Version: 1.108.1
Commit: 585eba7c0c34fd6b30faac7c62a42050bfbc0086
Date: 2026-01-14T14:55:44.241Z
Electron: 39.2.7
ElectronBuildId: 12953945
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Linux x64 6.8.0-1044-aws

[bitadmiral]

After downgrading Python Environments extension to 1.16.0 by switching to Release Version (disabling Pre-Release), and deleting that auto-created .vscode/settings.json file, and then restarting extensions, all my library references are now resolved again in my workspace.