Claude accounts and usage
draftAgents run on the Claude accounts your runners hold. Each runner stores the tokens of up to four accounts (Runners); Pitwall shows how much of each is left, and chooses which one every step runs on.
Claude credentials stay on the runner. The server never sees a token: it knows each account by its email and a hash of each token, and the limits the runners report.
Usage rings
Section titled “Usage rings”Usage, at the bottom of the sidebar (the chip beside “Pitwall” on a phone), has one circle per account:
| Ring | Window |
|---|---|
| Outer | The weekly limit |
| Inner | The 5-hour window |
Each turns amber from 70 % and red from 90 %. Hover for the figures and when they reset; click for the pace, the runners holding the account, what is using it now, Rename and Refresh.
The figures move with every job on the account. Refresh measures it now, with a one-word request on a runner holding it: it takes under a minute, spends a little of the account, and opens a 5-hour window if none is open.
Using several accounts
Section titled “Using several accounts”Your settings → Claude accounts has a card per account, by email: its rings, the runners holding its token, a switch to turn it off, and Keep below thresholds for its 5-hour and weekly windows.
How Pitwall chooses, for each step:
| Strategy | Spends |
|---|---|
| Expiring first (default) | The account whose weekly window resets soonest, since its unused quota is lost first |
| Fixed order | The first account in the cards’ order. Drag a card to reorder |
An account is chosen only when it is on, held by the runner, not limited and under both its Keep below thresholds. The step in flight finishes on its account.
When a step hits a limit, it continues at once on another free account of the same runner, in the same session. With none free, it pauses, and the ticket and Runners say until when; it resumes on its own when an account frees up. A pause is never a failure: it spends no attempt.
The email an account is stored under is trusted, never verified: a token stored under the wrong email cannot be detected.
Kick-off
Section titled “Kick-off”Kick-off, on an account’s card: a time and days, in your time zone. At that time a runner holding the account sends a one-word request, which opens its 5-hour window, so it resets sooner. Offset the times across accounts. With no runner online, the card says “missed at” and it tries again the next day.
Usage schedule
Section titled “Usage schedule”Your settings → Usage schedule keeps the rings fresh without clicking:
- your time zone, taken from the browser until you choose one;
- your working hours;
- how often to refresh.
Turn auto-refresh on for today from the refresh button beside Usage, or have it turn itself on on the days you choose. Each refresh spends a one-word request per account, only inside your working hours; an account busy with a job is read from that job instead. It also catches usage spent outside Pitwall.