Two VS Code instances with separate accounts and extensions
Keep a client's setup in a second VS Code on the same Mac: both open at once, each signed in to its own account, with its own notifications and Dock icon. Parallex is free for now, Pro included.
Can you run two VS Code instances with different accounts on a Mac?
VS Code's profiles separate settings and extensions inside one VS Code, and code --user-data-dir <folder> starts a separate one from Terminal. A second VS Code made by Parallex does that for you, with its own sign-ins, extensions and Dock icon, or sharing your settings.
How
- Install Parallex (below). Your Visual Studio Code isn't changed.
- Choose New Instance and pick Visual Studio Code. Name it for what it's for, like “Visual Studio Code Work”, and give it a color.
- Open it and sign in with the other account. Both run at once, each in its own windows, each with its own Dock icon.
Or without Parallex: every way to run an app twice on a Mac, compared.
What you get with Visual Studio Code
- Its own copy of VS Code, with its own Dock icon, name and color, its own notifications, and its own macOS permissions.
- Its own Library and keychain, so its sign-in, settings and caches are separate from your other VS Code, and it has its own encryption key in the keychain.
- Guard keeps the copy out of the original's data, and the isolation check shows what the copy has opened of yours.
- Kept up to date by Parallex: VS Code's own updater is turned off in the copy, and Parallex refreshes the copy when your VS Code updates.
- Share settings (an option): your settings, keybindings, snippets and extensions, kept in step, while the copy's sign-ins and open projects are its own.
~/.vscodestays with the copy, so its extensions and shared state don't touch yours.- Works for VS Code Insiders too.
Tested every night
Parallex's compatibility lab makes a fresh copy of Visual Studio Code 1.144.0 every night on a clean Mac and opens it. On October 30, 2026, on macOS 26.6.2, the copy ran, and nothing reached the original's data. Its copies have run clean on all 31 nights since September 30. See every app's latest result.
Good to know
- With Share settings on, keep Settings Sync off in the copy.
Questions
Aren't VS Code profiles enough?
Profiles change settings and extensions inside one VS Code. An instance is a second VS Code, running beside the first, with its own sign-ins, state and window.
Will the second VS Code keep working when VS Code updates?
Yes. The copy's own updater is off, and Parallex refreshes the copy when your VS Code updates, keeping its sign-in and data. If an update gets in the way, the copy can go back to the version it was on, data too, while your VS Code moves on.
What does Parallex cost?
Nothing, for now. Since October 31, 2026, Parallex is free, Pro included, on as many Macs as you like, with no license, no card and no account. That's for an undefined time, not a trial: there's no countdown. Licenses people bought stay valid. If Parallex is ever paid again, this site will say so before anything changes, and every copy you've made keeps opening, and can always be exported, either way. Pro is moving a copy to your other Mac (Carry), running several sealed agents on one task (Fleet), sharing your Claude setup across accounts, usage for each account in the menu bar, folders that switch your identity in Terminal, agent workspaces (an identity of its own for each AI agent) and a Parallex MCP server.
Get Parallex
Free for now, Pro included, on as many Macs as you like. For macOS 14 and later.
Or in Terminal
curl -fsSL https://parallex.mandip.dev/install | shOr with Homebrew
brew install --cask mandipadk/parallex/parallexThen choose New Instance, pick Visual Studio Code, and give it a name.
Already have Parallex? Make a second Visual Studio Code: New Instance opens with Visual Studio Code picked, for you to name and color.