VS Code Python Environments Extension: April 2026 Update - Faster, More Reliable, and Smarter

Welcome to the April 2026 update of the Python Environments extension for Visual Studio Code. This release delivers a faster startup, stronger reliability, and thoughtful quality-of-life improvements for terminals and package management. Below, we answer your top questions about what's new and how it improves your daily workflow.

What makes startup faster in this update?

We've trimmed startup time with three key changes. First, lazy manager discovery defers detection of pipenv, pyenv, and poetry environments until you actually interact with one—like opening a Pipfile or pyproject.toml. This eliminates unnecessary work for most users who rely on venv, uv, or conda. Second, faster environment resolution shortens the path from extension activation to interpreter readiness. Third, the default workspace scan pattern changed from ./**/.venv to .venv and */.venv. This avoids deep recursive traversal that could hang the PET process on large projects, especially over Remote-SSH. If your virtual environments are nested deeper, simply configure custom paths via the python-envs.workspaceSearchPaths setting.

How has reliability been improved?

Two major fixes boost stability. The extension now includes PET crash recovery: if the Python Environment Tools process crashes mid-refresh, the extension retries the refresh and handles empty or malformed responses gracefully. A transient failure no longer leaves you with a blank environment list. Additionally, the conda base environment bug is resolved. After a window reload, the conda base environment could mistakenly appear as a different named environment, silently changing your interpreter selection. That confusion is now eliminated.

Do I still need to manually refresh package lists?

No! The extension now auto-refreshes package lists after you run pip install or pip uninstall. It watches for metadata changes in site-packages and updates the package view automatically. This saves you a manual refresh step and keeps your environment view in sync with actual installed packages—no more wondering if the list is current.

What's new for terminals in multi-project workspaces?

When you create a new terminal in a workspace with multiple Python projects, the extension now prompts you to choose which project's environment to activate. Previously, it silently picked one, which could be confusing. This interactive prompt ensures you always activate the right environment for the project you're working on—no more accidental package installations in the wrong context.

How is PowerShell activation on Windows improved?

Virtual environment activation via PowerShell could fail if the system execution policy blocked scripts. The extension now sets a process-scoped execution policy before running the activation script. This bypasses the restrictive policy (like Restricted or AllSigned) that might prevent .ps1 scripts from running. The result: a seamless activation experience without requiring you to change your system-wide policy.

What was the conda base environment fix?

After a window reload in VS Code, the conda base environment was sometimes incorrectly restored as a different named environment. That made it appear that your interpreter selection had silently changed. This issue is now fixed. The extension correctly restores the base environment and your intended interpreter selection remains intact after reloads.

What are the overall benefits of this update?

This release focuses on three areas: faster startup through lazy detection and smarter scanning, enhanced reliability with PET crash recovery and conda base fix, and terminal & package quality-of-life—auto-refreshing packages, multi-project terminal prompts, and PowerShell activation fix. Together, these improvements make the Python Environments extension more responsive and trustworthy, especially for large projects, remote workspaces, and users with complex environment setups.