Introduction
The Python Environments extension for Visual Studio Code has received a significant update as of April 2026, bringing a host of improvements focused on startup speed, reliability, and user experience. This release addresses common pain points such as slow activation in remote workspaces, crashes, and inefficient package management. Below, we break down the key changes.
Faster Startup
One of the most noticeable enhancements is the dramatic reduction in startup time, particularly for users working in remote or containerized environments. Three core optimizations drive this improvement:
Lazy Manager Discovery
Previously, the extension eagerly discovered environments managed by pipenv, pyenv, and poetry on startup, even for users who never used them. Now, detection is deferred until you actually interact with those managers—for example, by opening a project containing a Pipfile or pyproject.toml with a poetry backend. This eliminates unnecessary overhead for the majority who rely on venv, uv, or conda (see issues #1423, #1408).
Faster Environment Resolution
The path from extension activation to interpreter readiness has been shortened. Both startup resolution and interpreter selection now complete with lower overhead (#1419).
Narrower Default Workspace Scanning
The default search pattern for virtual environments has been refined. Previously, ./**/.venv triggered a recursive scan of the entire workspace tree, causing the Python Environment Tools (PET) process to hang for 30+ seconds on large projects—especially over Remote-SSH—leading to cascading timeouts and restart loops (see #1460, #1434). The new default is .venv and */.venv, covering standard layouts without deep traversal. Users with environments nested deeper than one level can customize via the python-envs.workspaceSearchPaths setting (#1419).
Improved Reliability
Several fixes address long-standing reliability issues, ensuring the extension remains stable even when underlying processes falter.
PET Crash Recovery
When the PET process crashed mid-refresh, the extension could become stuck with no environments visible. Now, the extension automatically retries the refresh after a crash and handles empty or malformed responses defensively. A transient PET failure no longer leaves you with a blank environment list (#1442, #1447, #1444).
Conda Base Environment Fix
After a window reload, the conda base environment was sometimes incorrectly restored as a different named environment, making it appear that your interpreter selection had silently changed. This issue has been resolved (#1412).
Environment Updates and Terminals
Quality-of-life improvements for package management and terminal usage round out this release.
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 (#1420).
Multi-Project Terminal Creation
In workspaces containing multiple Python projects, creating a new terminal now prompts you to choose which project’s environment to activate, rather than silently picking one (#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 correctly.
Conclusion
This April 2026 update significantly boosts the performance, reliability, and usability of the Python Environments extension for VS Code. Whether you’re working locally, remotely, or in containers, the improvements—from faster startup to smarter terminal handling—make your Python development experience smoother. For more details, check the linked issues in the original release notes.