
The terminal shows one running total. A dashboard shows where the money actually goes: per project, per git branch, per model, per developer, over time, with budgets and a re-priced history. Goei is that dashboard, fed by an open-source CLI that reads the logs Claude Code already writes. No API keys.
Every dollar attributed to where it came from, so the cost of a feature, a runaway agent, or a heavy model is legible instead of a single monthly total.
Set a budget scoped to a project, a branch, or the whole team, and get alerted before it is blown. Pair with budgetclaw for hard SIGTERM caps on a runaway session.
Every past month valued at the API rates that were live on the days it ran, from the open AI Price Index, so an old month reads true, not re-scored at today's rate.
See what your usage is worth at list rates against your Pro or Max price, so you know whether the plan is a bargain. Try it first with the calculator.
LOCAL usage value at list API rates and BILLED provider charges are always labeled separately and never added together.
Goei's dashboard is fed by the open-source budgetclaw CLI, which reads the session logs Claude Code already writes and pushes daily dollar-and-token rollups with a device token you can revoke. No API keys, no prompts, nothing in the request path. It works on Claude Pro and Max, where no billing API exists.
Teams billed through a provider API can also connect a billing key for the authoritative billed figure, encrypted at rest. That billed number is always shown next to, never added to, the local list-rate value.
If you already run ccusage, you already have everything the dashboard reads. Install the open-source CLI and push your history.
Prefer to look before you sign up? Open the live demo, no account needed.
It is a place to see what Claude Code is costing you over time, broken down by project, git branch, model, and (for a team) by developer, instead of a single running total in the terminal. Goei is a hosted one: each machine runs the open-source budgetclaw CLI, which reads the session logs Claude Code already writes and pushes daily dollar-and-token rollups, and Goei charts them, dedupes across machines, and keeps a re-priced history.
Not for Claude Code usage on Pro or Max, which have no billing API. Goei's local track reads the same ~/.claude session logs ccusage reads, through budgetclaw, and sends only daily rollups with a revocable device token. Zero keys, no prompt content, nothing in your request path. An API key is only needed for the optional billed track that reads a provider billing API directly.
Spend per project, per git branch, per model, and per developer; trends over days, weeks, and months; budgets and alerts scoped to a project, branch, or the whole team; a subscription-value card that shows what your usage is worth at list rates versus your Pro or Max price; and 12 months of history re-priced at the API rates that were live on each day, not today's rates.
Both. The local track works on Claude Pro and Max plans, where there is no billing API at all, by reading local usage logs through budgetclaw. Teams billed through the Anthropic or ElevenLabs API can additionally connect a billing key for the authoritative billed figure, which is always shown separately from the local list-rate value and never added to it.
There is a free tier that shows your recent history, and Pro is $19/month flat for up to 10 developers (not per seat), which unlocks the full team rollup and 12 months of re-priced history. The budgetclaw CLI that feeds it is free and open source.
Goei is part of RoninForge. See the full overview, how to track spend across a team, or the ccusage comparison.