VS Code discovers Conda environments but Python: Select Interpreter does not display them

@StellaHuang95 已經在處理了。

開始於 2026年8月5日。

Does this issue occur when all extensions are disabled?: N/A, need python extension to get it to work

# VS Code discovers Conda environments but Python: Select Interpreter does not display them

## Environment

- VS Code: 1.130.0
- OS: macOS (Apple Silicon)
- Conda: 26.3.2
- Python Environments extension: 1.36.0
- Python extension: current release at time of filing
- Pylance: current release at time of filing

## Problem

VS Code no longer displays my Conda environments in the interpreter picker.

When I run **Python: Select Interpreter**, I only see:

- System Python
- Any interpreter that was manually selected previously
- Enter Interpreter Path
- Create Virtual Environment

My Conda environments are not listed.

However, manually selecting an interpreter by path works correctly.

For example, if I manually select:

```text
/envs//bin/python
```

the environment works normally afterward.

The issue is specifically that discovered Conda environments are not shown in the interpreter picker.

## Steps to Reproduce

1. Install Miniforge/Conda and create one or more Conda environments.
2. Verify that the environments exist:

```bash
conda env list
```

3. Open VS Code.
4. Install and enable:
- Python
- Python Environments
- Pylance
5. Open a workspace/folder.
6. Run:

```text
Python: Select Interpreter
```

## Expected Behavior

All discovered Conda environments should appear in the interpreter picker.

For example:

```text
base

...
```

## Actual Behavior

The interpreter picker only displays:

```text
System Python
Enter Interpreter Path
Create Virtual Environment
```

along with any interpreters that were manually selected previously.

Discovered Conda environments are not shown.

## Evidence From Logs

The Python Environments extension reports that Conda environments are being discovered successfully:

```text
Environment discovery complete: 9 environments found (Global: 1, Conda: 8)
```

Example log entries:

```text
Using conda from persistent state: /bin/conda

Found named environment:
Found named environment:
Found named environment:

Discovered env:
/envs//bin/python

Discovered env:
/envs//bin/python

Discovered env:
/envs//bin/python
```

The logs indicate that environment discovery is functioning correctly, but the discovered environments are not displayed in the interpreter picker UI.

## Troubleshooting Already Attempted

Verified Conda is functioning correctly:

```bash
conda env list
```

returns all expected environments.

Verified Conda executable is present:

```bash
which -a conda
conda info --base
```

Both return expected results.

Verified the integrated VS Code terminal can use Conda normally.

Verified that manually selecting an interpreter path works and the selected environment functions correctly.

Executed:

```text
Python: Clear Workspace Interpreter Setting
```

and then:

```text
Developer: Reload Window
```

Deleted the Python Environments extension cache:

```text
~/Library/Application Support/Code/User/globalStorage/ms-python.vscode-python-envs
```

Deleted VS Code workspace storage:

```text
~/Library/Application Support/Code/User/workspaceStorage
```

Restarted VS Code.

Reinstalled VS Code completely.

Issue persists.

## Additional Notes

The problem appeared suddenly after previously working correctly.

The integrated terminal is able to use Conda normally, and the Python Environments extension consistently reports successful Conda environment discovery.

This appears to be an issue where discovered Conda environments are not being surfaced in the interpreter picker UI despite being successfully discovered by the Python Environments extension.