Stop fighting VS Code profiles.
Lock extensions & .env per repo.
VS Code still lacks declarative repo-level extension toggling and ${env:VAR} interpolation inside .code-workspace files. ExtProfileLock audits drift, generates exact CLI toggle batches, and injects local .env variables automatically.
The Old Painful Way
- • Manually toggling conflicting formatters & linters across client repos
- • Hardcoding local machine paths because
.code-workspaceskips${env:VAR} - • Restarting VS Code from terminal just to refresh cached shell env vars
With ExtProfileLock
- • Commit one
workspace-lock.jsonso every repo enforces required & disabled extensions - • Interpolate
${env:VAR}straight from.envinto portable workspace configs - • Generate ready-to-run
code --install-extension/--disable-extensionbatches
Up and running in 60 seconds
Add workspace-lock.json
List required and disabled extension IDs in your repo root.
Audit Drift Free
Run runWorkspaceAudit to spot conflicting extensions and parse .env.
Activate Pro Key
Unlock automated CLI batch commands, monorepo lock merging, and ${env:VAR} workspace interpolation.
Simple, developer-friendly pricing
Free Starter
€0
Single-repo extension drift checks & .env parsing.
- ✓ Audit
required&disabledextensions - ✓ Local
.envparser with zero telemetry
Pro License
€19 once
Delivered instantly via Stripe license key.
- ✓ Executable VS Code CLI toggle batch generator
- ✓
.code-workspace${env:VAR}interpolation - ✓ Multi-folder monorepo lockfile merging
FAQ
Why commit workspace-lock.json instead of VS Code Profiles?
VS Code Profiles live globally per user machine, whereas workspace-lock.json lives in Git so teammates stay aligned automatically.
How does offline validation work?
Once validated with Stripe, your Pro license stays active offline with a 7-day grace window.