Your Questions Answered: VS Code Python Environments Extension April 2026 Update

Welcome to our Q&A on the latest update to the Python Environments extension for Visual Studio Code, released in April 2026. This release brings major improvements in startup speed, reliability, and terminal/package management. We’ve broken down the key changes into easy-to-digest questions and answers so you can quickly understand what’s new and how it benefits your daily workflow. Whether you work on remote containers or local projects, these updates aim to make environment handling smoother and faster. Let’s dive in.

1. What made the extension’s startup noticeably faster in this update?

The April 2026 release slashes startup time through three targeted changes. First, lazy manager discovery means the extension no longer scans for Pipenv, pyenv, or poetry environments as soon as it activates. Instead, detection happens only when you actually interact with those tools—like opening a Pipfile or a pyproject.toml with poetry backend. This eliminates unnecessary work for the majority of users who use venv, uv, or conda. Second, faster environment resolution shortens the path from extension activation to interpreter readiness, reducing overhead during startup and interpreter selection. Third, the default workspace scanning pattern was narrowed from ./**/.venv (which caused deep recursive scans and frequent timeouts on large projects or over Remote-SSH) to simply .venv and */.venv. This covers the standard layout without deep traversal. If you have environments nested deeper, you can add custom paths via the python-envs.workspaceSearchPaths setting. Together, these changes make activation snappy even in remote and containerized workspaces.

Your Questions Answered: VS Code Python Environments Extension April 2026 Update — Source: devblogs.microsoft.com

2. How does the extension handle a crash of the PET process?

Previously, if the Python Environment Tools (PET) process crashed during a refresh, the extension could become stuck in a broken state with no environments visible. The April update introduces robust crash recovery: after a PET crash, the extension now automatically retries the refresh. It also defensively handles empty or malformed responses, so a transient PET failure no longer leaves you with a blank environment list. This means you can keep working without having to reload the window or manually trigger a refresh. The fix addresses issues #1442, #1447, and #1444, making the environment list much more resilient.

3. What was the conda base environment bug and how was it fixed?

A subtle bug (#1412) affected the conda base environment after a window reload. The extension could incorrectly restore the base environment as a different named environment, making it appear that your interpreter selection had silently changed. This was confusing and could lead to running code with the wrong Python interpreter. The April 2026 update corrects this by ensuring the conda base environment is properly identified and restored to its correct state after a reload. Now your interpreter selection stays exactly as you left it, eliminating that silent surprise.

4. Does the package view now update automatically after installing or uninstalling packages?

Yes, one of the most requested quality-of-life improvements is here. You no longer need to manually refresh the package view after running pip install or pip uninstall. The extension now watches for metadata changes inside site-packages and triggers an automatic refresh of the package list. This means after you run a pip command in the terminal, the installed packages view updates in near real-time, keeping your environment overview accurate without extra clicks. This feature is tracked in issue #1420 and makes package management feel much more fluid.

5. How does multi-project terminal creation work now?

In workspaces that contain multiple Python projects, creating a new terminal used to silently pick an environment, which could be the wrong one for your current task. The April update changes this behavior: when you create a new terminal in a multi-project workspace, the extension now prompts you to choose which project’s environment to activate. This simple prompt prevents confusion and ensures each terminal starts with the correct Python environment and dependencies for the project you’re working on. It’s a small but powerful improvement for developers juggling several projects in one workspace.

6. What PowerShell activation fix was made for Windows users?

Activating a virtual environment via PowerShell on Windows could fail if the system’s execution policy blocked scripts—a common security setting. The extension now sets a process-scoped execution policy before running the activation script, allowing the .ps1 activation file to run without changing the system-wide policy. This means fewer activation failures and a smoother experience for Windows developers who rely on PowerShell. The change is transparent: you just get the activated environment with no extra steps.

7. Are there any other settings I should know about for scanning nested virtual environments?

Yes. As mentioned in question 1, the default scanning pattern changed to avoid deep recursion. If your project uses virtual environments nested more than one level deep (for example, inside subdirectories of subdirectories), you’ll need to add custom paths using the python-envs.workspaceSearchPaths setting. This setting allows you to specify additional glob patterns to scan. For instance, you might add **/.venv if you deliberately place environments in deep folders. This gives you flexibility without forcing a heavy default scan on everyone. Check the extension’s settings page for more details.

Tags: