routing

Routing runs across clausona accounts

clausona keeps several Claude Code and Codex accounts on one machine. A route is a named group of those accounts and a rule for picking one of them by how much of its plan quota is used. clausona run --route <name> starts the tool on the account the rule picks right now. (csn is an alias for clausona that only the user's interactive shell has. Run clausona.)

Run clausona route --help once before anything else. It lists every command, option and exit code of the installed version. Where it differs from this skill, it wins.

clausona route with no arguments opens the Routes screen, a TUI meant for a person at a terminal. Do not run it; use the subcommands below. (In a shell without a terminal it only prints the help.) A user who would rather look through routes on that screen can run it themselves.

What decides the pick

• An account's usage is the higher of its 5H and 7D windows: 0% 5H with 99% 7D is 99%. That number, and nothing else, is ranked and shown.
• When the tool's arguments name a model (claude --model opus, codex -m gpt-5.3-codex-spark, also after exec), the account's limit on that model joins the max: Claude's is weekly, and a Codex one can have a 5-hour and a weekly window, of which the higher counts (named in the note and usage.window as GPT-5.3-Codex-Spark 5H or … 7D). A model falls under a limit when the limit's name (Opus, GPT-5.3-Codex-Spark) is a word of the model's name, in any case: opus, claude-opus-4-5, opus[1m] fall under Opus; gpt-5.3-codex does not fall under GPT-5.3-Codex-Spark. A run that names no model counts no model's limit, even if the account's default model has one: pass --model when the work needs a model with its own limit. -c model=…, a Codex config profile and opusplan are not read.
• clausona stops at the first stage that finds someone:
  1. pool: from members under maxUsage (default 80), chosen by the strategy.
  2. fallback: the first fallback member, in listed order, under maxUsage.
  3. overflow: every member is at maxUsage or over it, so the one with the most left (lowest usage) is taken, pool or fallback, at 90% or 99% alike.
  4. nobody: every member is at 100% or skipped. Nothing is launched, exit code 75. With --wait, it waits for the soonest reset instead and starts again at 1 (see Waiting).
• Strategies: round-robin (default; the account picked longest ago, a never-picked one first), headroom (lowest usage), expiring (lowest usage among accounts whose weekly limit resets within 24 hours; with none, as headroom).
• Signed-out, expired and unreadable accounts are skipped at every stage, and so is one whose stored sign-in is another account's.
• An API profile in a route (named exactly; no pattern matches one) is ranked by its spend as a share of its limit: a clausona budget (clausona route budget), else the limit set on its provider key. One with no limit, whose provider reports no spend, or whose spend could not be read is skipped. It is billed per use.
• Resumed runs (-c/--continue, -r/--resume, --from-pr, codex resume or fork) use only accounts that share sessions: the primary account and profiles with merged sessions. If none of them can take it, the account that holds the session has to be run by name.