Please make `python-envs.terminal.autoActivationType` syncable to all remotes

Evaluación

Este issue todavía no se ha evaluado.

Descripción

The canonical fix for VSCode killing any running process to activate a Python environment after opening a terminal is to set autoActivationType to a non-default value.

The problem is that, at least on my machine, this is per-remote. Below screenshots are on an AWS EC2 instance:

This means that every time I start an instance or a new dev container, the first command I run in every terminal is killed until I got change that setting again.

Given that killing running processes indiscriminately is disruptive, I think it would be good to make it possible for a user to change this behavior for good. Otherwise, the only option is "python.terminal.activateEnvironment": false, which isn't ideal either.

Maybe there could be a defaultAutoActivationType setting that syncs, so the user can choose the syncing version or the other at will? Alternatively, setting the default to shellStartup might be less surprising and less likely to cause problems.

A good reason to care about this is that this can cost the user money. In my case, it killed an OpenCode session that had been running for hours, which I discovered too late, leading to a cache miss on the whole conversation when I started it again.

Guía de contribución

Abrir la guía de contribución

Primeros pasos

1. Lee el issue completo y luego la guía de contribución del proyecto.
2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
3. Haz un fork del repositorio y trabaja en una rama.
4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/vscode-python-environments

• API package validation fails due to ambient type definitions in parent directories Abierto

  microsoft/vscode-python-environments#1799 · 1 asignado · Abierto el 19/9/2026

• "python.defaultInterpreterPath" ignored and overwritten by automated user setting Abierto

  microsoft/vscode-python-environments#1796 · 1 asignado · Abierto el 17/9/2026

• Python Environments causes invalid "Python 3.14.undefined" kernels and Jupyter hangs on "Connecting to kernel" Abierto

  Dificultad 4/5 3-5 días Aptitud para principiantes 48/100

  microsoft/vscode-python-environments#1795 · Abierto el 17/9/2026

• Update dependencies with actionable security alerts Abierto
  triage-needed

  microsoft/vscode-python-environments#1791 · 1 reacción · 2 asignados · Abierto el 16/9/2026

• Poetry package listing fails for nested/non-root pyproject.toml projects (`poetry show` runs with wrong cwd) Abierto
  triage-needed

  Dificultad 4/5 3-5 días Aptitud para principiantes 74/100

  microsoft/vscode-python-environments#1779 · 1 comentario · 1 reacción · Abierto el 11/9/2026

Todos los issues de microsoft/vscode-python-environments

Issues similares

• Required field with a schema default (ajv useDefaults) can permanently block submission Abierto
  Type/Bug

  Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100

  OpenNSW/nsw-srilanka#497 · Abierto el 21/9/2026

• portal pins drifted from wallet main Abierto

  Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100

  0xMiden/bridge-portal#132 · Abierto el 21/9/2026

• [react-doctor] js-length-check-first · src/screens/MapScreen/BoundsEditor.tsx:59 Abierto
  react-doctor severity:warning tech-debt

  Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100

  digidem/comapeo-cloud-app#403 · Abierto el 21/9/2026

• An expired login is reported to Sentry as an error Abierto

  Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100

  ARTPARK-SAHAI-ORG/calibrate-frontend#634 · Abierto el 21/9/2026

• Cloudflare scaffold recommends the keyless cloudflare/... model but never declares the AI binding it requires Abierto

  Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100

  withastro/flue#739 · Abierto el 21/9/2026

Más issues de TypeScript