Time Trakkr for Claude Code

Time Trakkr connects to Claude Code through a plugin that records how long the agent worked in a connected repository, as agent time for the person who ran it.

FreeEarly release
Start free

What it does

Agent time, kept apart from yoursRecorded for the person who ran the agent, but left out of their own hours, utilization and timesheet approvals.
Billed at an agent rateAccepted agent time bills at the rate an admin sets for agents, on its own invoice lines labeled (agent time).
The repository picks the projectAn admin maps repositories to a project and task. A session anywhere else sends nothing at all.
Reviewed before it countsSessions wait in a pending list and are accepted once the day ends, unless an admin turns that off. People can still reduce or delete an entry.
Prompts and code stay putThe plugin reports how long the agent worked. Prompts, file contents and diffs are never sent.

How to set it up

  1. An admin enables Agent time under Settings → Add-ons.
  2. The admin sets a default agent rate. Until there is one, nothing is recorded.
  3. The admin connects each repository to a project and task under Settings → Agent time → Repositories.
  4. Each developer installs the plugin once: claude plugin marketplace add Time-Trakkr/agent-plugins && claude plugin install timetrakkr@timetrakkr.
  5. The first session in a connected repository opens your browser. Sign in, pick the workspace and press Allow access.

What it won’t do

  • Record Claude Code cloud sessions. The plugin runs on your own machine.
  • Record anything in a repository nobody has connected. It sends nothing there, not even the name.
  • Read or change your time entries. Its sign-in can only report agent time and read repository rules.
  • Bill agent time at the person's own rate.
  • Put token cost on an invoice. It is an estimate at list price, shown on the Agent work report.

Questions about Claude Code

Is this the same as connecting Claude Code over MCP?

No. Over MCP, Claude Code queries and logs your own time. The plugin records how long the agent itself worked, as agent time. You can use either or both.

What does the plugin send?

How long the agent worked, in which connected repository and branch, and token counts when they can be read. Prompts, file contents and diffs are never sent.

Can an admin require the plugin?

Yes, through Claude Code managed settings. Otherwise each developer installs it with one command.

Is waiting for a permission prompt counted?

Not on Claude Code. That wait is left out of agent time.

Can agent time be added by hand?

No. If your agent is not supported, log your own time as usual.

Early releaseCodexRecord how long the Codex CLI works in your repositories, as agent time at a rate you set.GitHubPick the repositories agent time is recorded in, from every repository you can reach.Early releaseTime Trakkr CLInpx @timetrakkr/cli: sign a machine in, see what a directory is tracked to, pause tracking.MCP serverPoint an MCP client such as Claude Code or Cursor straight at your workspace.
Every integration →

Connect Claude Code to your own workspace

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