New

Agent time: record it, review it, accept it at an agent rate

Agent time, free on every plan, records how long your coding agents worked, keeps it in a pending list until you accept it, and bills it at an agent rate on its own invoice lines, apart from your own hours.

Agent time, free on every plan, records how long a coding agent worked on a project, for the person who launched it. An admin switches it on under Settings → Add-ons; until then nothing is recorded.

Agent time is the sum of the agent's turns, from a prompt being submitted to the agent stopping. Time between turns, and time spent waiting on a permission prompt, is not counted.

Review it on your timesheet. Recorded sessions appear in a pending list on your own timesheet's day view, with the project and task, the branch, a one-line summary and the time. Accept a session, change its project or task and then accept, discard it, or accept the whole day. Accepting makes one time entry for the exact time, marked as agent time. It works in a week you have already submitted.

Agent time has its own rates. An admin sets what agent time bills at and costs under Settings → Agent time: a rate for the workspace, with overrides for a client, a project or one agent host, and the option to track agent time without billing it. The rate is fixed on the entry at the moment it is accepted, so a later change never reprices it. With no rate that applies, agent time cannot be accepted, and it never takes the person's own rate.

Accepted agent time is not counted as the person's time. It is listed on their timesheet marked as agent time, beside their day and week totals and never in them, and it is left out of utilization, capacity, reminders and the weekly submit and approve flow. It does count toward the work: project budgets, profitability, uninvoiced time and invoices include it.

On an invoice, agent time has its own lines. Whichever way the invoice is grouped, agent time is on lines labeled "(agent time)", apart from the person's. Each of those lines is rounded once, on its total, to the workspace's rounding step: ten four-minute sessions are forty minutes before rounding, not ten rounded sessions. Agent time that is still pending, or marked not billable, is never on an invoice.

One report, in totals. The Agent work report shows, per person, accepted agent hours by project, the most sessions run at the same moment, the agent's own estimate of the work by hand beside the time it took, and an estimated token cost. An admin sees everybody, a manager their reports, anybody else themselves. What a session was stays with the person who ran it. The report is opened from the pending list or the Approvals page; it is not in the report tabs.

Token cost is an estimate. It prices the tokens a session reported at list price on the day you look, using prices an admin can change under Settings → Agent time. It is not what anybody was charged and is never on an invoice. A model with no price shows "no price set" and a session that sent no token counts shows "not captured"; neither is shown as zero.

The assistant can list and accept your own pending agent time, give the report, and, for an admin, list and set agent rates and model prices. Setting and accepting need a connection that acts as a person: a read-only organization key can read but not change anything.

An admin can turn on auto-accept. It is off by default. When on, agent time from a repository mapped by a workspace rule is accepted for the person once the day has ended in the workspace's time zone, and the entry is marked as accepted automatically. It never accepts a session mapped by a file in the repository, one with no agent rate, one on a project the person may not log time to, or one they discarded. Discarded agent time is deleted after 90 days.

Agent time is measured, so it cannot be raised. An accepted entry can be reduced, moved (which re-prices it) or deleted, and cannot be made longer than the agent measured.

What this does not do yet:

  • Managers do not see what is pending. On the Approvals page they see how many sessions each person has waiting and how much time, and nothing about what the sessions were.
  • Claude Code and the Codex CLI only. Agents that run in the cloud are not supported.
  • No packaged installer. The plugin is loaded from a local copy of its folder.
  • No summary of a session is recorded yet, so a session is named by its agent and branch.

Only metadata is recorded: the repository, the branch, the model, token counts and the timings. Prompts, file contents and diffs are never recorded.

Since then:

  • Auto-accept is on by default since 5 October, unless an admin turns it off, and setup is one page under Settings → Agent time → Setup.
  • Cursor is supported as well as Claude Code and the Codex CLI, since 6 November.
  • The plugins are published and install with one command, since 5 November, so nobody loads one from a local copy.
  • Agents that run in the cloud were not supported when this was written. Later entries say what has changed.

← Everything that has changed

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