Accounts and usage

Settings > Accounts holds every account your agents run on and shows what is left of each one. Claude and Codex each take up to ten subscription accounts. API keys and custom endpoints sit below them.

Your Warshall account is the card at the top of the tab. It is covered on the Warshall account page.

Linking an account

The Claude and Codex sections each have a Link account button and a count of the slots in use, such as 2/10. The button turns off once all ten are used.

Linking opens your browser. While it waits, the new row reads Finish signing in from the browser. Open it here. Click here to open the page again, or right-click it and pick Copy link to paste the address into another browser. The row updates by itself when the sign in finishes, so there is nothing to come back and click. The x on a row that is still linking cancels it. A sign in that fails shows a Failed tag beside the address and the reason under it.

Each account keeps its credentials in a folder of its own, so moving between accounts never asks you to sign in again. If you were already signed in to claude or codex before installing Warshall, that sign in is adopted as a linked account and left where it is. Remove the adopted row and it is not offered again.

The account row

• The logo at the left names the provider. The plan, such as MAX or FREE, sits beside the address. The line under it gives the kind, OAuth for a subscription, API key or Endpoint, and how old the usage reading is.
• The first account you link is the provider’s default account, the one runs use when nothing else picks one. Removing it passes that role to the next subscription.
• The Weekly Ceiling Limit box sits on the right of the card, before the ping button. See ceilings.
• The ping button sends one short message on the provider’s cheapest model with that account’s own credentials. This is what brings a stale sign in back to life. For a custom endpoint it asks the server for its model list instead. A failed ping shows its message under the row. A good one shows nothing.
• The x removes the account.

Subscriptions are listed highest plan first. An account whose plan is not known yet sits at the bottom. A newly linked subscription shows a loading bar where its usage will go until the first reading arrives.

API keys and endpoints

API keys takes a provider, Claude or Codex, a label and the key. Custom endpoints takes a label, the base URL of an OpenAI compatible server and an optional key. Add saves either one.

Neither kind reports usage windows, so neither shows a meter or takes a ceiling. A run on an API key is paid in money, so the money limits on the stop losses page apply to it instead of the window limits. A model on a custom endpoint runs through Warshall’s own loop. See custom endpoints.

Reading usage

A linked subscription shows one row per usage window the provider reports. Each row carries the window’s name, the percent remaining, a bar, the exact reset time with a countdown beside it, and the length of the window, such as a 5h window or a 7-day window. A window with no reset time says reset time not reported.

The line under the address says how old the reading is. Usage is read again every two minutes. Refresh usage at the top of the tab reads every account now.

The figure in each terminal’s head is how much of your whole linked subscription capacity is left, as one percent. Each plan counts by what it is worth, so a large plan moves the figure more than a small one. A paid plan is read by its shortest window, the one you run into first. A free plan is read by its longest. The figure shows a dash until a first reading arrives. Hover it for one line per plan, largest first, with all of its windows side by side.

Choosing the account a terminal runs on

Open the model picker in a terminal’s head. Under the model list are two lines of their own, Effort and Account. The Account line names the plan and the start of the address of the account this terminal runs on.

• Click Account to open the provider’s accounts beside the picker, subscriptions first, then API keys. Each shows its plan and address and a line per usage window with a bar and the time until it resets. The tick marks the one in use. Click another to switch.
• Right-click Account to step to the next account without opening the list.
• The line only appears when the model’s provider has a linked account.

While Autopilot is on, the line reads Usage Pooled and opens nothing, because Autopilot picks the account for each run.

The orchestrator’s model lists carry the same choice as a cell at the right end of each model row. Hover it for the account in full. Click it to step to the next account. See The orchestrator.

Per project defaults

A terminal you have not picked an account for follows its project’s rule. Set it in Settings > Projects under Usage Account.

The same tab has Default provider, the provider new terminals in that project open on. See Providers.

When usage cannot be read

A reading can fail because the sign in has gone stale, or because the provider’s usage service is busy or cannot be reached. Only the first says anything about your account, so Warshall does not call an account untracked straight away.

1. For four minutes the last good reading stays on screen while Warshall keeps asking. A window whose reset has passed is dropped from it rather than shown with an old figure. With no earlier reading, the row keeps its loading bar.
2. When the sign in itself failed, Warshall pings the account at two minutes and again at four.
3. If a ping succeeds, the account works, and it is never called untracked. Only its meter could not be read.
4. Otherwise, after the four minutes, the row says Usage unavailable with the reason. It keeps trying on every poll and recovers by itself.

An untracked account is left out of the terminal figure and a warning mark appears beside it, because the picture is incomplete. Its line in the hover breakdown reads untracked.

What usage feeds

• Usage autopilot sends each run to the linked account with the most usable room.
• Stop loss and ceilings stops a run that burns too much of a window, and stops all work on an account past the ceiling you set for it. A run that starts on an account with a window 90% used or more also gets a notice that it may not fit.
• Auto continue reads the spent window to know when the work can go on.
• The Most remaining rule above reads it to pick an account.