Automatic account switching at the limit
Put as many Claude Code and Codex accounts as you like in a chain. When the remaining limit drops below your threshold, or the CLI reports a limit, the agent moves to the next available account. The conversation is copied over and the agent carries on. Cursor, Gemini, Copilot and the other CLI agents have their own accounts and fallback order too.
This feature is in the Pro and Team plans. On the free plan it shows as locked; sign in with your AgentVera account and upgrade to unlock it. Compare plans
Account chains and thresholds
You set up separate chains for Claude and Codex in the app’s account switching settings. The threshold applies to what’s left of the 5-hour or weekly limit, and the chain wraps around after the last account. If “Move the conversation to the new account” is off, the switch starts a new conversation.
- A chain needs at least two accounts.
- Switching also recognizes expired or rejected logins and skips to the next working account.
- The status bar shows each account’s 5-hour and weekly usage.
Accounts of other agents
Under Settings → Accounts → Accounts of other agents you add accounts for Cursor, Gemini, Copilot, opencode, Hermes, Qwen, Droid, Kimi, Amp and the other CLI agents. In the agent window you pick the agent’s account and an ordered list of fallback accounts.
- Gemini, Copilot, Hermes, Kimi, opencode, Crush, Cline and Vibe accounts sign in with the CLI’s own sign-in, in a folder of their own; your own sign-in is left alone.
- Cursor accounts sign in with cursor-agent on a Mac; extra Amp, Goose, Qwen and Droid accounts run on API keys.
- Keys are kept encrypted and never sent to the window; Settings shows whether each account is signed in.
- At the limit, the next model of the chain is tried on the same account first, then the next account. The conversation stays the same; a model or account that hit its limit is skipped for an hour.
Where the limits come from
Limits are read from Anthropic’s usage service for Claude and from codex app-server per account for Codex. These endpoints aren’t a stable public API.
Questions
Which tools does it work with?
Claude Code and Codex use account chains. Cursor, Gemini, Copilot, opencode, Hermes, Qwen, Droid, Kimi, Amp and the other CLI agents have Settings → Accounts → Accounts of other agents, and each agent window has its own fallback order.
Is the conversation lost?
No. With moving the conversation on, its record is copied into the new account’s folder and the agent continues the same conversation.
How many accounts can I add?
Chains have no length limit; switching needs at least two accounts.
Related features
Related terms:Usage limits
Bring your agents to one desk.
Start on the free plan. Download it, add a project folder and open your first agent.
Posts on this topic
Blog- November 3, 2026Claude Code account switchers compared: auto-switch at the limitTools that move Claude Code or Codex to another account when the usage limit hits: ccam, AgentPool, ccswap, claude-swap, codex-swap and AgentVera, compared.
- November 17, 2026How to use Crush: a step-by-step guide to Charm’s coding agentHow to use Crush, Charm’s terminal coding agent: install, pick a provider or local model, approve tools, use crush run, resume sessions and set up crushrc.
- November 15, 2026How to use Cline CLI: a step-by-step guide to Cline in the terminalHow to use Cline CLI: install with npm, sign in or bring your own key, switch Plan and Act, run headless with --json, resume sessions and add rules and MCP.