Python Environments VS Code Extension: April 2026 Update Q&A

Welcome to our Q&A breakdown of the April 2026 update for the Python Environments extension in Visual Studio Code. This release brings significant improvements to startup speed, reliability, and daily workflow in terminals and package management. Below, we answer the most common questions about these changes.

What are the major improvements in the April update?

The update focuses on three core areas: startup performance, reliability, and quality-of-life enhancements for terminals and package management. Key highlights include faster activation through lazy environment manager discovery, reduced workspace scanning scope, automatic retry after PET process crashes, and automatic package list refresh after install or uninstall operations. Multi-project terminal creation now prompts you to choose which environment to activate, and PowerShell activation on Windows no longer fails due to execution policy restrictions. These changes collectively make the extension more responsive and robust, especially on remote or containerized workspaces.

How has startup performance been improved?

The extension now starts noticeably faster, particularly in remote and containerized workspaces. Three key changes were made:

• Lazy manager discovery: Previously, Pipenv, pyenv, and poetry were detected eagerly at startup. Now, detection is deferred until you interact with one of those managers, such as opening a project with a Pipfile or pyproject.toml using poetry. This eliminates unnecessary scanning for the majority of users relying on venv, uv, or conda.
• Faster environment resolution: The path from extension activation to interpreter readiness is now shorter. Both startup resolution and interpreter selection complete with less overhead.
• Narrower default workspace scanning: The default search pattern changed from ./**/.venv (which could hang for 30+ seconds on large projects over Remote-SSH) to .venv and */.venv. This covers standard layouts without deep traversal. For deeper nesting, you can add custom paths via the python-envs.workspaceSearchPaths setting.

How does the extension handle PET process crashes?

When the Python Environment Tools (PET) process crashed mid-refresh, the extension could end up in a broken state with no environments visible. To fix this, the extension now automatically retries the refresh after a crash and defensively handles empty or malformed responses. As a result, a transient PET failure no longer leaves you with an empty environment list. This change is documented in issues #1442, #1447, and #1444, ensuring that even if PET crashes temporarily, the environment view returns to normal after retrying.

What fix was applied to the Conda base environment?

Previously, after a window reload, the Conda base environment could be incorrectly restored as a different named environment. This made it appear that your interpreter selection had silently changed, causing confusion. The April update resolves this issue (see #1412) so that the Conda base environment is now correctly identified and preserved after reloads. This reliability fix ensures that your chosen interpreter remains stable, especially users who rely on Conda environments.

How is terminal management improved?

Two significant improvements were made:

• Auto-refreshing package lists: You no longer need to manually refresh the package view after running pip install or pip uninstall. The extension watches for metadata changes in site-packages and updates the 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 picking one silently (#1401). This gives you explicit control over the activated environment.

What change was made to PowerShell activation on Windows?

Virtual environment activation via PowerShell could fail on Windows if the system execution policy blocked scripts. The extension now sets a process-scoped execution policy before running the activation script. This ensures that .ps1 activation scripts run smoothly, bypassing system-level restrictions without compromising security. This fix is especially beneficial for users who encounter the "execution policy" error when trying to activate a Python virtual environment in the VS Code terminal.