Cursor CLI time tracking, per client and project
Time Trakkr records how long the Cursor CLI, cursor-agent, works in each of your client repositories, interactive or with -p, as agent time for the developer who ran it. It is billed at an agent rate you set, on its own invoice lines, and never at the developer’s own rate.
How it works
- 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.
- 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.
- Each developer installs the plugin. You need Node 20 or later.
cursor-agent plugin marketplace add https://github.com/Time-Trakkr/agent-plugins
Then start cursor-agent, type /plugins, open Marketplace, pick timetrakkr and choose Install for you, and run npx @timetrakkr/cli cursor setup once so whole turns are counted. If the browser does not open to sign you in, type /timetrakkr-login. /timetrakkr-status says what the current directory is tracked to and why. - 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.
- 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 Cursor CLI is measured
- With timetrakkr cursor setup done, a turn runs from the prompt you submit to the moment the agent stops. Agent time is the sum of the turns, so time between turns is not counted.
- Without it, the Cursor CLI tells the plugin about tool calls but not prompts, so each turn counts from its first tool call to its last. That is lower than the time the agent worked, never higher. cursor setup adds two inert entries to ~/.cursor/hooks.json, after showing them and asking.
- Time the Cursor CLI spends waiting on a permission prompt is counted, because Cursor does not report it.
- No token counts are sent, so the estimated token cost says “not captured”, never zero.
- Cursor has no way to show a line when a session starts. /timetrakkr-status shows what a session is tracked to.
The Agent work report shows accepted agent hours per person and project, with the estimated token cost beside them.
What it will not do
- The Cursor editor. It has not been checked against real sessions yet.
- Cursor cloud agents. The plugin and your sign-in are on your own machine, 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 Cursor CLI time tracking
Can Cursor CLI time be tracked per client?
Yes. An admin maps each repository to a project and task, and the project belongs to a client. Cursor CLI sessions in that repository, interactive or with -p, are recorded against it as agent time for the developer who ran them.
Why is less time recorded than the session took?
Probably because timetrakkr cursor setup has not been run. Without it, the Cursor CLI reports the agent’s tool calls to the plugin, not your prompts or the agent stopping, so each turn counts from its first tool call to its last. timetrakkr status says whether it is set up.
What rate is Cursor 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 Cursor alone. Cursor time is never billed at the developer’s own rate.
Does Time Trakkr see my Cursor prompts or code?
No. The plugin sends the session’s times, repository address and branch, and model. Prompts, file contents, diffs and your Cursor account email are never sent.
Does it work in the Cursor editor or with Cursor cloud agents?
Not yet for the editor, which has not been checked against real sessions. Cursor cloud agents run where the plugin is not installed, so nothing is recorded for them.
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