# Clawdrobe > Clawdrobe is a free macOS app that runs several Claude Desktop accounts side by side: each account gets its own app, Dock icon, sign-in and chat history, with usage limits, alerts and a quick switcher in one place. Free for two accounts; Clawdrobe Pro is a one-time $10. Clawdrobe is a native macOS app (macOS 26 or later · Apple silicon and Intel). Each Claude Desktop account gets its own app built from the installed Claude: its own Dock icon, sign-in and chat history. Clawdrobe shows each account's 5-hour and weekly usage (read from files Claude Desktop writes on the Mac) and, from the readings Claude kept, the weekly pace (percent a day lately), when the week runs out at that pace and when it resets, a line on each usage bar at how much of that window has gone by (when its reset time is known), the weekly room left across all accounts together (in whole weekly limits), how long it lasts at their combined pace and whether that pace is more than the accounts keep up with each week, alerts at 70/80/90% of a limit and when an account's week won't last until the reset at the pace of the last day, opens accounts with ⌘1–⌘9, ⌘0 (most room left) or a quick switcher on ⌃⌥Space, closes idle accounts to free memory, and gives each account its own claude- Terminal command (set in the account's Tools) so Claude Code runs as that account; the Tools button also opens Claude Code as that account in Terminal, iTerm, Ghostty or another terminal chosen in Settings. An account can have its own commit name and email (the account's Tools → Commit As): Claude Code sessions from its claude- command, the Tools button and its folders (with the folder hook) commit with them (git's author and committer variables, only in those sessions and folders). An opt-in clawdrobe-account command (Settings → General) puts the account's name in Claude Code's status line, so each session shows which account it runs as. Clawdrobe adds that status line to ~/.claude/settings.json on request (one click; the rest of the file is kept as it was, the old file is backed up, and a status line the user already has is never replaced). With it, Clawdrobe also keeps the 5-hour and weekly usage and reset times Claude Code passes its status line (only those numbers, in a local file), so an account's usage stays current while Claude Code runs, even when Claude Desktop hasn't updated it lately. Summary lists every Claude Code session running on the Mac (from Terminal or an account's Code tab) with the account it uses (from its CLAUDE_CONFIG_DIR), its folder and when it started; Clawdrobe only reads the process list for this. Folders can belong to an account (the account's Tools → Folders, plus one hook line in ~/.zshrc): plain claude in Terminal inside a client's or project's folder then runs as that account. Added accounts share the main account's Claude Code skills, settings, CLAUDE.md, plugins and MCP servers, and Claude Desktop's own MCP servers (claude_desktop_config.json); every account's Code tab lists the Code sessions started in any account. Sign-ins and chats stay separate. When Claude Desktop updates, each account's app is rebuilt from the new Claude the next time it opens; accounts that were open during the update are listed in Summary and the menu bar with a button that restarts them on the new Claude. It is not a hack: each account app is a copy of the installed Claude running Claude's own unchanged code with its own data folder, so it signs in and talks to Anthropic exactly like Claude Desktop; Clawdrobe never sits between Claude and Anthropic, automates chats or touches usage limits. It never reads Claude passwords, tokens or chats and never calls Claude's servers. Free: every feature for 2 accounts. Clawdrobe Pro: a one-time $10 license key for unlimited accounts on up to 3 Macs; no subscription, no refunds. Clawdrobe is not affiliated with Anthropic. ## Docs - [Terms of Service](https://clawdrobe.com/terms.md): The agreement for using Clawdrobe and buying Clawdrobe Pro. - [Privacy Policy](https://clawdrobe.com/privacy.md): What Clawdrobe collects, why, and who processes it. - [Changelog](https://clawdrobe.com/changelog/): what's new in each version ## Blog - [Claude Code With Multiple GitHub Accounts](https://clawdrobe.com/blog/claude-code-multiple-github-accounts/): Claude Code pushes and opens PRs as whichever GitHub account git and gh use in that folder. How to check it and give each project the right account. - [Claude Code Committing With the Wrong Git Email?](https://clawdrobe.com/blog/claude-code-commit-wrong-email/): Claude Code commits with whatever git is set to in that folder, not your Claude account's email. How to check it, fix it per folder, and repair past commits. - [How to Run Claude Code Sessions in Parallel](https://clawdrobe.com/blog/claude-code-parallel-sessions/): Run several Claude Code sessions at once without edits colliding: one git worktree per session, agent view for background tasks, and what it does to limits. - [Claude Team Plan: Price, Limits and Team vs Pro](https://clawdrobe.com/blog/claude-team-plan/): Claude Team costs $25 a seat a month ($20 billed yearly) for 2 to 150 people. What Standard and Premium seats get, how limits work, and Team vs Pro. - [Claude Usage Tracker: 4 Ways to See Your Limits](https://clawdrobe.com/blog/claude-usage-tracker/): Track your Claude usage with Settings → Usage, Claude Code's /usage and status line, ccusage, or Clawdrobe for several accounts. What each one shows and misses. - [Claude Desktop vs Claude Code: Which One to Use?](https://clawdrobe.com/blog/claude-desktop-vs-claude-code/): Claude Desktop is the Mac and Windows app with Chat, Cowork and a Code tab; Claude Code is the coding agent behind that tab and in your terminal. Which to use when. - [Claude Pro vs Max vs Ultra: Which Plan Do You Need?](https://clawdrobe.com/blog/claude-pro-vs-max/): Claude Pro is $20 a month, Max $100 and Ultra $200. What each one adds in usage, Fable access and limits, and how to tell from your own usage which to pick. - [How to Switch Claude Accounts in the Terminal](https://clawdrobe.com/blog/switch-claude-account-in-terminal/): Switch Claude Code to another account with /login or claude auth, check which one you're on, and set up one command per account so you never log in twice. - [Claude Code: A Different Account for Each Project](https://clawdrobe.com/blog/claude-code-different-account-per-project/): Make plain claude use your client's account in the client's folder and your own account everywhere else, with direnv, a zsh hook or Clawdrobe. - [Claude Code Sessions Gone After Switching Accounts?](https://clawdrobe.com/blog/claude-code-sessions-gone-after-switching-account/): Switched accounts in Claude Desktop and the Code tab is empty? Your sessions aren't deleted. Why the list changes, how to get them back, and how to see them everywhere. - [How to Sign In to Two Claude Accounts at Once](https://clawdrobe.com/blog/sign-in-to-two-claude-accounts/): Stay signed in to a work and a personal Claude account at the same time in the browser, Claude Desktop and Claude Code, without the sign-in landing in the wrong one. - [Claude Usage Limit Reached? What to Do Next](https://clawdrobe.com/blog/claude-usage-limit-reached/): Hit "5-hour limit reached" or "You've reached your weekly limit" in Claude? How to tell which limit stopped you, your options, and how to avoid a repeat. - [Can You Have Multiple Claude Accounts? What's Allowed](https://clawdrobe.com/blog/claude-multiple-accounts-allowed/): Anthropic's terms don't limit you to one Claude account, but they ban sharing an account, dodging bans and bypassing restrictions. Here's where the line is. - [How to Manage Multiple Claude Accounts Without Mixups](https://clawdrobe.com/blog/how-to-manage-multiple-claude-accounts/): A simple system for running several Claude accounts day to day: one job per account, clear names, limits you can see, and Claude Code on the right login. - [Claude's 5-Hour and Weekly Limits, Explained](https://clawdrobe.com/blog/claude-5-hour-and-weekly-limit/): How Claude's 5-hour session limit and weekly limit work, when each one resets, what uses them up fastest, and your options when you hit one. - [Claude Work and Personal Account: How to Switch or Use Both](https://clawdrobe.com/blog/claude-work-and-personal-account/): Same email? Claude's switcher in the lower left holds both accounts. Different emails? Four ways to run work and personal Claude on one Mac, plus Claude Code. - [How to Switch Accounts in Claude Desktop](https://clawdrobe.com/blog/switch-accounts-claude-desktop/): Claude Desktop can switch between a personal and an organization account on the same email. For two different emails, here are your options. - [How to Use Multiple Accounts in Claude Code](https://clawdrobe.com/blog/claude-code-multiple-accounts/): Run Claude Code as your work account in one terminal and your personal account in another, with CLAUDE_CONFIG_DIR, shell aliases or Clawdrobe. - [How to Use Multiple Claude Accounts on One Mac](https://clawdrobe.com/blog/multiple-claude-accounts-on-one-mac/): Four ways to use a work and a personal Claude account on the same Mac, what each one costs you in time, and how to keep both open side by side. ## Optional - [Everything in one file](https://clawdrobe.com/llms-full.txt) - [Download](https://clawdrobe.com/download): the newest notarized build (.dmg)