I use these extensions to manage my interactions with poetry
- ameenahsanma.poetry-monorepo
- zeshuaro.vscode-python-poetry
- teticio.python-envy
After updating VS Code to the below, I no longer spawn new terminals with my poetry interpreter activated, nor is it available to select as the default interpreter.
Version: 1.103.0 (Universal)
Commit: e3550cfac4b63ca4eafca7b601f0d2885817fd1f
Date: 2025-08-06T21:40:10.271Z
Electron: 37.2.3
ElectronBuildId: 12035395
Chromium: 138.0.7204.100
Node.js: 22.17.0
V8: 13.8.500258-electron.0
OS: Darwin arm64 24.0.0
I have a workaround for setting this based on other comments. Main drawback is that terminals still need to be activated using eval $(poetry env activate).
"python.useEnvironmentsExtension": true,
"python.defaultInterpreterPath": "/Users/ntindle/Library/Caches/pypoetry/virtualenvs/<poetryenv>/bin/python3.12"
Poetry Details
❯ poetry env activate
source /Users/ntindle/Library/Caches/pypoetry/virtualenvs/autogpt-platform-backend-LOXRIHzA-py3.12/bin/activate
❯ poetry --version
Poetry (version 2.1.2)
❯ eval $(poetry env activate)
Hope this helps
I use these extensions to manage my interactions with poetry
After updating VS Code to the below, I no longer spawn new terminals with my poetry interpreter activated, nor is it available to select as the default interpreter.
I have a workaround for setting this based on other comments. Main drawback is that terminals still need to be activated using
eval $(poetry env activate).Poetry Details
Hope this helps