harnsy Max
See the limit before you hit it.
Usage shows every 5-hour and weekly limit of your logins with a forecast to the reset, the history of each limit, and what your agents spent. It’s in every harnsy build; a harnsy Max key turns it on.
Each login: subscriptions from Connections and each harness’s own login. The bar is used now; the pale part is the forecast to the reset; the thin mark is an even pace.
Personal · week 31% now, about 48% by the reset
Switch a project’s subscriptionLimits
Every limit in sight.
For each login, the 5-hour and the weekly window as bars: the bar is what you used, the pale part is the forecast to the reset, a thin mark is an even pace, and the reset time is beside it.
A verdict for each.
Enough, tight, or runs out at a time. It also says when a limit is used up until a time, when there is no fresh reading, when it reset since the last reading, or when there are too few readings.
How the forecast works.
It carries on the recent pace: the last hour for the 5-hour window, the last day for the week, and the whole window when there are fewer than three readings in that span (it needs three readings over at least five minutes). “Tight” starts at 90%, “runs out” at 100%. It is an estimate, not a promise.
Two logins, one subscription.
Mark a connection “Same subscription as” another and the two count as one account.
Why a limit is missing.
When the limits of a Claude login cannot be shown, a notice says why instead of leaving an empty bar.
Spend
Codex input and cache reads, separately.
Codex input tokens and cache reads are counted separately in the spend table.
A way out.
When a login runs tight or out, Usage suggests another subscription to move a project to, with “X% now, about Y% by the reset”, and a link to switch it in Connections.
The history of every limit.
Charts of the limit windows over the last 24 hours or 7 days, the limit dashed. History starts when you install this version; nothing is filled in backwards.
Where the tokens go.
Spend for today, 7 or 30 days, grouped by project, team, role, agent, login, harness or day: cost, then input, cache write, cache read and output tokens, then sessions, with a total. Cost is the harness’s own figure at API prices, not a bill.
Which agent eats the week.
Group the spend by agent or project to see who uses most, before the weekly limit is gone.
A daily budget (experimental).
Off until you switch it on. It shows how much of each weekly limit may go today so the limit lasts to the reset, as a “today” bar under each weekly bar. Leads can read it before they hand out heavy work.
Where it comes from
Taken from your machine.
The numbers are read once a minute on your machine and stay there. Claude Code: its own status-line snapshot for the limits and cost, and the session transcripts for tokens. Codex: the limit windows and token totals in its session files. OpenCode: cost and tokens per message.
What the agents spent, from their sessions’ running totals. History starts when this version was installed.
| project | Cost | Input | Cache write | Cache read | Output | Sessions |
|---|---|---|---|---|---|---|
| acme-shop | $132 | 1.2M | 3.4M | 41.8M | 610k | 38 |
| acme-api | $58.40 | 540k | 1.5M | 17.2M | 260k | 21 |
| docs-site | $12.10 | 120k | 330k | 3.9M | 70k | 9 |
| no project | $1.85 | 18k | 40k | 610k | 9k | 3 |
| Total | $204 | 1.88M | 5.27M | 63.5M | 949k | 71 |
Cost is the harness’s own figure at API prices, not a bill; subscriptions report it too. Codex reports tokens only.
What the agents spent, from their sessions’ running totals. History starts when this version was installed.
| agent | Cost | Input | Cache write | Cache read | Output | Sessions |
|---|---|---|---|---|---|---|
| acme-shop-backend | $61.40 | 480k | 1.4M | 18.2M | 260k | 14 |
| acme-shop-lead | $34.20 | 260k | 700k | 9.8M | 140k | 11 |
| acme-shop-frontend | $22.75 | 190k | 520k | 6.1M | 98k | 8 |
| acme-shop-tester | — | 310k | — | 4.2M | 120k | 6 |
| acme-shop-reviewer | $13.85 | 120k | 310k | 3.6M | 64k | 5 |
| Total | ≥ $132 | 1.36M | 2.93M | 41.9M | 682k | 44 |
Cost is the harness’s own figure at API prices, not a bill; subscriptions report it too. Codex reports tokens only. Some sessions report tokens only (Codex): the sum is partial.
Each login: subscriptions from Connections and each harness’s own login. The bar is used now; the pale part is the forecast to the reset; the thin mark is an even pace.
A key turns it on.
Without a key, Usage shows a short note about harnsy Max instead. Add a harnsy Max key on the License page to turn it on.
Limits, honestly
- Codex reports tokens only, no money, so sums that include Codex sessions are partial.
- OpenCode reports no limit windows: it has spend, but no limit bars and no weekly budget.
- Cost is counted at API prices; what a subscription really costs you is set by its vendor.
- A forecast needs a few readings: a new login shows “too few readings” at first.
Your first team is one prompt away.
Installing takes one sentence to your agent. To open agents for you, harnsy drives a terminal: tmux on Linux and macOS, its own terminal host on Windows.
Install harnsy following https://harnsy.dev/llms.txtQuestions
What's in harnsy, and what's in harnsy Max?
harnsy: one project, up to 10 agents at once, one machine. harnsy Max is the same build with a key: the key sets the numbers of projects and agents, several machines as one team, several subscriptions and their usage.