Agent time is new, and free on every plan, for teams that use coding agents. It records how long an agent worked in one of your repositories, for the person who ran it, and turns that into time entries on the right project, priced at an agent rate rather than the person's own.
Setting it up. An admin switches it on under Settings → Add-ons, which opens a short checklist: set a default agent rate, and connect the repositories you want tracked, each one mapped to a project. Each developer then installs the plugin for Claude Code or Codex with one command, and signs in through the browser the first time a session starts.
What is counted. The time from a prompt being sent to the agent stopping, turn by turn. Time between turns, and time spent waiting for you to approve something, is not counted. Only the repository, branch, model, token counts and timings are recorded; prompts, file contents and diffs never are.
What happens to it. Agent time waits in a pending list on the person's
timesheet, where they can accept it, move it to another project or task, or
discard it. At the end of each day, agent time from a connected repository is
accepted automatically, unless an admin turns that off. Time mapped by a
.timetrakkr.json file in the repository is never accepted automatically.
People can still reduce or delete an accepted entry, and they cannot make it
longer than the agent measured.
How it is billed. Accepted agent time counts toward project budgets, profitability and invoices, on invoice lines of its own labeled "(agent time)". It is kept out of the person's own hours, utilization, reminders and weekly approval.
What it does not do: it does not record an agent in a repository that is not mapped to a project, and it records nothing until the workspace has a default agent rate.