Time Trakkr for Cursor

Time Trakkr connects to the Cursor CLI, cursor-agent, 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.
Interactive and cursor-agent -pBoth ways of running the Cursor CLI are recorded. 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 adds the marketplace once: cursor-agent plugin marketplace add https://github.com/Time-Trakkr/agent-plugins.
  5. Then, in cursor-agent, type /plugins, open Marketplace, pick timetrakkr and choose Install for you.
  6. Run npx @timetrakkr/cli cursor setup once, so whole turns are counted. It shows the two entries it adds to ~/.cursor/hooks.json and asks first.
  7. Sign in with /timetrakkr-login in a cursor-agent session. Pick the workspace and press Allow access.

What it won’t do

  • Count whole turns until cursor setup has been run. Before that, the Cursor CLI reports tool calls but not prompts, so a turn counts from its first tool call to its last.
  • Record the Cursor editor, which has not been checked yet, or Cursor cloud agents, which run where the plugin is not.
  • Send token counts. Token cost shows "not captured".
  • Leave out time waiting for a permission prompt. Cursor does not report it, so it is counted.
  • Bill agent time at the person's own rate.

Questions about Cursor

Which parts of Cursor are supported?

The Cursor CLI, cursor-agent, interactive and with -p. The Cursor editor has not been checked yet, and Cursor cloud agents are not supported.

What does cursor setup change?

It adds one entry each for beforeSubmitPrompt and stop to ~/.cursor/hooks.json, after showing them and asking. They do nothing themselves; they let the Cursor CLI run the plugin’s own hooks for those events, so whole turns are counted. --undo removes them.

Is this the same as connecting Cursor over MCP?

No. Over MCP, Cursor acts as you and logs your own time. The agent-time plugin records how long Cursor’s agent worked, as agent time at an agent rate.

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

Connect Cursor 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