Home / Compatibility / Visual Studio Code
Run two VS Code instances on Mac
A VS Code instance starts as a clean editor: its own extension set, its own settings, its own sign-in. Install and remove extensions in it without touching your original editor.
7-day free trial · $19 once · macOS 13+ · notarized by Apple
What you get
- Its own extensions. Each instance keeps a separate extension set — one editor per client, project or stack, with nothing bleeding across.
- Its own settings and sign-in. Separate settings, separate account. Your main editor stays exactly as you left it.
- Forks work too. Insiders, VSCodium, Cursor and Antigravity IDE are detected generically, not from a list.
- A Claude account per instance. The Claude Code extension and CLI inside an instance hold their own Claude account — and the instance's integrated terminal uses that same isolated account.
Verified as of MacDupl 0.1.9. On 0.1.8 and earlier, instances shared the original's extensions folder — update MacDupl if you're on an older build.
- Verified as of MacDupl 0.1.9 — on 0.1.8 and earlier, instances shared the original's extensions folder.
- VS Code forks — Insiders, VSCodium, Cursor, Antigravity IDE — are detected by engine, not from a hardcoded list.
How to set it up
- Pick the app
Open MacDupl and choose Visual Studio Code from the list of apps installed on your Mac. - Name and colour it
Call it “Work”, “Personal” or a client's name, and give it one of nine icon tints. - Hit Create
About two seconds later there's a new Visual Studio Code in your Dock — install only the extensions that client or project needs — the new editor starts clean.
Questions about Visual Studio Code
Can I sign into a different Claude account per editor?
Yes. The Claude Code extension in an instance holds its own Claude account, verified with the extension's shipped binary, and the instance's integrated terminal uses the same isolated account. Note this is scoped to Claude Code specifically — extensions that keep account state in your home folder or the Keychain still share it.
Do my settings carry over?
An instance starts clean, which is what keeps client setups apart. Configure it once for that project and it stays that way.
Does it work with Cursor?
Yes. VS Code forks are detected generically, so Cursor, VSCodium, Insiders and Antigravity IDE all clone the same way.
What happens when VS Code updates?
Instances keep themselves in sync with the original — MacDupl refreshes them when the original updates, with your settings and sign-in intact.
Try it on your own Mac
The free trial classifies every app in your Applications folder instantly, so you can see exactly how Visual Studio Code is handled before paying anything.