harnsy Max
Out of one subscription’s limits.
Your subscriptions live in Connections, each agent runs on the one you pick, and Usage shows every 5-hour and weekly limit with a forecast. It’s in every harnsy build; a harnsy Max key turns it on.
Subscriptions
Several subscriptions on one machine.
Add your Claude, Codex and OpenCode logins and API keys as connections, including other providers behind OpenCode, such as GLM on Z.ai. harnsy keeps the secrets encrypted.
Each agent on the connection you pick.
Start an agent on a chosen connection, or pick the subscription a project’s team runs on. When one runs low, start the next agents on another.
Limits
Every limit in sight.
Usage shows each subscription’s 5-hour and weekly limits as bars: green when it holds, amber when it’s tight, red at the cap, with the time it resets.
A forecast, and a way out.
harnsy projects each limit to its reset: enough, tight, or runs out and when. It names the connections you could switch to.
Usage statistics
Where the tokens go.
Spend for today, 7 and 30 days, by project, team, role, agent, login, harness or day: tokens, sessions and cost, with a total.
Which agent eats the week.
Sort the spend by agent or project to see who uses most, before the weekly limit is gone.
The history of every limit.
A chart of each subscription’s use over the last 24 hours or 7 days, with an even-pace mark, so you see the pace, not just today’s number.
A key turns it on.
Without a key, Connections and Usage explain what they do and stay off. Add a harnsy Max key on the License page to turn them on.
Limits, honestly
- 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.
- Signing in to Codex by device code hasn’t been tried live yet.
Your first AI team is one prompt away.
Installing takes one sentence to your agent. To open agents for you, harnsy needs tmux.
Install harnsy following https://harnsy.dev/llms.txt