Multiple Accounts

  • Desktop app
  • Plus, Pro, Team

What it does

Sign in to several accounts of the same CLI (a Work login, a Personal login, one per client) and keep them all active in the same window. AgentsRoom pins an account per project, per sidebar folder or per agent, so a work project runs on the work subscription while a personal project next to it runs on yours, and two agents of one project can even use two different accounts at once. Supported for Claude Code, Codex, Grok Build and Cursor, each isolated by its own configuration directory; Antigravity is the special case, where an "account" is a Gemini API key. Sign-in happens inside Settings, credentials never leave the machine, and the account each agent runs on stays visible on its card. Signed in to AgentsRoom, your accounts (name, colour, email) follow you on every computer, each one waiting for its own sign-in there.

For a one-off, the right-click launch menus also let you start a closed agent or a quick agent on another account for that launch only, without touching what the agent is pinned to.

Where to find it

  • Settings > Multiple accounts (first entry of the Agents & AI group of Settings since 2026-10-23; its own page since 2026-10-21; each provider tab of Settings > AI providers also shows how many accounts it has and a Manage accounts button): pick the provider's tab (Claude, Codex, Grok, Cursor, Antigravity), then its Accounts block (Claude Accounts, Codex Accounts...), with Add an account, Set default, Custom path and the Signed in / Not signed in badge per row. The row at the top shows the login the CLI holds by itself (~/.claude), with its email for Claude. It is called Default while it is the default account, and by its folder (~/.claude) once another account is set as default; its Set default button makes it the default again.
  • Fastest way: the Settings gear at the bottom right of the footer > Multiple accounts (Claude, Codex…) (since 2026-11-05) opens that page on the default provider's tab. Not on the phone, which has no such menu.
  • Per project: Project settings > Defaults > AI providers (account picker). Per folder: the folder's defaults. Per agent: the Claude account / Codex account / ... picker in Add agent and Edit agent, whose sub-label says what Default resolves to ("Project default: Work", "Global default: Personal").
  • Every account picker (Claude, Codex, Antigravity, Grok, Cursor; in Add / Edit agent, project settings, folder settings, the new project dialog and the scheduled task form) ends with a Default account chip once at least one account is configured. The chip carries that name while the CLI's own login is the default, and the folder (~/.claude, ~/.codex...) once another account was set as default. Its sub-label names the CLI's own home (~/.claude, ~/.codex, ~/.grok, ~/.cursor, the signed-in email for Claude) and its tooltip reads "Run on the login the CLI made on its own, even when the project or folder pins another account".
  • The Add multiple accounts dashed button in the agent dialogs jumps to the right Settings tab.
  • For one launch: right-click a closed agent, the menu shows the Provider, Account, Model, Context and Effort rows above the Launch agent button; right-click the Quick agent button (the bolt, in the floating pill above the dock since 2026-10-28; in the agents toolbar when projects sit side by side), and each provider's model list ends with the same Account row.
  • Footer usage panel: one section per signed-in account.

How to use it

Your first account needs no Add an account, on every plan, Free included: agents run on the login the CLI made by itself. Sign in once with the CLI's own command in any terminal, or when the agent starts (claude then /login, codex login, grok login, cursor-agent login), and every agent uses it. Add an account is for accounts on top of that one: one on Free and Plus (since 2026-11-12), unlimited on Pro (past the first extra account on Free or Plus, the button shows a crown and opens the upgrade window).

  1. Settings > Multiple accounts, pick the provider tab, click Add an account. AgentsRoom creates a managed directory and opens a mini terminal running the official CLI login (claude then /login, codex login, grok login, cursor-agent login). Finish the browser step; the badge flips to Signed in when the credentials file appears (Cursor asks you to confirm instead, since it does not publish where it writes credentials).
  2. Name the account, give it a colour (16 distinct colours, or Custom color for any colour, picked in the colour picker or typed as a Hex code), and Set default if every new agent should use it. That colour then marks the account wherever it is named: the avatars, the Usage panel, the quota rules and the line the terminal prints when a quota rule picks the account an agent starts on (since 2026-10-23). On a running agent, the avatar shows the account it really runs on: when a quota rule starts it on another account than planned, the dot takes that account's colour and its tooltip names the planned one (since 2026-10-26).
  3. Pin it where it belongs: on a project (Project settings > Defaults), a folder, or a single agent. Resolution order at launch: agent override, project pin, nearest folder, global default, then the CLI's own home. Default inherits from the level above; Default account stops the cascade and pins the CLI's own login, whatever the project or folder says.
  4. Changing the default account (Settings, or the phone), the account of a project, a folder or a running agent relaunches the affected agents on the new account with their context carried over; a toast tells you how many were relaunched. Agents pinned to their own account, or whose project or folder pins one, are not touched by a change of the default.

