The Python Environments extension for Visual Studio Code has received a significant update in April 2026, focusing on startup performance, reliability, and quality-of-life improvements for terminals and package management. This release addresses common pain points for developers working with remote environments, large projects, and multiple Python versions. Here are the key highlights.
Faster Startup Performance
The extension now activates noticeably faster, especially in remote and containerized workspaces. Three major changes contribute to this speed gain.
Lazy Manager Discovery
Previously, Pipenv, pyenv, and Poetry environments were eagerly discovered on startup. Now, detection is deferred until you interact with these tools — for example, opening a project that uses a Pipfile or pyproject.toml with a Poetry backend. This eliminates unnecessary work for the majority of users relying on venv, uv, or Conda. (Refer to issues #1423 and #1408 for technical details.)
Faster Environment Resolution
The path from extension activation to interpreter readiness is now shorter. Resolution during startup and interpreter selection completes with less overhead, making the overall experience smoother. (Issue #1419)
Narrower Default Workspace Scanning
The default search pattern for virtual environments was ./**/.venv, which triggered a recursive scan of the entire workspace tree. On large projects and especially over Remote-SSH, this could cause the Python Environment Tools (PET) process to hang for 30+ seconds during configuration, leading to cascading timeouts and restart loops. The default pattern is now .venv and */.venv, covering standard layouts without deep traversal. If you have virtual environments nested deeper, add custom paths via the python-envs.workspaceSearchPaths setting. (Issues #1460, #1434, and #1419)
Improved Reliability
Stability has been a key focus, with two notable fixes that prevent the extension from entering broken states.
PET Crash Recovery
When the PET process crashed mid-refresh, the extension could end up with no environments visible. Now, the extension retries a refresh after a crash and handles empty or malformed responses defensively. A transient PET failure no longer leaves you with a blank environment list. (Issues #1442, #1447, #1444)
Conda Base Environment Fix
After a window reload, the Conda base environment could be incorrectly restored as a different named environment, making it appear that your interpreter selection silently changed. This bug has been fixed. (Issue #1412)
Enhanced Terminal and Package Management
Several quality-of-life improvements streamline daily workflows.
Auto-Refreshing Package Lists
You no longer need to manually refresh the package view after running pip install or pip uninstall. The extension now watches for metadata changes in site-packages and updates the package list automatically. (Issue #1420)
Multi-Project Terminal Creation
In workspaces with multiple Python projects, creating a new terminal now prompts you to choose which project’s environment to activate, rather than silently picking one. (Issue #1401)
PowerShell Activation on Windows
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 activation, ensuring .ps1 scripts work reliably. (Refer to issue details in the original update.)
These changes make the Python Environments extension more efficient, reliable, and user-friendly for day-to-day development. Update to the latest version via the VS Code marketplace or by checking for updates within the editor.