Integrations · Agents
Track Claude Code cost by ticket, person and client.
Claude Code reports through four doors: the Claude Code mod, session files read by the CLI, telemetry push and the GitHub Action. Each session becomes a token entry on a ticket, with a summary of the work.
- DoorsClaude Code mod, CLI, telemetry push, GitHub Action
- Brings inTokens, cost, model, branch and a summary per session
- Cost lands onTickets, projects and the person who answers for it
From a session to a ticket.
Start with telemetry for the whole organization. Add the mod where people want the ticket and the summary.
- 1
Push telemetry
An administrator adds the exporter to Claude Code's managed settings once. Nobody installs anything, and cost lands on projects by repository.
- 2
Add the mod
The mod records every turn and writes the summary as the session runs. It shows the cost in a band above the prompt, in the terminal and in the desktop Code tab.
- 3
Review and submit
People see their draft token entries, fix a ticket if a rule missed it, and submit their token sheet.
What leaves the machine.
A summary, never the transcript
The summary and the tag values are the only text in a token entry. Ticket keys found in prompts are the one exception, and the service drops any event that carries prompt text.
Ask Claude about cost
Ask "what did SF-1 cost this week?" in the session, and the mod answers with a report table.
Seats without a usage bill
On Claude Team, Max or Pro there is no usage bill. Usage is shown at API rates, labelled as an estimate.
In the docs
Start alone in a few minutes. Add your team when the first month closes.
No card for the free plan. Fourteen days to try the Team plan.