One launch on another account: right-click a closed agent (or the Quick agent button), open the Account row, pick an account, then press Launch agent (or the quick agent's model entry). The row opens on the account the agent really resolves to (agent pin, project, folder, global default) and lists Default account plus every account of the chosen provider. The pick is armed for this spawn only and is never written on the agent: at the next opening the agent is back on its usual account. Picking the account it already resolves to arms nothing. The row is hidden when the provider has no account concept or no account is configured yet, and a pick made for one provider is dropped if you switch the launch to another provider.

Codex with an OpenAI API key (since 2026-11-08, reported by Rafael): in the Codex sign-in window (Add an account, or Sign in again on a row), paste the key in Or use an OpenAI API key and click Save key, instead of the browser login. The key becomes that account's login, kept where Codex keeps its own credentials (auth.json in the account's folder, readable by you only), and goes with the account to your SSH servers like a ChatGPT login. Usage is billed per request to the key's OpenAI organization: no plan quota is shown for that account. Only keys starting with sk- are accepted.

Reuse an existing directory: toggle Custom path and point the row at a folder you already signed in to, for example a CCS (Claude Code Switcher) instance under ~/.ccs/instances/<name>. No re-login needed.

Personal configuration: a managed account starts with an empty user layer (no slash commands, skills, subagents, hooks, plugins or user MCP servers). Turn on Use my personal CLI configuration to load your own layer into every account, for Claude Code and Codex; the panel lists what is loaded (Slash commands, Skills, Subagents, Memory file, Hooks, Plugins, User MCP servers, Project MCP servers, and so on) and what is not reaching your agents. For Claude Code the MCP servers you added with claude mcp add at user scope and, since 2026-09-20, those added at project scope for a given folder (-s local) both follow: a project-scope server reaches the same folder inside every account, and a server the account already declares under that name wins. Credentials, sessions and history stay isolated.

Antigravity: the tab holds Gemini API keys (stored in the Secret Manager). Turn on Read the key from the environment for them to take effect; this changes every Antigravity session on the machine, including ones started outside AgentsRoom.

