Debugger, "Run Python File", etc. fails when launched into a new terminal

[estyrke]

When doing something that launches a command in a new terminal (e.g. pressing the debug button on a test as I was doing right now), the env activation command seems to block execution of the launch. I'm left with an interactive prompt and nothing happens:

source /Users/emil/[redacted]/.venv/bin/activate
 /usr/bin/env /Users/emil/[redacted]/.venv/bin/python /Users/emil/.vscode/extensions/ms-python.debugpy-2025.15.2025102001-darwin-arm64/bundled/libs/debugpy/adapter/../../debugpy/launcher 53878 -- /Users/emil/.vscode/extensions/ms-python.python-2025.17.2025101701-darwin-arm64/python_files/vscode_pytest/run_pytest_script.py -vv --rootdir=/Users/emil/[redacted] --capture=no 
~/C/[redacted] ❯❯❯  

I am using OS X, zsh (with prezto if that is relevant). Worth noting is also that the env doesn't get activated either, so basically the two commands seem to cancel each other in some way.

I tried changing python-envs.terminal.autoActivationType to shellStartup instead of command, but then the env doesn't get activated at all. It does however solve the issue at hand. If the command happens to launch into an existing terminal it also works fine.

[anthonykim1]

Can you try again with latest insiders and latest pre-release of Python env extension.

Also, do you have shell integration enabled?

Insiders build?

[anthonykim1]

Try not using prezto prompt, also hover over terminal tab to see shell integration is rich or something else.