Features

Everything it does today.

Tallyhook reads the session logs Claude Code and Codex already write and turns them into a ledger you can act on. This page lists what is built and working. What is not built is at the bottom, by name.

Attribution

The part no vendor dashboard does: tying a session to the thing it was for.

Cost per repo

Every session is tagged with its git remote, normalised to host/org/repo, so the same repo checked out on two laptops is one line rather than two.

Repo groups

Put repos in a group once, by client, service or squad. Every past and future session from that repo follows, so mapping is a one-time job, not upkeep.

Per developer and per model

The same totals broken down by who ran the session and which model answered, for any date range.

Honest pricing

List prices per model, with cache reads, 5-minute cache writes at 1.25x input and 1-hour writes at 2x priced separately. A model with no known price is reported as unpriced rather than guessed.

Read more

Watching what it costs

Finding the expensive thing the same day, rather than on next month's statement.

Cost-spike alerts

Set a dollar threshold and every workspace owner gets one email the moment a single session crosses it.

Monthly budgets

A budget per group, with an email at 80% and again at 100%, so a retainer or a team's allowance never overruns quietly.

Webhook alerts

Both alerts can POST to a URL as well as emailing. Verified end to end with Discord, where a real alert renders as plain text with its detail lines intact. The same payload also carries the field Slack documents for incoming webhooks, but we have not watched one arrive there, so we are not claiming it. Saving a URL sends a test immediately.

Month-end forecast

A plain projection from the spend so far, so the renewal question has a number behind it instead of a feeling.

Biggest changes

Which group or repo moved most against the previous period, in dollars, so an acceleration is visible before it compounds.

8-week trend

Weekly cost per group over the last eight complete weeks. The current, part-finished week is excluded rather than compared against full ones.

Cost per active developer

Total spend over the developers who actually ran sessions, so growth in headcount and growth in cost per head are told apart.

Getting the money back out

For teams who bill this usage on, and for teams who only have to explain it.

Invoices with markup

A printable billing document with your markup applied, itemised by developer and by model. Workspaces set to internal mode get the same document as a cost report, with no markup.

Client report links

A read-only link showing one group's numbers and nothing else in the workspace. No login for whoever you send it to.

CSV export

The same figures as raw rows, for a spreadsheet or an accounting tool. Cell values are guarded against formula injection.

A rate per client

One markup for the workspace, or a different one for a client who negotiated it. A document covering several clients prices each line at its own rate and says so rather than pretending one rate applies.

Real invoice details

Your billing name and address, a tax or VAT registration, and payment terms, printed on the document itself.

Billing timezone

Months begin and end on your clock, not the server's. Without it a session run at 8pm on the last day of the month lands in the next month's invoice, because it is already tomorrow in UTC.

What makes it safe to install

The collector runs on your developers' machines, so this part is not a footnote.

Metadata only

Token counts, timings, repo and branch, developer identity, turn and tool-call counts, edited file paths. Transcripts, code, diffs, tool output and environment variables never leave the machine.

Read more

Open-source collector

One dependency-free file, MIT licensed, on GitHub and npm. Your security reviewer can read exactly what it sends instead of taking our word for it.

Read more

A free local report, and free client billing

npx tallyhook prints cost per repo for one machine with no account and nothing uploaded, and npx tallyhook --by client rolls those repos up into the clients you bill with your markup, so the tool can be judged before anyone signs up. Paste its output into a shareable card if you want to post what a project cost.

Read more

An MCP server

npx tallyhook mcp lets Claude Code, or any MCP client, answer cost questions about its own work: spend by repo, by model, the sessions that cost the most, and this period against the one before. Local and account-free like the report, and it reads the same files.

GitHub sign-in only

No password of yours for us to store or lose. We read your profile and primary email, nothing else.

Price overrides

Negotiated rates or a model we do not know yet: set the price and every past session reprices.

Not built yet

Listed because you would find out anyway, and better from us than after installing. Say which one you need and it moves up the list.

Cursor
It does not write per-request token usage to a local log, so it needs a proxy. That is a bigger trust ask, and it is not built.
Native Windows
macOS and Linux today. WSL should work because it is Linux, but it is untested.
SSO
GitHub OAuth only.