I have a work Cursor account and a personal one. Cursor only lets one account be signed in at a time, so switching means signing out and back in. A community extension called Userdata Switcher gets around that, and it works well enough that Cursor should build the same thing in.
What it is
Userdata Switcher is a free, MIT-licensed extension by forum user domoarigatomrburato. It’s on Open VSX (version 1.4.2 when I checked), and the source is on GitHub. The author announced it on the Cursor forum on June 14, 2026. They said they built it because they also pay for both a work and a personal subscription.
It opens a separate Cursor window for each “userdata.” Each one has its own sign-in, subscription, chat history, caches, tabs and extension state. That means a Work window and a Personal window can be open side by side, each signed into its own account.
How it works
VS Code-based editors, Cursor included, have a --user-data-dir launch flag. It tells the editor which folder to use for its state: login, settings, history and so on. Point it at two different folders and you get two separate editors:
cursor --user-data-dir="~/cursor-work"
cursor --user-data-dir="~/cursor-personal"Cursor staff have posted that exact workaround on the forum. The extension puts a UI on top of it:
- A status bar item (for example
Work (default)), or Userdata Switcher: Open Userdata in New Window (Cmd+Shift+Uon macOS,Ctrl+Shift+Uelsewhere). - Create a new userdata, either copying your current settings, keybindings and snippets once or starting empty. Name it and sign in.
- Rename, reveal or delete userdatas from a manage menu. Each one shows as
runningoridle. - Extensions are installed once and shared through a common
--extensions-dir. There’s no token copying, no SQLite edits and no background sync.
Platforms and limits
- OS: the author says they tested it on an Apple Silicon Mac, a Windows 11 VM and a Linux VM. The readme handles all three (Finder/Explorer/file manager, Trash/Recycle Bin).
- Editors: Cursor, VS Code, VS Code Insiders and Antigravity IDE. It doesn’t try to detect other VS Code forks.
- Local only: it runs in the local desktop UI and doesn’t activate in Remote SSH, WSL, dev containers or other remote extension hosts.
- Settings drift: theme, settings, keybindings and snippets are copied once, then each userdata changes on its own.
- Deleting: you can’t delete the current window’s userdata or the default one. Deleting a running userdata quits that instance first.
- Not covered by the flag: Cursor staff have noted that the
--user-data-dirworkaround “doesn’t cover everything, like MCP configurations.” The mobile app has no equivalent.
Cursor should build this in
Cursor knows people want this. In July 2026, Cursor staff member deanrie wrote that “there’s no native account switcher yet, and it’s not on the roadmap right now.” On October 11 he repeated it in the same thread: “The request is on our radar, but it isn’t on the roadmap right now.” He also confirmed that “having multiple accounts is totally fine. The only restriction is sharing a single account.”
So having more than one account is allowed and the workaround is official, but users still have to use launch flags or a third-party extension to get it. A built-in account switcher would cover what the flag misses (MCP config, mobile), make billing mistakes on the wrong account less likely, and make it clear which account is running in which window. VS Code already handles multiple accounts for GitHub and Microsoft sign-in, and Cursor could do the same for its own account.
If you want it too, add your vote and use case to the Seamless Account Switching in Cursor thread. Staff keep pointing people there. Until Cursor ships something, Userdata Switcher is the easiest way to run both accounts at once.