Integrations · Ticket systems
AI agent cost per ticket, synced from GitHub Issues.
Token Controller syncs your tickets from GitHub Issues, so every token entry can land on the issue its work belongs to.
- Connects byA GitHub API token
- Brings inTickets with titles, descriptions, parents and assignees
- SyncEvery 15 minutes, or on demand
Your tickets, as they are.
Tickets are numbers, so the key pattern names the repository with the number.
- 1
Add an API token
In the web app, open Settings, then Ticket systems, and add an API token from GitHub Issues. Nobody needs a GitHub Issues sign-in.
- 2
Map the projects
Map each GitHub Issues project to a Token Controller project. The ticket key pattern follows from it.
- 3
Let tickets sync
Tickets sync every 15 minutes, or on demand, with their titles, parents and assignees. Each ticket carries its project's tags, such as the client.
How keys become cost on tickets.
The tools never need your tickets
The Claude Code mod, the CLI and the GitHub Action find keys with the pattern alone. Token Controller checks every key against the tickets it syncs.
A new ticket is never lost
A key that has not synced yet is placed anyway, and the ticket fills in at the next sync. If it never turns up, the token entry shows in the review list.
Tickets roll up
Tickets inside tickets roll up to their parent and to the project, so a token budget can sit at any level. Whoever connects GitHub Issues answers for that data flow.
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.