Stack Builder
Every project opens with exactly the extensions it needs, and nothing else.
Stack Builder scans a folder, finds every project inside it and what each one is built with, and gives
each project its own extension set. When you open a project through Stack Builder, only that set
(plus a few you always want) is switched on, just for that window. Close it and nothing has changed.
No profiles to juggle, no extensions to disable by hand, no fifty extensions loading for a single Python script.
Getting started
- Open a folder and click the Stack Builder icon in the Activity Bar, then Scan this folder.
- Check what it found, include or skip extensions, then create a workspace for the whole project or for single folders.
- From then on:
- Stack Launcher loads any of those workspaces' extensions and settings into the window you're in.
- Open Projects opens one project, or several together, in a window.
- Ctrl+Alt+R (Cmd+Alt+R on Mac) opens a recent project with its own extensions.
Everything is also in the Command Palette under Stack Builder:, so you never need to remember a shortcut.
Features
Scan a project
Stack Builder: Scan Project (also on the Explorer right-click menu for any folder).
- Finds every sub-project and shows it as a folder in the sidebar, with a signal meter for how strongly it was detected.
- Shows the files that gave each stack away, like
next.config.ts, FaceCenterTester.csproj or pubspec.yaml.
- Lets you add any subfolder as its own folder, or remove one you don't want.
- Lists the extensions each project needs, laid out like the Extensions view. Include puts an extension
in the project's set (and installs it if it's missing); Skip leaves it out.
- Find more opens the Extensions view already searching for that stack. Install one from there and
Stack Builder offers to add it to that folder.
- Add extension… adds any extension to a folder by hand: pick from what's installed, or type a Marketplace ID.
Hand-added extensions are remembered for the project and can be removed with ×.
Workspaces: whole project, or one folder
- Create root workspace writes one
.code-workspace for the whole project, with a folder per sub-project.
- Create workspace for this folder writes one inside a single folder, so it can be opened on its own.
- Open alone opens just that folder, lean.
Each workspace comes with build folders (node_modules, bin/obj, .venv, .next and more) kept out of
search and file watching, per-project settings (Python interpreter, C# solution), and debug configurations
including a Run everything compound. Existing files you wrote yourself are never overwritten.
Stack Launcher
Stack Builder: Open Stack Launcher, or click the status bar item.
- Lists the workspaces in the folder you have open. Tick one or more to load their extensions and
settings into this window, on top of your own folders.
- Shows what will be on: Always on, From ticked workspaces, From presets, and
Everything else installed. Flip any switch for this session.
- Apply to this window reopens the same window with that set. VS Code can't switch extensions in a
window that's already running, so it closes and reopens (about two seconds, after asking about unsaved files).
- Turn everything back on returns the window to how it was, with every extension on.
- Save to workspace makes your current choice that workspace's own extension set.
Open Projects: one or several in a window
Stack Builder: Open Projects…
- Lists your recent projects plus the workspaces in this folder. Add any other folder or workspace file with +.
- Tick one to open it with only its extensions, or tick several to open them together in one window
with all their folders, settings and extensions combined.
- Open with everything opens normally instead.
Presets
Quick-fill extension lists for your machine, like Web, Android or Hardware. In the Launcher, add a
preset to switch its extensions on, untick what you don't need, and save.
- Create: Save current set as preset… in the Launcher (as a new preset, or replacing one), or the + on
Presets in the Stack Builder view.
- Edit, rename, delete: hover a preset in the Launcher or the Stack Builder view, right-click it, or use
Stack Builder: Manage Presets…. Editing is a tick list of your installed extensions, plus any ID you type.
Dev, Android and Hardware are built in. Delete or change them like any other preset.
Always-on extensions
Pin an extension in the Launcher, or tick it in Stack Builder: Edit Always-On Extensions…, to keep it on in
every window: your theme, your AI assistant, your formatter. Saving a set (to a workspace or as a preset)
includes the always-on extensions that are on, so the set still works if you unpin one later.
Recent projects (Ctrl+Alt+R)
Stack Builder: Open Recent Project… shows your recently opened projects (the × removes one). Projects with an extension
set open lean; others open normally. The button on each row opens it with everything on instead.
Opening a project the normal way
If you open a project through File → Open or the editor's own recent list, every extension loads.
Stack Builder notices and offers to reopen it lean, once or always. The status bar shows whether
the window is lean or has everything on.
Commands
| Command |
What it does |
| Scan Project |
Scan the open folder (or the right-clicked folder in the Explorer) |
| Open Stack Launcher |
Tick workspaces to apply their extensions and settings to this window |
| Open Projects… |
Open one project, or several together in one window |
| Open Recent Project… |
Recent projects, opened with their extensions (Ctrl+Alt+R) |
| Open This Project Lean |
Open the current folder's project with only its extensions |
| Reopen This Window Lean |
Reopen this project window with only its extensions |
| Manage Presets… |
Create, edit, rename and delete presets |
| New / Edit / Rename / Delete Preset… |
The same, one action at a time |
| Edit Always-On Extensions… |
Tick the extensions kept on everywhere |
| Manage Remembered Choices… |
Undo "Always do this", "Don't ask for this folder" and removed recent projects |
| Show Log |
Open the Stack Builder log |
Settings
| Setting |
Description |
stackBuilder.alwaysOn |
Extensions kept on in every window Stack Builder opens |
stackBuilder.presets |
Your preset extension lists, e.g. { "Web": ["dbaeumer.vscode-eslint"] } |
stackBuilder.onOpenStack |
When a project opens with everything on: ask (default), always reopen lean, or never |
stackBuilder.catalogPath |
Path to your own stack catalog. Leave empty for the built-in one |
stackBuilder.scan.maxDepth |
How many folders deep a scan looks. 0 = no limit. Also set from the Scan panel |
stackBuilder.scan.maxFiles |
Most project files a scan collects before stopping (default 50,000) |
stackBuilder.scan.useIgnoreFiles |
Skip folders listed in the project's .gitignore (any depth), .ignore and .rgignore. On by default |
stackBuilder.scan.exclude |
Extra folder names to skip, e.g. ["vendor"] |
Supported stacks
Web: Next.js, React, Vue, Nuxt, Angular, Svelte, Astro, Remix, Gatsby, Vite, Tailwind, TypeScript, Express, NestJS, Deno, Bun, Electron, Tauri, Ionic / Capacitor, Storybook, Playwright, Vitest, Prisma, GraphQL
Backend: Python, Django, FastAPI, Flask, Streamlit, PyTorch / ML, Conda, Go, Rust, C# / F# / VB / .NET, PHP, Laravel, Ruby, Swift, R, Elixir, Haskell, OCaml, Julia, Scala, Clojure, Zig, Lua, Dart, Protocol Buffers
Mobile & JVM: Android, Gradle, Kotlin, Kotlin Multiplatform, Compose, Maven, Spring Boot, Ant, Flutter, React Native, Expo
C / C++ & embedded: CMake, Meson, Make, Visual Studio C++, vcpkg / Conan, Unreal, STM32, PlatformIO, Arduino, ESP-IDF, Raspberry Pi Pico, Zephyr, Keil, MicroPython, ARM & x86 assembly, Verilog / VHDL
Infra & tools: Docker, Dev Containers, Terraform, Helm, Kustomize, Ansible, Bicep, Pulumi, Serverless, Nix, PowerShell, Jupyter, LaTeX, Godot, Unity, VS Code extensions
A Python app is found from its code too (main.py, app.py, __main__.py), not only from a requirements file.
Virtual environments are skipped whatever they're called, folders your .gitignore files and VS Code excludes leave out are skipped too, and a manifest at the top of a repo doesn't hide the projects in its subfolders.
To add your own, copy the bundled catalog/default-catalog.json, point stackBuilder.catalogPath at it and add an entry:
{ "id": "rust", "label": "Rust", "markers": ["Cargo.toml"], "profile": "Dev",
"extensions": ["rust-lang.rust-analyzer"], "excludes": ["target"] }
markers are file names (wildcards work). contains is an optional pattern the file's contents must match,
for stacks without a unique file name. profile names the preset the stack belongs to.
How lean opening works
Stack Builder opens the new window through the editor's own command line with the documented
--disable-extension switch, once for every installed extension that isn't in the project's set or your
always-on list. That switch only applies to the window it opens and is never saved, so your installed
extensions and their enabled state are untouched. No shell or script interpreter is involved: the editor's
own executable runs its own command-line script, exactly like the code command does.
Good to know
Workspaces Stack Builder generates for you (a window you applied workspaces to, or projects opened
together) are saved in the project's .vscode/stack-builder folder. That keeps them inside a folder you
already trust, so they don't open in Restricted Mode. The folder ignores itself in git.
Lean windows can only switch extensions off. Keep everything installed and enabled as normal; Stack Builder
installs anything a project needs that's missing, after asking.
Works best with a single editor profile, since the project's extension set does the job profiles used to.
Detection reads file names and a few small manifests (package.json, requirements.txt, pyproject.toml,
pubspec.yaml). It never reads your source code.
Extension names and icons come from the Visual Studio Marketplace; offline, extension IDs are shown instead.
The recent-projects list reads the editor's own recent history where available, plus Stack Builder's own.