Python env activates automatically ignoring settings

[asmXI]

Type: Bug

Set these:

• "python.terminal.activateEnvironment": false,
• "python.terminal.activateEnvInCurrentTerminal": false,

and try to run some python app and stop it. Then try opening a new terminal window, python env is activated.

VS Code version: Code 1.103.1 (360a4e4fd251bfce169a4ddf857c7d25d1ad40da, 2025-08-12T16:25:40.542Z)
OS version: Windows_NT x64 10.0.26100
Modes:
Remote OS version: Linux x64 6.6.87.2-microsoft-standard-WSL2

System Info

Item	Value
CPUs	11th Gen Intel(R) Core(TM) i5-1145G7 @ 2.60GHz (8 x 1498)
GPU Status	2d_canvas: enabled direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off trees_in_viz: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	undefined
Memory (System)	15.73GB (2.22GB free)
Process Argv	--crash-reporter-id 8191be4b-ea1c-440f-894b-715054d2860b
Screen Reader	no
VM	0%

Item	Value
Remote	WSL: Ubuntu-24.04
OS	Linux x64 6.6.87.2-microsoft-standard-WSL2
CPUs	11th Gen Intel(R) Core(TM) i5-1145G7 @ 2.60GHz (8 x 0)
Memory (System)	7.62GB (3.49GB free)
VM	0%

Extensions (54)

Extension	Author (truncated)	Version
river	aid	0.0.3
vscode-azurevirtualmachines	ms-	0.6.9
jupyter-keymap	ms-	1.1.2
remote-ssh	ms-	0.120.0
remote-ssh-edit	ms-	0.87.0
remote-wsl	ms-	0.99.0
remote-explorer	ms-	0.5.0
proto	pet	0.0.4
claude-code	Ant	1.0.83
ty	ast	2025.35.12261122
ruff	cha	2025.24.0
gitignore	cod	0.10.0
vscode-markdownlint	Dav	0.60.0
githistory	don	0.6.20
prettier-vscode	esb	11.0.0
shell-format	fox	7.2.8
copilot	Git	1.350.0
copilot-chat	Git	0.30.1
vscode-github-actions	git	0.27.2
vscode-pull-request-github	Git	0.116.1
terraform	has	2.34.5
git-graph	mhu	1.30.0
microsoft-testing	ms-	0.1.17
azure-dev	ms-	0.9.0
vscode-azure-github-copilot	ms-	1.0.84
vscode-azure-mcp-server	ms-	0.5.6
vscode-azureappservice	ms-	0.26.3
vscode-azurecontainerapps	ms-	0.9.0
vscode-azurefunctions	ms-	1.18.1
vscode-azureresourcegroups	ms-	0.11.1
vscode-azurestaticwebapps	ms-	0.13.1
vscode-azurestorage	ms-	0.16.5
vscode-azureterraform	ms-	0.6.0
vscode-azurevirtualmachines	ms-	0.6.9
vscode-containers	ms-	2.1.0
vscode-cosmosdb	ms-	0.27.1
vscode-docker	ms-	2.0.0
debugpy	ms-	2025.10.0
python	ms-	2025.12.0
vscode-pylance	ms-	2025.7.1
vscode-python-envs	ms-	1.2.0
datawrangler	ms-	1.22.0
jupyter	ms-	2025.7.0
jupyter-keymap	ms-	1.1.2
jupyter-renderers	ms-	1.3.0
vscode-jupyter-cell-tags	ms-	0.1.9
vscode-jupyter-slideshow	ms-	0.1.6
vscode-node-azure-pack	ms-	1.7.0
windows-ai-studio	ms-	0.18.3
code-spell-checker	str	4.0.47
even-better-toml	tam	0.21.2
vscode-ai-foundry	Tea	0.8.0
intellicode-api-usage-examples	Vis	0.2.9
vscodeintellicode	Vis	1.3.2

(1 theme extensions excluded)

A/B Experiments

vsliv368:30146709
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythoneinst12:31285622
996jf627:31283433
pythonrdcb7:31342333
usemplatestapi:31297334
747dc170:31275177
aj953862:31281341
9d2cg352:31346308
convertlamdaf:31368658
usemarketplace:31343026
nesew2to5:31336538
agentclaude:31350858
replacestringexc:31350595
nes-set-on:31351930
6abeh943:31336334
envsactivate1:31353494
0927b901:31350571
ji9b5146:31348712
45650338:31358607
0cj2b977:31352657
asdad-cf:31365767
retryenabled:31368124

[anthonykim1]

Are

"python.terminal.activateEnvironment": false,
"python.terminal.activateEnvInCurrentTerminal": false,

changed or handled with env extension? @eleanorjboyd

[eleanorjboyd]

will review- thank you!

[eleanorjboyd]

Hi! Still working on this but you should be able to set envs.terminal.autoActivationType: "off" which will solve your problem as that setting is respected by the envs extension. Sorry for the delay!

[eleanorjboyd]

Thanks for the report. I don’t think this issue is still current as we have made a lot of improvements

We now explicitly handle the activation settings more carefully, including the pre-existing terminal case that this issue described, and respect both the legacy Python settings and the envs extension setting.

If you still see automatic activation in a newly opened terminal on the latest builds with both of these set to false:

• "python.terminal.activateEnvironment": false
• "python.terminal.activateEnvInCurrentTerminal": false

please open a fresh issue with logs plus the exact setting scopes (user/workspace/workspace folder), since that would likely be a different regression from the original report. Thank you!!