Anthropic’s Claude Desktop has long suffered from a rigid single-instance limitation on macOS, forcing users to sign out of one account to access another. A new open-source utility called claude-multi-desktop breaks this bottleneck by leveraging Electron’s native --user-data-dir flag. The script allows a single Mac to run multiple independent Claude Desktop windows, each tied to a different account, without modifying the core application binary.
Technical Implementation and Architecture
The tool operates as a lightweight bash script that launches separate instances of the existing Claude.app with distinct data directories located in ~/Library/Application Support/. Unlike heavier virtualization approaches, it does not copy, re-sign, or patch the Anthropic binary. This design ensures that when Anthropic pushes a Claude Desktop update, every active account instance receives the patch automatically. The launchers themselves reside in ~/Applications, appearing in Spotlight and Launchpad as distinct entities like 'Claude Work' or 'Claude Personal'.
Shared Context and Session Handoffs
The most significant architectural choice is the sharing of the ~/.claude directory across all accounts. This means that skills, CLAUDE.md files, memory, and MCP servers defined in one account are instantly visible to all others. Furthermore, because all instances share the same Claude Code session list, users can execute cross-account commands. A session in a work account can identify and message an idle session in a personal account using Claude Code’s ListAgents and SendMessage tools, effectively allowing for complex, multi-account workflow orchestration.
Intended Use and Limitations
The developers are explicit about the tool’s scope: it is built for individuals managing a personal and a work account simultaneously, not for abusing usage quotas. The disclaimer strictly advises against using multiple accounts to pool or stretch limits, stating that such use cases are unsupported. Installation is flexible, supporting Homebrew, npm, or a double-click disk image, though the unsigned nature of the macOS installer requires manual approval in System Settings on Sequoia and later versions.
Key Takeaways
- Zero Patching: The tool uses public Electron flags, leaving
Claude.appuntouched and ensuring update compatibility. - Shared Context: All accounts read the same
~/.claudeconfig, meaning skills and MCP servers are global to the user. - Cross-Account Messaging: Sessions can communicate via
ListAgentsandSendMessage, enabling handoffs between personal and work contexts. - Strict Usage Policy: The project explicitly disavows quota farming, targeting legitimate dual-account users only.
The Bottom Line
This tool solves a specific, annoying friction point for power users without resorting to fragile hacks, making it a welcome addition to the OpenClaw ecosystem despite its strict non-commercial usage warnings.