Repository navigation
VS Code issues relating to new terminal activation feature #22879
Description
This is to track outstanding VS Code bugs so terminal activation feature can stabilize:
-
.zshrcis overriding the environment variable set by shell integration on macOS vscode#205102 - Prepending using shell integration does not work for zsh, even when shell integration is activated vscode#205133
- Expose API whether shell integration is working or not vscode#205058
-
onDidExecuteTerminalCommanddoes not fire events for hidden terminal vscode#199611 - Environment collection should not be applied on hidden terminals (non-windows) vscode#197187
- Provide a way to exempt a terminal from applying any env collections vscode#194819
- This is not needed if #197187 is solved
- Resolve Provide a way to exempt a terminal from applying any env collections vscode#194819 (comment)
- Resolve Environment collection should not be applied on hidden terminals (non-windows) vscode#197187 (comment)
- Provide a way to exempt a terminal from applying any env collections vscode#194819
-
onDidWriteTerminalDataevent does not contain shell integration sequences for hidden terminals vscode#204616 - Prepending using shell integration does not work for fish when using starship prompt vscode#208465
- Ensure we use correct workspace folder for remote terminals vscode#180486
- Multiroot workspaces for remote scenarios does not work currently because of this
- Expose shell integration command knowledge to extensions vscode#145234
- Explore terminal buffer API vscode#207504
- We would need this to get command output, if microsoft/vscode#145234 doesn't cover it.
- Shell integration isn't enabled for Debug terminals vscode#204694
- Shell integration isn't enabled for Task terminals vscode#205177
- Environment collection replace API strips equals sign at the end vscode#197603
Our follow up action items based on that:
- Adopt to using VS Code API to access terminal output #22128
- If automatic shell integration is failing to activate environment, recommend users to do manual installation #23113
- Enable experiment for multiroot remote scenarios:
vscode-python/src/client/common/experiments/helpers.ts
Lines 12 to 17 in 0438813
Issue to keep in mind:
PREPEND: #21906
Activity
KayvanShah1 commentedon Feb 8, 2024
karrtikr commentedon Feb 8, 2024
JoelFeiner-viimed commentedon Feb 8, 2024
gabethehuman commentedon Feb 8, 2024
karrtikr commentedon Feb 8, 2024
karrtikr commentedon Mar 26, 2024
notes.md
valhuber commentedon Jul 15, 2025
Critical Regression - VS Code Python Extension Breaking Both Terminal AND Application Execution
This issue represents a critical regression that has broken core Python development functionality. The VS Code Python extension changes have broken both terminal virtual environment activation AND Python application execution.
Background & Fundamental Goal
One of the fundamental goals of modern Python development tooling is to solve the default virtual environment issue for new users. New Python developers are often confused by virtual environments, and tooling should "just work" when a project specifies a virtual environment.
This is why we implemented computed default virtual environments in our ApiLogicServer project generator - to automatically configure the correct virtual environment for users so they don't have to manually figure out activation, paths, and environment management.
The Problem
With VS Code 1.102.0 and recent Python extension versions,
python.defaultInterpreterPathcorrectly sets the interpreter in the UI, but fails to:(venv)prompt, wrong Python path)Impact on Project Generators & New User Experience
This particularly affects project generators that create workspaces with shared virtual environments to solve the "default venv for new users" problem. Our ApiLogicServer project generator creates projects with:
/Users/val/dev/ApiLogicServer/ApiLogicServer-dev/build_and_test/ApiLogicServer/venv"python.defaultInterpreterPath": "/Users/val/dev/ApiLogicServer/ApiLogicServer-dev/build_and_test/ApiLogicServer/venv/bin/python"The goal: New users run
ApiLogicServer createand get a project that "just works" with the correct virtual environment activated automatically.The reality: Users now get broken projects where nothing works as expected, defeating the entire purpose of computed default virtual environments.
What's Broken
python.terminal.activateEnvironment: trueRequired Workarounds
We've had to implement extensive workarounds in our project generator, adding complexity that defeats the "simple for new users" goal:
{ "python.defaultInterpreterPath": "ApiLogicServerPython", "python.terminal.activateEnvironment": true, "python.terminal.activateEnvInCurrentTerminal": true, "python.envFile": "${workspaceFolder}/.env", "terminal.integrated.profiles.osx": { "venv": { "path": "/bin/zsh", "args": ["-c", "source ${workspaceFolder}/.vscode/venv_init.sh && exec zsh"] } }, "terminal.integrated.defaultProfile.osx": "venv" }eleanorjboyd commentedon Dec 8, 2025
Anthony Kim (@anthonykim1) should this be closed as it is related to the old activation stuff?
valhuber commentedon Dec 8, 2025
Eleanor Boyd (@eleanorjboyd) Anthony Kim (@anthonykim1)
I am not an internals person, so I do not understand "old/new activation stuff", but I am happy to jump on a call to explain my needs, and explore alternatives.
anthonykim1 commentedon Dec 27, 2025
yeap, closing against: microsoft/vscode-python-environments#962