Can Codus switch accounts automatically when usage runs low?

Yes. Open a provider's usage panel, then Switch status to see Account switching. Switch accounts before usage runs out enables the check; the default threshold is 95 percent. Codus checks fresh usage in the background and chooses an eligible account. Running responses finish before switching.

From Codus 0.2.210 the main Brain supervises usage. Every 5 minutes Codus checks each Claude and Codex account that a quadrant or Brain is using. Five points before the Check at percentage (90 percent by default) the main Brain's chat warns you, on your phone too: which account, which limit, when it resets, which terminals use it and which account they will move to. At the Check at percentage Codus moves each of those terminals to the signed-in account with the most room and says so in that chat. A terminal that is working moves when its current reply ends, keeps its conversation and is told to carry on. When no other account has room, the chat says when one frees up and suggests adding another account.

Background recovery requires Codus 0.2.186 or later. Codus 0.2.185 and earlier delegate these decisions to Brain 1; older versions call the option Let Brain 1 handle high usage.

Before you start

Have another signed-in account with available usage. Account switching and Claude/Codex handoffs are allowed by default, and Codus prefers a spare account on the same provider before it hands a session to the other provider. Moving accounts does not remove the provider's limits or purchase more usage.

Check or change the settings

1. Click Claude or Codex in the status bar, then Switch status.
2. Check Automatic switching and its On, Off or Paused status.
3. Expand Switching settings. Allow agents to change accounts permits account moves; Allow switching between Claude and Codex separately permits provider handoffs.
4. Set Check at to a whole percentage from 1 to 99 and click Save threshold.
5. Decide whether to enable Allow automatic changes to pinned accounts. Leave it off to preserve those account assignments.

A choice you save here is kept across updates. Codus only turns these on by itself for settings that were never saved.

Keep a terminal on its account

Tell the main Brain, for example "don't switch Q3 today" or "leave [email protected] alone until tomorrow". It stops the supervisor from moving that terminal, or every terminal on that account, for the time you give. You still get the warnings. A 5-hour limit that resets within the hour is waited out rather than switched away from.

If nothing moves

In Codus 0.2.186 or later, Brain 1 can be busy, stopped or out of usage: routine recovery runs in Codus itself. The desktop must remain open. Each affected terminal still waits for its own response to finish.

Expand Recent activity, then View details on the affected check. Missing spare accounts, unconfirmed usage, permissions or pinned assignments can leave terminals unchanged. Retry usage check is offered when a check needs attention; Codus also rechecks automatically, with a delay between checks and after recent switches. A cancelled terminal stays excluded for that usage warning, including after an app restart; a new usage window or an explicit retry can make it eligible again. A model-specific usage window does not necessarily mean every model on the account is exhausted.

In Codus 0.2.209 and earlier, an agent showing "You've hit your weekly limit" (or a per-model limit such as Opus) could not be switched: Codus did not recognise those messages and kept the agent where it was. Update to 0.2.210 or later. Until then, switch it yourself: click Claude in the status bar, then Switch status. On that agent's row choose Switch account…, pick an account and confirm with Switch anyway.

In Codus 0.2.210, moving an agent with a very long conversation could fail with "did not confirm its native conversation (oversized-record)", and Codus put it back on its previous account. Switching it by hand failed the same way. Update to 0.2.211 or later and the move completes.

In Codus 0.2.211, the same kind of move could still fail with "did not confirm its native conversation (transcript-changed)" when the agent started working as soon as it reopened, for example because a message was waiting for it. Update to 0.2.212 or later.

In 0.2.188 or later, pending warnings share one automatic usage check, with at least three minutes between these checks. That delay survives an app restart. Warnings for a previous account or an expired usage window are closed automatically. Stopped terminals do not trigger recovery checks.

Usage refresh delayed means the provider has temporarily limited requests for usage figures. For Claude, Codus waits until that account's saved retry time before checking it again, including after an app restart. The label alone does not mean the account has used all its allowance. Sign-in required and Usage out of date describe separate problems reading the account's login or current usage.

You never have to wait for the warning to clear. Switching a warned terminal yourself, or asking the Brain to switch it to a named account, goes ahead at the next safe prompt and settles the warning for that terminal. The only switch that waits is one Codus is already carrying out on that same terminal.

How do I know it worked?

From Codus 0.2.210 the main Brain's chat says when a terminal moved, for example "Q3 now runs on" and the new account. Recent activity records the check and terminals left unchanged. The terminal list confirms successful moves as Verified. A warning, an On label or available spare usage alone does not prove a switch happened or guarantee uninterrupted work.

Stopped terminals are not launched just to apply an account choice. Account saved means the choice will apply when that terminal starts. Confirming account means it has started but Codus is waiting for its session receipt; it becomes Verified automatically after confirmation. Missing identity or conversation evidence can still prevent a safe switch.

In Codus 0.2.186 or later, Account ready identifies a confirmed fresh launch on the selected account before its first message. Codus does not require a conversation receipt for a terminal it can prove has never had a conversation. Drafts keep that switch waiting; unknown or previously used conversations still require preservation evidence.