Repository navigation
Activating environment takes a few seconds #26065
Description
Type: Bug
Behaviour
Activating a venv when opening a terminal takes 3-4 seconds. Previously, it used to be pretty much instantaneous. Even worse, while the env is being activated, I can already run commands, which eventually will error because they require the activated env.
Steps to reproduce:
- Open the integrated terminal
- Observe the "Activating venv" message in the toolbar
- This takes a few seconds
- After that, the venv is finally activated
Extension version: 2026.5.2026070801
VS Code version: Code 1.130.0 (Universal) (1b6a188127eeaf9194f945eb6eb89a657e93c54c, 2026-07-22T14:55:04Z)
OS version: Darwin arm64 25.5.0
Modes:
- Python version (& distribution if applicable, e.g. Anaconda): 3.14.5
- Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Venv
- Value of the
python.languageServersetting: None
User Settings
languageServer: "None"
testing
• pytestArgs: "<placeholder>"
• pytestEnabled: true
Installed Extensions
| Extension Name | Extension Id | Version |
|---|---|---|
| air-vscode | Pos | 0.28.0 |
| claude-code | Ant | 2.1.220 |
| code-spell-checker | str | 4.5.6 |
| code-spell-checker-german | str | 2.3.4 |
| copilot-chat | Git | 0.58.0 |
| debugpy | ms- | 2026.7.12081007 |
| js-debug | ms- | 1.117.0 |
| js-debug-companion | ms- | 1.1.3 |
| jsts-chat-features | Typ | 0.0.4 |
| jupyter | ms- | 2025.9.1 |
| python | ms- | 2026.5.2026070801 |
| quarto | qua | 1.135.0 |
| rainbow-csv | mec | 3.24.1 |
| rewrap-revived | dnu | 1.16.3 |
| ruff | cha | 2026.66.0 |
| ty | ast | 2026.64.0 |
| vscode-js-profile-table | ms- | 1.0.10 |
| vscode-pull-request-github | Git | 0.160.0 |
| vscode-python-envs | ms- | 1.36.0 |
| vscode-yaml | red | 1.24.0 |
System Info
| Item | Value |
|---|---|
| CPUs | Apple M2 Pro (12 x 2400) |
| GPU Status | 2d_canvas: enabled GPU0: VENDOR= 0x106b [Google Inc. (Apple)], DEVICE=0x0000 [ANGLE (Apple, ANGLE Metal Renderer: Apple M2 Pro, Version 26.5.2 (Build 25F84))], DRIVER_VENDOR=Apple, DRIVER_VERSION=26.5.2 ACTIVE Machine model name: Mac Machine model version: 14.9 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 trees_in_viz: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgpu: enabled webnn: disabled_off |
| Load (avg) | 2, 2, 2 |
| Memory (System) | 32.00GB (0.09GB free) |
| Process Argv | |
| Screen Reader | no |
| VM | 0% |
Activity
[-]Activating environment suddenly take 3-4 seconds[/-][+]Activating environment suddenly takes 3-4 seconds[/+][-]Activating environment suddenly takes 3-4 seconds[/-][+]Activating environment suddenly takes a few seconds[/+][-]Activating environment suddenly takes a few seconds[/-][+]Activating environment takes a few seconds[/+]cbrnr commentedon Jul 30, 2026
This issue also prevents users from properly running a Python script via the "Run Python File" toolbar button. When no previous terminal exists, the script starts before the environment is activated, so it uses the global Python environment instead of the virtual environment (typically resulting in errors). So I would say this is a pretty serious issue...
cbrnr commentedon Jul 31, 2026
Could this be related to some newly introduced VS Code setting? It seems like the environment gets activated only after the message disappears after a few seconds:
Setting
"terminal.integrated.initialHint": falseremoves the message, but not the delay!cbrnr commentedon Sep 23, 2026
I tried to replicate this issue with 1.138.0, and it seems it was fixed at some point.