Record or run a macro

Record or run a macro in Visual Studio Code — with three ready prompts, from the immediate task to the lasting pattern.

3prompt heights
Open it in the interactive atlas →

3 ready prompts

Written for the moment this actually comes up.

Improve — make it easier to accept

+
Before I record this macro for the team, make it forgiving: surface any editor settings the macro…
Before I record this macro for the team, make it forgiving: surface any editor settings the macro relies on, ensure the snippet paste respects tab size and uses spaces, and flag commands that assume a saved file or a specific language mode. Highlight where the macro could break on Windows vs macOS or when files are unsaved, and suggest two small edits so reviewers can approve it quickly.

Decide — diagnose the stuck moment

+
I started recording a macro to insert a header, save, and run analysis.py. The recorder saved…

I just tried to record keystrokes but the macro didn't run on save.

I started recording a macro to insert a header, save, and run analysis.py. The recorder saved keystrokes, but when I trigger MacroRunSnippet nothing happens. I suspect it's a matter of where the macro file was written or a missing permission for running the terminal command. I can't tell whether the activation keybinding collided with another extension or the macro failed to save. What is the most likely cause and the simplest steps to get it working for my user on Windows 10?

Become — change the pattern

+
Over the last three months I keep making near-identical macros for formatting, header insertion,…

I keep rewriting the same small macros for different projects.

Over the last three months I keep making near-identical macros for formatting, header insertion, and running tests. They eat time and confuse teammates when they land in different places. I want one reliable habit to stop duplicating effort and make macros shareable across projects. What change should I adopt first so macros are reusable, documented, and easy for the team to accept?

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.