Anthropic has long been criticized for forcing Claude Desktop users into a single-account workflow, a restriction that frustrates developers and agencies managing multiple client profiles. A new open-source project, claude-accounts, attempts to bypass this limitation on Windows with a lightweight launcher that supports multiple named profiles. Released as an early preview v0.1.0 on November 9, 2026, the tool isolates user data directories to allow simultaneous sign-ins without modifying the core Claude Desktop application.

The Mechanics of Multi-Profile Isolation

The launcher operates by leveraging the --user-data-dir startup argument, directing each named account to a separate local data folder. This approach keeps account profiles persistent across restarts, relying on Claude’s native login expiry mechanisms rather than implementing custom token management. The application provides a system tray menu and a dedicated interface for adding, opening, renaming, and deleting profiles. It supports both Microsoft Store and standalone installations of Claude Desktop, with detection logic for common executable paths and a manual override for custom locations.

Handling the Google Sign-In Quagmire

One of the most complex challenges in multi-account desktop management is OAuth callback routing. The claude-accounts tool introduces a temporary per-user claude:// command routing mechanism to ensure Google sign-in links reach the correct instance. This routing is active for ten minutes or until manually ended, with original Windows registry associations backed up and restored automatically. If automatic routing fails, the tool offers a manual callback fallback where users paste the claude://login/google-auth link into a dedicated dialog. The project explicitly notes that full Google sign-in completion still requires manual account testing, and no successful automatic routing claim is made for all development environments.

Compatibility and Security Boundaries

The project is strictly a launcher, not a security boundary between Windows users. While it separates profile data, it warns that machine-level services like Cowork, Claude Code, and global shortcuts may still conflict or be shared across instances. The tool is built on .NET 10 and provides self-contained executables for both win-arm64 and win-x64 architectures, eliminating the need for users to install the .NET SDK. All mutable data resides in %LOCALAPPDATA%\ClaudeAccounts\, with atomic writes and backup files to prevent configuration corruption.

Key Takeaways

  • The tool is an independent project (MIT licensed) and is not affiliated with Anthropic.
  • It supports Windows 11 and requires the official Claude Desktop app.
  • Profile separation is achieved via --user-data-dir without modifying Claude Desktop itself.
  • The project is in early preview (v0.1.0) and lacks end-to-end multi-account authentication testing.

The Bottom Line

While the lack of native multi-account support in Claude Desktop remains a significant friction point for professional users, this v0.1.0 preview feels like a necessary stopgap. It’s a technically sound workaround, but the reliance on manual OAuth routing and the 'early preview' status means users should test it cautiously before trusting it with critical client workflows.