Home / Setups

Example setups

Each setup below is a set of separate app instances: every account in its own app, with its own login, its own Dock icon and its own colour. Copy one as it is, or use it as a starting point. If you'd rather start from your role, see use cases.

AI developer

Work and personal AI accounts, plus a client's editor kept apart from yours.

Each Claude keeps its own login, plan and conversation history, so the work subscription and your own account are both a click away. The client's VS Code has its own extensions and settings, and MacDupl gives the Claude Code extension inside it its own account, separate from the one in your main editor.

Good to know

Cowork runs in a Claude instance, but linking it to your computer (attached folders, computer use) only works in your original Claude. ChatGPT runs on MacDupl's native tier, which is Beta.

Freelance developer with two clients

Each client's chat, editor and tracker as one set you open and close together.

Put each client in its own workspace. Launch All opens that client's apps in one click and Quit All closes them at the end of the day, so a client's Slack never pings you on another client's time and their extensions never load in the other editor.

Good to know

Install Slack from slack.com, not the Mac App Store. The App Store build is sandboxed and can't be cloned.

Community manager

Your own accounts and the community's accounts, never mixed up.

  • Discord (Main) — Discord Verified
  • Discord (Community) — Discord Verified
  • Telegram (Personal) — Telegram Verified
  • Telegram (Community) — Telegram Verified

Two Discord accounts stay signed in side by side with no re-login, and each Telegram instance keeps one account open in its own window. The colour tells you which account you're about to post from before you type.

Good to know

Use Telegram's direct download from telegram.org, not the App Store build.

Work and personal on one Mac

The work set closes at six; the personal set stays open.

A work Chrome and a personal Chrome each have their own extensions, cookies and Google sync account, in their own Dock icons. A second Spotify shows up as its own device in Spotify Connect, so two accounts don't fight over playback.

Meetings across organisations

Your own Zoom, a client's Zoom and a client's Teams tenant, all signed in.

Each Zoom instance keeps its own session, so signing into the client's account no longer signs you out of your own. Single sign-on works too: sign-in links go to whichever instance is in front, so the browser login lands where you started it.

Good to know

Install Zoom from zoom.us. Teams is listed as Should work: same engine as tested apps, not tested hands-on yet.

These setups are examples, not requirements: mix any apps from the compatibility list. Some services limit how many accounts one person can run, so following each service's terms is up to you.

Build any setup in a few minutes

  1. Create a workspace for each client or persona (Acme, Work, Personal). Picking a workspace when you create an instance fills in its colour and names it “App (Workspace)”, the naming used above.
  2. Add the instances. Pick an app, keep or change the name and colour, and click Create. Each one takes about 2 seconds.
  3. Sign in once in each. Every instance starts signed out and keeps its own login from then on.
  4. Open a whole set at once. Launch All starts a workspace's apps together; Quit All closes them.

Try a setup on your own Mac

The 3-day trial is fully featured, so you can build a whole setup and see how each app behaves before paying. After that it's $19 once.