Claude Code time tracking, per client and project

Time Trakkr records how long Claude Code works in each of your client repositories, as agent time for the developer who ran it, against the project that repository is mapped to. It is billed at an agent rate you set, on its own invoice lines.

How it works

  1. An admin sets it up once. Enable Agent time under Settings → Add-ons and set a default agent rate. Nothing is recorded until there is one.
  2. Repositories are mapped to projects. Pick each repository, from GitHub or by its address, and the project and task its time belongs to. A repository nobody has mapped sends nothing.
  3. Each developer installs the plugin. You need Node 20 or later.
    claude plugin marketplace add Time-Trakkr/agent-plugins && claude plugin install timetrakkr@timetrakkr
    The first session in a connected repository opens your browser to sign in: pick the workspace and press Allow access. Inside a session, /timetrakkr:status says what the current directory is tracked to and why.
  4. Sessions become agent time. Each session waits in the developer’s pending list on their timesheet. It is accepted by them, or automatically once the day ends unless an admin turns that off, and can be reduced or deleted until it is invoiced.
  5. Accepted time is billed as agent time. It is billed at the agent rate, on invoice lines labeled (agent time), and counts toward budgets and profitability. It stays out of the developer’s own hours and utilization.

How Claude Code is measured

The Agent work report shows accepted agent hours per person and project, with the estimated token cost beside them.

What it will not do

  • Claude Code cloud sessions. The plugin and your sign-in are on your own machine, not the cloud one, so nothing is recorded for them.
  • It never sends your prompts, the contents of any file, or diffs. The service refuses a report that carries anything beyond the fields the help article lists.
  • It records nothing in a repository nobody has mapped to a project, not even the repository’s name.
  • It does not let anyone type agent time in by hand. Time you spent yourself is logged as your own time, as usual.
  • Token cost is an estimate at list price on the day you look. It is never what you were charged and never on an invoice.

Questions about Claude Code time tracking

Can Claude Code time be tracked per client?

Yes. An admin maps each repository to a project and task, and the project belongs to a client. Every Claude Code session in that repository is recorded against it, as agent time for the developer who ran it.

Is Claude Code time counted as the developer’s own hours?

No. It is credited to the developer who launched Claude Code, on its own row on their timesheet, but it is kept out of their own hours, utilization and capacity. It does count toward project budgets, profitability and invoices.

What rate is Claude Code time billed at?

An agent rate an admin sets for the workspace, a client or a project, with a separate cost rate. A rule can be limited to one agent host. Claude Code time is never billed at the developer’s own rate.

Does Time Trakkr see my Claude Code prompts or code?

No. The plugin sends the session’s times, repository address and branch, model and token counts. Prompts, file contents and diffs are never sent.

Does it work with Claude Code in the cloud?

No. Only Claude Code running on your own machine is supported. Claude Code cloud sessions record nothing, because the plugin and your sign-in are not on that machine.

Read the details

The hours, the invoices, and what they earned

Free for unlimited people. One paid plan, $10 per member per month, when you want HR, scheduling, timesheet approvals, scheduled backups, email from your own domain and scheduled reports.

Start free