Terminal Venv auto activation not working

[cmplsn]

Type: Bug

Behaviour

I'm creating the venv externally from vscode (python -m venv .venv), as i did multiple times on another macbook i no longer have, and when opening the project folder (containing .venv) through vscode i used to set >Python: Select Interpreter to the one inside .venv and when creating new terminals it would automatically activate the virtual environment without the need to activate it in every new terminal. this no longer works and if i don't explicitly activate the venv in vscode integrated terminal it refere the .pyenv installations rather then the local .venv ones.

The Settings to activate Env through terminal for the Python extensions are turned on.

The global python pip installations are made through pyenv.

Extension version: 2025.10.0
VS Code version: Code 1.102.0 (cb0c47c0cfaad0757385834bd89d410c78a856c0, 2025-07-09T22:10:34.600Z)
OS version: Darwin arm64 24.6.0
Modes:

• Python version (& distribution if applicable, e.g. Anaconda): 3.10.18
• Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Venv
• Value of the python.languageServer setting: Default

User Settings

languageServer: "Pylance"

Installed Extensions

Extension Name	Extension Id	Version
debugpy	ms-	2025.10.0
js-debug	ms-	1.102.0
js-debug-companion	ms-	1.1.3
jupyter	ms-	2025.6.0
jupyter-keymap	ms-	1.1.2
jupyter-renderers	ms-	1.3.0
python	ms-	2025.10.0
vscode-js-profile-table	ms-	1.0.10
vscode-jupyter-cell-tags	ms-	0.1.9
vscode-jupyter-slideshow	ms-	0.1.6
vscode-pylance	ms-	2025.6.2

System Info

Item	Value
CPUs	Apple M1 (8 x 2400)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on 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: enabled_on video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	10, 5, 4
Memory (System)	8.00GB (0.11GB free)
Process Argv	--crash-reporter-id 7a2f682b-cb7e-41df-8f29-c980af9f52a3
Screen Reader	no
VM	0%

A/B Experiments

vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
binariesv615:30325510
962ge761:30959799
h48ei257:31000450
nativeloc1:31344060
5fd0e150:31155592
dwcopilot:31170013
6074i472:31201624
dwoutputs:31242946
9064b325:31222308
copilot_t_ci:31333650
e5gg6876:31282496
pythoneinst12:31285622
c7cif404:31314491
pythonpulldiag:31343502
996jf627:31283433
pythonrdcb7:31342333
usemplatestapi:31297334
0aa6g176:31307128
747dc170:31275177
aj953862:31281341
generatesymbolt:31295002
convertfstringf:31295003
9d2cg352:31346308
usemarketplace:31343026
nesew2to5:31336538
agentclaude:31335815
nes-diff-11:31337487
6abeh943:31336334
yijiwantestdri0626-t:31336930
ji9b5146:31342393

[eleanorjboyd]

do you think it is the same as this: #25284

[anthonykim1]

Before when it was all working fine, did you see the activate command show up in your terminal?

[A00474880]

For me the failed command shows up:

$ conda activate cenv

EnvironmentNameNotFound: Could not find conda environment: cenv
You can list all discoverable environments with `conda info --envs`.

For me cenv is a local environment created with conda create --prefix. And manually activating the environment with conda activate ./cenv works fine.

Seems like something related to environment pathing broke in the last update.

[eleanorjboyd]

I think you are likely running into this if you can see my comment there for solutions to fix it: #25284

[A00474880]

I think you are likely running into this if you can see my comment there for solutions to fix it: #25284

Thank you, installing Python Environment worked for me. Following instructions from :#25291

How are insiders picked? I didn't know I was an insider

[eleanorjboyd]

insiders is a VS Code version that ships daily, anyone can install it if you want the very latest! https://code.visualstudio.com/insiders/

[cmplsn]

do you think it is the same as this: #25284

Yes it most likely is the same problem.

• correct interpreter from my virtual environment is used correctly to launch jupyter kernel,
• correct interpreter from venv is used to run python cells and .py files
• the integrated vscode terminal instead needs manual activation although (.venv) is already displayed at the beginning of each command line.

Actions i performed

• Tried to uninstall and reinstall pyenv -> didn't work
• Uninstalled and reinstalled VSCode even rolling back to previous versions -> didn't workd

[cmplsn]

I think you are likely running into this if you can see my comment there for solutions to fix it: #25284

Thank you, installing Python Environment worked for me. Following instructions from :#25291

How are insiders picked? I didn't know I was an insider

Even without installing VSCode Insiders following instructions from [#25291] solved it for me too.
thank you!

[A00474880]

I didn't install the insider version of vscode either. Does this mean something else might be broken here for the stable version? I'm adding more information in case this needs to be re-opened

$ code --version
1.102.1
7adae6a56e34cb64d08899664b814cf620465925
x64

I'm using it for remote development on ubuntu 24.04:

Operating System: Ubuntu 24.04.2 LTS                       
Kernel: Linux 6.8.0-1025-gcp
Architecture: x86-64

$ bash --version
GNU bash, version 5.2.21(1)-release (x86_64-pc-linux-gnu)