Coding agents now do part of the billable work, and somebody has to answer for it on the invoice. Time Trakkr records how long an AI coding agent works in each client repository, as agent time for the person who ran it, at an agent rate an admin sets, and bills it on invoice lines of its own.
A session is recorded only when its repository is mapped to a project and task, by an admin’s rule or by a .timetrakkr.json file in the repository. Agent time is the sum of the agent’s turns, from the prompt to the moment the agent stops. The time between turns, and time spent waiting for someone to answer a permission prompt, are not counted.
Each session waits in the person’s pending list, and pending time is never on a report or an invoice. It is accepted by the person, or automatically once the day ends when an admin’s rule mapped the repository, unless an admin turns automatic accepting off. Sessions mapped by a .timetrakkr.json file, or with no agent rate, always wait for the person.
An entry accepted automatically is marked so. Like any agent entry, it can be reduced, moved or deleted until it is invoiced.
An admin sets an hourly bill rate and cost rate for agent time: for the whole workspace, then for a client or a project where the agreement differs, and optionally for one agent host. A rule can also track agent time without ever billing it. Rates are fixed when the time is accepted.
With no rate that applies, agent time cannot be accepted. It is never billed or costed at the person’s own rate instead.
Billable agent time is on invoice lines labeled (agent time), after the person’s own lines, whichever grouping you choose. It counts toward project budgets, profitability and uninvoiced time, and stays out of the person’s own hours and utilization. The Agent work report shows accepted agent hours per person and project, with an estimated token cost that is never on an invoice.
An agent that runs with nobody at the keyboard, such as a cloud, CI or third-party agent, can be an agent member: a member of the workspace in its own right, with its own token, logging its own time through the REST API or MCP. Its hours appear under its own name on timesheets, reports and invoices. Agent members are free and never count as seats.
An agent can also sign up for a workspace of its own, through the API, with no person involved.
Yes, for Claude Code and the Codex CLI. Each session in a repository mapped to a client project is recorded as agent time for the person who ran it, and billed at an agent rate on its own invoice lines.
No. It is billed and costed at an agent rate an admin sets, fixed when the time is accepted. If no agent rate applies, the time cannot be accepted, and it is never billed at the person’s own rate instead.
Not necessarily. Agent time from a repository an admin mapped is accepted automatically once the day ends, unless an admin turns that off. Pending time is never invoiced, and accepted time can still be reduced or deleted until it is invoiced.
No. It is shown beside the person’s own hours, not in them, and is left out of utilization, capacity and timesheet approval. It does count toward project budgets, profitability and invoices.
None of it. The plugin never sends prompts, file contents or diffs, and sends nothing at all from a repository that is not mapped to a project.
Yes, as an agent member. It is free and never counts as a seat. It gets its own token, logs its own time through the REST API or MCP, and appears under its own name on timesheets, reports and invoices, labeled Agent. It has no email address and cannot sign in to the web app.
Yes. An agent can sign up through the API by solving a short proof-of-work challenge. That creates a workspace the agent owns and returns an owner token and a recovery key, with no person involved.
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