When we do, code doesn't pick up the activated virtualenv. This feature is supported, but there is an early exit check which documents an assumption that CLI launches and workspace files are not used ...

When I start my vscode it checks for virtual environments and detects them (according to the logs). However when I want to switch interpreter it will only show the list of globally installed python ...