Account Auto-Switch
- Desktop app
- Plus, Pro, Team
What it does
When the account an agent runs on hits its usage limit mid-task, AgentsRoom hands the same conversation to another signed-in account of the same provider and the work continues: no restart from a blank prompt, no waiting for the 5-hour or weekly window. The exhausted account is benched until its quota resets, then rejoins the pool by itself. It is what keeps unattended runs (scheduled tasks, backlog tickets, team workflows) alive past a quota wall, and what makes several smaller subscriptions behave like one bigger plan.
To leave the CLI altogether rather than the account, the same action offers Another CLI (see Quota Rules). Since 2026-09-23 the trigger is a quota rule (action Move running agents, switch-running), not a global switch: moving work onto another subscription is a billing decision, and an explicit rule is the strongest form of asking for it. The rule watches a gauge and fires once per quota window; the switch machinery (bench, candidate election, transcript migration, resume) is unchanged.
Users who had the retired switch on were migrated automatically at first launch: for each provider with readable gauges and a spare account, two rules were seeded (session ≥ 99 % and week ≥ 99 %), named after the old setting. The rules are ordinary: editable, disablable, deletable.
Where to find it
- Usage panel > Quota management (Control column, the middle one, next to the gauges): the rule list and its editor. Pick the action Move running agents in the rule editor (there is no template for it).
- Settings > Multiple accounts, last row of Settings shared by all accounts: the Quota rules shortcut (since 2026-09-28), which opens the same rule window from where one looks for it first.
- Each account row in Settings > Multiple accounts has a Backup account / Never used as backup toggle (shown from two accounts), which opts an account in or out of the fallback pool. Shown for Claude, Codex and Grok only: a rule needs a readable gauge.
- In the terminal, a line "Usage limit reached on X. Continuing on Y..." when the switch completes, a toast "Started on Y" when a launch was moved pre-emptively, and a system notification Account switched.
How to use it
- Sign in to at least two accounts of the same provider (see Multiple Accounts; the CLI's own login counts as one).
- In the usage panel, create a rule: quota of that provider, Most constrained account (or a specific one), window Session (and a second rule for the weekly window if you want both walls covered), threshold 99 %, action Move running agents.
- Optionally mark accounts that must never be borrowed (strict work / personal or client A / client B separation) as Never used as backup. They still work for agents explicitly bound to them.
- Nothing else. When the gauge crosses the threshold, AgentsRoom benches the account, picks the signed-in account of the same provider with the most quota left (or, since 2026-11-05, the next one to reset if the rule's Which account says so), migrates the transcript when the provider needs it, relaunches the CLI on the same session and sends a short instruction to continue the interrupted work.
Pre-flight: an agent about to start on an account a rule has benched is started on a healthy one instead, and a toast says so.
Never in the middle of a turn (since 2026-10-27): an agent that is working (a request or a tool running, a question open in its terminal, a scheduled run whose first turn has not finished) is left alone and moved on a later reading, once its turn is over. An account that really runs dry ends the turn by itself, so the agent is then moved and told to pick the work back up. The rule also reads the account the agent was actually LAUNCHED on: an agent a redirect rule already started on another account is not on the watched account and is not moved.
Settings
quotaRules(global, usage panel > Quota management): the rules themselves, includingswitch-runningones. Pilotable over MCP throughsettings_set.accountAutoSwitchMigrated(read-only state): one-time marker that the retired global switch was carried over (or was never on). The oldaccountAutoSwitchkey is captured once, then dropped from the settings file.- Per-account exclusion: the Backup account toggle on each row (stored with the account).
Agent tools (MCP)
settings_setquotaRules: read or rewrite the rules (object array, see the spec entry for the exact shape).usage_overview: the per-account quota bars the decision is based on.
Providers
- Claude Code: the conversation is copied into the incoming account's directory before the relaunch (a Claude session physically lives in the account that created it), then resumed.
- Codex: credentials are rebound and the session resumed; rollouts live in the per-project home AgentsRoom generates, so nothing moves.
- Grok Build: the agent relaunches on the other account; its session id is not carried, so the conversation restarts. Grok publishes one gauge for the whole provider, not one per account.
- Cursor and Antigravity: no automatic switch anymore. Their gauge in the Usage panel is one reading for the whole machine, not one per account, so no rule can tell their accounts apart; the retired switch reacted to the CLI's own wall message, which was their only trigger. Manual switching (agent sheet, switch modal) still works.
- Kimi, OpenCode: gauges exist but they have no account concept, so no pool to switch within.
Mobile
The rules run on the desktop for every agent, including ones piloted from the phone; the phone shows the new account on the agent's dot and spec strip. Rules can be edited from the phone (Activity > Usage > Quota management, plus a Quota rules shortcut in Settings > Usage); see Quota Rules.
Limits
- Needs at least two usable accounts of the same provider, so in practice Plus (one added account plus the CLI's login) or Pro.
- A rule fires once per quota window (it re-arms at the reset), not on every tick; a resumed conversation is nudged back into motion once it has relaunched.
- The pre-flight only moves a launch off an account a rule has benched: no rule, no rebind, nobody is re-pooled onto another subscription without having written one.
- A candidate above roughly 90 % of its quota is skipped by the election.
- The switch writes the new account as an agent override, never on the project or global default.
- A benched account is remembered in memory only: restarting the app clears the bench.
- Providers with one gauge per machine rather than per account (Cursor, Antigravity) cannot be covered by a switch rule.
- An agent running on an SSH server (see Remote SSH Offload) can be moved too, since 2026-10-26 for Claude Code: only to an account that has its server token on this computer (Settings > Multiple accounts > Claude, Long-lived token), never to the CLI's own login, which on a server is the server's login. The conversation resumes on the server. A connection with Copy the agents' accounts and secrets to this host unticked moves nobody.
Common questions
- I had the old switch on, what happened to it? It became rules: for each provider with gauges and a spare account, "Keep working when an account runs out (session)" and "(week)" rules at 99 %, already enabled. Nothing to do.
- Does the agent lose the conversation? Not on Claude or Codex: the same session resumes on the new account. Grok relaunches instead.
- Could it burn my second subscription by mistake? The rule reads measured gauges, never prose, and the election skips accounts above ~90 %. Exclude any account with Never used as backup.
- Everything is out of quota, what happens? The agent stops; the rule's own notification says it acted, and the usage panel shows the benched accounts.
- Is this against the providers' terms? AgentsRoom uses subscriptions you own and are signed in to, through each CLI's documented account isolation; it does not create accounts or share credentials.
- My rule moved nothing: the agent stopped, or came back on the same account. Fixed on 2026-10-10 (reported by a user, Codex rule at 89 %). The rule now records the incoming account on the agent before relaunching it, then hands it over like a manual account change. Before, three things could go wrong: under 90 % the fresh usage reading lifted the bench at once and the agent restarted on the watched account; above, a Codex conversation was copied to the old account and could not be found on the new one; and the tab could freeze on a terminated process. The benched account now stays out until its gauge drops below the rule's own threshold (capped at 90 %).
- The agent was moved but sits idle until I type "continue". Fixed on 2026-11-12 (reported by a user with four Claude accounts). Right after the relaunch, the instruction to continue could be written into the terminal that had just been closed, so the resumed agent never received it. It now waits for the new terminal only. If the instruction still cannot be sent (the resumed session is not ready after 90 seconds, or the relaunched CLI did not start), the agent's console and a notification say so, with the reason: send the agent a message to resume.
Related
- Quota Rules: the rules that trigger the switch, and their other actions.
- Multiple Accounts: adding the accounts the switch chooses from.
- Claude Code Token Usage: the usage panel where the quota bars and rules live.
- Scheduled Tasks: the unattended runs that benefit most.