bug: terminal triggered package refresh to use correct env#1175
Merged
eleanorjboyd merged 1 commit intomicrosoft:mainfrom Feb 4, 2026
Merged
bug: terminal triggered package refresh to use correct env#1175eleanorjboyd merged 1 commit intomicrosoft:mainfrom
eleanorjboyd merged 1 commit intomicrosoft:mainfrom
Conversation
TylerLeonhardt
approved these changes
Feb 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fixes #653
Automatic Package Refresh from Terminal
When you install, uninstall, or modify packages directly in the terminal using commands like pip install, conda install, poetry add, or pipenv install, the extension automatically detects these changes and refreshes your package list. The extension monitors terminal commands and recognizes package-modifying operations across all common Python package managers—including pip, uv, conda, mamba, poetry, and pipenv.
To ensure the correct environment is updated, the extension uses the environment that's actually activated in that specific terminal, not simply the workspace's selected environment. This means if you activate a different virtual environment in a terminal and run pip install requests, the package list refreshes for that activated environment rather than your project's default. If no environment is explicitly activated in the terminal, the extension falls back to matching the environment based on the terminal's working directory and workspace context.
This automatic refresh keeps your package views in sync without requiring manual intervention, ensuring that the Environment details panel and other package-related features always reflect your latest changes.