Update an extension

Update an extension in Visual Studio Code — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
Install the updated version of the Python extension and apply it to my user profile only; do not…
Install the updated version of the Python extension and apply it to my user profile only; do not change workspace extensions. After update, run the debugger quickly to confirm breakpoints still bind in my Flask app and report back if any debugger settings changed.

Improve — make it easier to accept

+
Before updating the Python extension, summarize breaking changes since the current version: list…
Before updating the Python extension, summarize breaking changes since the current version: list new features, removed features, and settings that were renamed. Highlight any changes that affect debugging, the language server, or virtual environment discovery. Suggest any pre-update steps I should take in this repo, like freezing the language server version in settings or backing up launch configurations.

Decide — diagnose the stuck moment

+
The Python extension prompted to update and asked me to restart; I postponed and now my debugger no…

The extension update offered a restart and I postponed; now debugging fails

The Python extension prompted to update and asked me to restart; I postponed and now my debugger no longer attaches to the Flask process. I’m worried the extension partially updated or cached old state. What diagnostic steps should I run to confirm the extension version and reload it safely, and which quick settings to check that usually break debugger attachment after an update?

Become — change the pattern

+
I repeatedly update language and tooling extensions and then spend hours chasing subtle regressions…

I update extensions ad hoc and then hunt regressions

I repeatedly update language and tooling extensions and then spend hours chasing subtle regressions in debug or linting. Recommend a lightweight update discipline for a small dev team: how often to update, which updates to pin, what quick smoke tests to run post-update, and a rollback plan that costs minimal developer time.

Next to this one

Other code editor work people do in Visual Studio Code.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.