Settings

  • claudeProfiles, codexProfiles, grokProfiles, cursorProfiles, antigravityProfiles (global, read-only over MCP): the accounts, managed by the sign-in flow.
  • defaultClaudeProfileId, defaultCodexProfileId, defaultGrokProfileId, defaultCursorProfileId, defaultAntigravityProfileId (global): the machine default per provider; null = the CLI's own login. Changed from Settings, from the phone or through settings_set (since 2026-10-16), it relaunches the running agents that inherit it.
  • inheritUserCliConfig (global, Settings > Multiple accounts > Settings shared by all accounts, below the provider tabs): load your personal CLI layer (slash commands, skills, subagents, memory file, hooks, plugins, user-scope and per-project MCP servers of the CLI's own config) into managed accounts, off by default, one switch for all providers.
  • accountIndicatorMode (global): color tints the provider mark on avatars and project tiles with the account colour, label writes the account name on the agent card.
  • Long-lived token of a Claude account (Settings > Multiple accounts > Claude, button on each account, since 2026-10-26, none by default): the long-lived token (claude setup-token, or since 2026-11-06 a Claude Platform API key sk-ant-api03-…, billed per use) that agents of that account use on SSH servers, see Remote SSH Offload. A credential, not a setting: kept encrypted in this computer's vault, never synced, never readable or writable by an agent tool.
  • Long-lived sign-in (token) (marked Recommended) or Classic sign-in (Settings > Multiple accounts > Claude, shown on an account while it is not signed in, since 2026-11-10): classic runs /login in the CLI; long-lived runs claude setup-token in the same window, saves the token (valid one year) on this computer and turns on the switch below, so the account shows Signed in (token) and its agents run even without a /login session. A classically signed-in account shows Switch to long-lived sign-in next to its email. Adding an account no longer opens the sign-in window by itself.
  • The ⋯ menu of each account (since 2026-11-10): Set default / Remove as default, Sign in again or switch account, Long-lived sign-in (token), Long-lived token settings, Custom path, Fallback account (checked when eligible), Sign out (claude auth logout), Remove this account. The Default row (~/.claude) has Set default, Sign in again or switch account, Long-lived sign-in (token), Long-lived token settings (since 2026-11-12) and Sign out; signing it out or into another account also changes the claude you run in your own terminal. It has no rename, colour, custom path, fallback switch or Remove: ~/.claude is Claude Code's own folder, the account agents fall back to when nothing pins one, so it is always listed.
  • Also use it for the agents of this computer (useServerTokenLocally on the Claude account, inside its Long-lived token block once a token is saved, off by default, this computer only, since 2026-11-10): the local agents of that account run on the server token instead of the /login session, so they keep working when that session expires after a long sleep of the computer. Remote Control and the claude.ai connectors do not work with this token. The token is then handed to each local agent of that account in an environment variable (CLAUDE_CODE_OAUTH_TOKEN): the agent and the tools it starts can read it, as the option's text says. The Usage panel still reads the /login session and may say it expired while the agents work.
  • Also use it for the agents of this computer, on the Default row (claudeSystemUseServerTokenLocally, global, this computer only, off by default, since 2026-11-12): the same switch for the Default account (~/.claude), inside its Long-lived token settings; Long-lived sign-in (token) on that row turns it on once the token is saved. Its token is kept in this computer's vault and is not sent to SSH servers.
  • claudeProfileId, codexProfileId, antigravityProfileId, grokProfileId, cursorProfileId (project, machine-local, Project settings > Accounts): the account every agent of the project runs on unless it pins its own; an id, "system", or null to inherit the folder, then the machine default.
  • Project and folder pins live in the project's and folder's defaults; agent overrides on the agent (accountProfileId through the MCP executor overrides). The value "system" means the CLI's own login, on every machine. The one-launch pick of the right-click menus is not a setting: nothing is stored.

Agent tools (MCP)

  • agents_save, agents_spawn, backlog_create / backlog_update: accept accountProfileId as an executor override, so a ticket or a spawned agent can be bound to one account (an inapplicable id is dropped and reported). "system" is accepted everywhere and never dropped: it pins the CLI's own login.
  • settings_get / settings_set: read the default account per provider, or change a saved agent's account with scope: "agent" (accountProfileId: an id, "system", or null to inherit). With scope: "project" (since 2026-10-16) or scope: "folder", claudeProfileId, codexProfileId and the other provider keys take an id or "system". Whatever the scope, the running agents whose account changes are relaunched on the new one with their conversation (since 2026-10-16 for the agent, project, folder and global scopes of these tools).
  • usage_overview: quota per signed-in account, per provider.

Providers

  • Claude Code: one directory per account (CLAUDE_CONFIG_DIR), the only provider that exposes the signed-in email, shown per row and in the pickers. An account's identity is its email plus its organization: a personal plan and a Team plan opened with the same email are two accounts, with two quotas, and the organization name is shown next to the email (on the account rows and in the usage panel) only when another account shares that email. The warning "Signed into the same account and organization as ..." appears only when two rows really are one login: they then count as one, agents cannot switch between them and auto-switch cannot take over when one runs out.
  • Codex: one directory per account (CODEX_HOME); Codex always runs from a home AgentsRoom generates per project, which is why the personal configuration switch matters even with a single account.
  • Grok Build (GROK_HOME) and Cursor (CURSOR_CONFIG_DIR): same directory model. Setting XAI_API_KEY or CURSOR_API_KEY does not switch account: both CLIs ignore the key once a session is stored, silently. Separate directories are the only reliable lever.
  • Antigravity: no directory. Google AI Pro and Ultra logins live in the OS keyring, one per machine, and cannot be alternated; an account here is a Gemini API key injected per agent.
  • Other providers: single login, no account tab, and no Account row in the launch menus.

Mobile

Present for everything except sign-in. The phone shows the account each agent runs on (colour dot on the avatar and in the console spec strip) and each project starts on, changes the account of a running agent from the Switch Provider sheet, picks the account when creating an agent or pinning a trigger (with the same Default / Default account choice as the desktop), and sets the machine default in Settings > Multiple Accounts, where the CLI's own login is checked while it is the default and named by its folder otherwise. Adding or removing an account requires the desktop, as the settings card says. The server token of a Claude account is created on the desktop only (it runs claude setup-token there); an agent started from the phone on an SSH server still gets it. The signed-in email, the organization name and the duplicate warning are not shown on the phone, and the one-launch account pick of the right-click menus is desktop only: a quick agent started from the phone follows the usual cascade.

Limits

  • Plan cap on added accounts: one on Free and Plus (since 2026-11-12, before that none on Free), unlimited on Pro. Existing accounts keep working after a downgrade; only additions are blocked. Several Antigravity keys need Pro.
  • Accounts are synced with your AgentsRoom account (since 2026-10-15): name, colour, signed-in email, the auto-switch opt-out and, for Antigravity, the name of the key's secret. The sign-in itself is never synced: sign in once on each computer. Without an AgentsRoom sign-in, accounts stay on the machine.
  • Grok, Cursor and Antigravity expose no login email: an account created by hand on two computers before the sync shows up twice; delete one of them.
  • Deleting an account leaves its directory on disk; agents that pointed at it fall back to the default silently. Its server token, if any, is deleted here and on every SSH server it was copied to.
  • Agents of a project that runs on an SSH server use a Claude account only through its server token: without one they run on the server's own login, and the terminal says so at each launch. The sign-in itself never goes to a server.
  • The Default account chip is not offered on a backlog ticket's account override; set "system" through the MCP tools instead.
  • No personal-configuration sync for Grok and Cursor, and no per-account quota reading for them.
  • Project hooks warning and provider settings read the directory of the account the agents really use, not ~/.claude, once an account exists.
  • The one-launch account pick applies to the launch you commit from that menu, nothing else: a later restart, resume or relaunch of the same agent goes back to its pinned account.
  • Moving an agent to another account of the same CLI keeps its conversation: the transcript is brought to the launch account and resumed there (Claude Code sessions live inside the account that created them). Since 2026-09-20 this also holds when the account change comes from a Temporary launch override or a team run; before, such a relaunch came back to a blank conversation.

Common questions

  • The CLAUDE.md and rules of a Claude account disappeared when I restarted a console. Fixed on 2026-11-10. With Settings shared by all accounts on and an account that has its own config folder, one file AgentsRoom could not write at that moment (held by another console, or by an antivirus, mostly on Windows) stopped the copy of your personal layer halfway: your CLAUDE.md and rules were removed and not put back, again at every launch. The new copy is now built before the old one is removed, so a blocked file no longer erases anything. Update the app; files removed before the update come back at the next console start.
  • Why can't I rename or remove the Default account like the others? The Default row is ~/.claude, the sign-in Claude Code made outside AgentsRoom: the folder belongs to Claude Code and it is the account agents use when nothing pins one, so it is always listed, with no name, colour, path or Remove. Its ⋯ menu has everything else: set it as default, sign in again or switch account, long-lived sign-in (token) and its settings, sign out.
  • My Claude account keeps asking me to /login again after a long weekend away from this computer. The Claude sign-in of a computer that stayed asleep for about two and a half days can come back expired: Anthropic refuses it, AgentsRoom never touches it. Use Long-lived sign-in (token) on that account (Settings > Multiple accounts > Claude): its agents then start on that token, valid one year. Remote Control and the claude.ai connectors do not work with it.
  • Can my Codex agents run on an OpenAI API key instead of a ChatGPT plan? Yes, since 2026-11-08: Settings > Multiple accounts > Codex, Add an account (or Sign in again on an existing row), then paste the key in Or use an OpenAI API key and click Save key. Setting OPENAI_API_KEY in the provider's Environment variables is not enough: Codex ignores that variable for its own login. The CLI's own login (~/.codex, no added account) takes a key from a terminal with printenv OPENAI_API_KEY | codex login --with-api-key.
  • I moved an agent to another account (or changed only its effort) in Switch model and it started an empty conversation. Fixed on 2026-10-25 (reported by Ioan Bita): when only the account or the reasoning effort changes (same CLI, same model), the relaunch now resumes the same conversation on the new account instead of handing over a Raw transcript. A real change of CLI or model, or a summary you ask for, still goes through the handover.
  • I'm on Free and Add an account shows a crown. How do I connect my Codex, Cursor or Claude account? The crown only appears once you have used your one free extra account. You don't need that button for your first login. Sign in with the CLI itself, once: codex login, cursor-agent login, or claude then /login, in a terminal or in the agent's own terminal at its first launch. Your agents then run on that login, which is the row at the top of the provider's Accounts block. Add an account adds a SECOND account next to it: one extra account on Free and Plus, unlimited on Pro.
  • I switched my agents to another account, but every message still hits the old account's usage limit. Fixed on 2026-10-16 (reported by a user). A running agent keeps the account it was started with until it is relaunched. Changes made in the app already relaunched it, but changes made by an agent through the settings tools (agents_save, settings_set on an agent, a project, a folder or the default account) were only stored: the console kept the old account. They now relaunch the agents concerned too. A pin made this way also replaces a pin left by an automatic account switch, which could otherwise hand the agent back to the exhausted account at its next launch. Update AgentsRoom.
  • Can I add DeepSeek, MiniMax, MiMo or another Anthropic-compatible API as a Claude account, and switch between them? No, an API provider is not an account. A Claude account in AgentsRoom is a configuration directory signed in with an Anthropic login. To run Claude Code on an Anthropic-compatible API, set ANTHROPIC_BASE_URL and the key (ideally {{secret:NAME}}) as environment variables on the agent or on the project, and make one agent per provider: switching provider is then switching agent. Since 2026-11-06 MiniMax and GLM models also have their own CLIs in AgentsRoom, MiniMax Code and ZCode (a community client), see Multi-Provider Support. Settings > AI providers holds the machine-wide level. CLIs that handle several backends themselves, such as OpenCode (/connect) or oh-my-pi (/login), are the other way. See Multi-Provider Support.
  • Do I need CCS or a shell wrapper? No. AgentsRoom sets the CLI's own directory variable per agent; CCS profiles can be reused through Custom path.
  • My agents run on an SSH server and ignore the Claude account I pinned. Give that account a server token: Settings > Multiple accounts > Claude, Long-lived token on the account, Create the token (AgentsRoom runs claude setup-token; sign in to claude.ai in your browser with that same account first). From the next launch the agents on the server run on it, and quota rules can move them between accounts that have a token. See Remote SSH Offload.
  • My Codex agent said "No saved session found with ID" after I changed its account. Fixed on 2026-10-01: when a Codex agent starts on another account than the one its conversation was recorded on (after a restart of the app, or with a one-launch pick from the menu), its conversation is now found in the other account's folder and brought over before it resumes. Update AgentsRoom.
  • I set some Claude CLI options (the provider's own settings, its /config) for one account. Do I have to set them again on my second Claude account? No. Settings > AI providers > Claude > Claude CLI settings > Open writes each change into every Claude account added in AgentsRoom, so all your agents behave the same whatever their account (since 2026-11-11 this also covers the options Claude keeps in each account's .claude.json, such as auto-compact). Your own ~/.claude, used outside AgentsRoom, is left untouched once an account exists. Slash commands, skills, memory and hooks are a separate switch: Use my personal CLI configuration.
  • Why did my slash commands disappear on a new account? The account directory starts empty. Turn on Use my personal CLI configuration in Settings > Multiple accounts.
  • claude mcp list inside an agent shows fewer servers than in my own terminal. A managed account receives nothing from your own ~/.claude.json unless Use my personal CLI configuration is on. With it on, both your user-scope servers and the project-scope ones you added for that folder are merged into every account at each launch (project scope since 2026-09-20). Servers declared in AgentsRoom itself (Settings, project or agent) reach every account regardless: see MCP Servers.
  • I am on a personal project but my work account is used. Check the Default account row and the pickers: the sub-label says which account Default resolves to. Also see Account Auto-Switch: a launch moved off an exhausted account shows a toast.
  • I set another account as default, but my agents still run on the old one, and after a restart the usage panel shows "Default account" with "The usage lookup for this account was rate limited". Fixed on 2026-10-02, two causes. The CLI's own login (~/.claude) kept the name Default account even after you set another account as default, so an error on it read as an error on your default, and its row titled Default at the top of Settings read as your choice being reverted. It is now called by its folder (~/.claude) everywhere as soon as another account is the default; the rate-limit message is about that login only and is retried automatically. And changing the default in Settings did not move the agents already running: they now relaunch on the new default with their conversation, as when the change comes from the phone, a project or a folder. Agents pinned to an account, or whose project or folder pins one, keep it. Update AgentsRoom.
  • Can two agents in one project use two accounts? Yes. Pin the project on one, override the other agent in Edit agent.
  • My project pins my work account. How do I run one agent on my personal login, the one the CLI holds in ~/.claude? In Add agent or Edit agent, pick the Default account chip at the end of the account picker (not Default, which inherits the work pin). That agent runs on the CLI's own login; the rest of the project stays on the work account. Same chip on a folder or a project to point them at the CLI login.
  • My personal Claude plan and my Team plan use the same email. Can I add both? Yes. Since 1.178.0 the two are told apart by their organization: each gets its own row, its own usage section and its own quota, with the organization name shown next to the shared email. Before, they were flagged as duplicates and merged in the usage panel, so the Team plan was never shown and auto-switch could not use it. Signing the second row into the same email and the same organization is the only case that still warns.
  • My agent's account is out of quota. Can I run it once on another account without editing it? Yes. Right-click the closed agent, open the Account row, pick the other account and press Launch agent. The agent's record is untouched: it comes back on its usual account next time. Same row when right-clicking the Quick agent button for a quick agent.
  • Can new launches go to my other account automatically when the first one is nearly full? Yes, with a quota rule (Usage panel > Quota management): the template Use another account redirects launches to the account you choose from a threshold, and the action Move running agents moves agents already running. See Quota Rules.
  • My Codex accounts stay at 99 % with "Reported 2 days ago: these figures refresh when an agent runs", and Refresh changes nothing. Most often your internet goes through a proxy (a company proxy, or a tool such as Clash or Surge in system proxy mode). Fixed on 2026-10-09: every quota reading now goes through the system proxy of your computer, like the browser and the CLIs, so quota rules stop setting those accounts aside on old figures. When a live reading fails, the panel now writes the reason under the date (for example "Could not reach the usage API for this account."). A proxy declared only as an environment variable in your shell profile, with no system proxy and no TUN mode, is still not seen.
  • My Antigravity agent quits right at launch with "the GEMINI_API_KEY environment variable is not set". Why? Antigravity is set to read its Gemini key from the environment, and this agent has no Antigravity account bound to it, so it gets no key. Since 2026-11-01 the banner above the console says so: "The Antigravity CLI is set to read its API key from GEMINI_API_KEY, and this agent has none, so it quit at launch." In Settings > Multiple accounts, bind an account to this agent (or set one as default), or turn off Read the key from the environment, then relaunch the agent.
  • Can I alternate two Google subscriptions on Antigravity? No tool can: the login is in the OS keyring, one per machine. Use Gemini API keys instead.
  • I added my work account on one computer. Why is it missing on the other? Fixed on 2026-10-15: your accounts now follow your AgentsRoom account. On the other computer the account appears with the same name, colour and email, marked not signed in: press Sign in once. The sign-in cannot be copied between computers because the provider renews its token on each use, and two computers sharing one would sign each other out. If that computer already had the same login under another row, both are merged into one and the projects, folders and agents pinned to it keep working.
  • Are my credentials sent anywhere? No. Sign-in runs the official CLI locally; AgentsRoom only watches for the credentials file.
  • I logged out of Claude and into another account, but the Default row still shows the old email, flagged as a duplicate. Fixed on 2026-10-09 (reported by a user). When the CLI's own folder held two login files (an old one left by a past setup and the live one), the row read the old one. It now reads the most recently written file, which is the login the CLI really uses.