Time Trakkr for Codex

Time Trakkr connects to the Codex CLI 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

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 codex execBoth ways of running the Codex 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 installs the plugin once: codex plugin marketplace add Time-Trakkr/agent-plugins && codex plugin add timetrakkr@timetrakkr.
  5. Start Codex and trust the plugin's hooks with /hooks. Codex does not run a plugin's hooks until you have.
  6. The first session in a connected repository opens your browser. Sign in, pick the workspace and press Allow access.

What it won’t do

  • Record Codex cloud tasks, which run where the plugin is not.
  • Record the Codex IDE extension, which does not load plugins.
  • Leave out time waiting for a permission prompt. Codex does not report it reliably, so it is counted.
  • Read or change your time entries. Its sign-in can only report agent time and read repository rules.
  • Bill agent time at the person's own rate.

Questions about Codex

Which parts of Codex are supported?

The Codex CLI, interactive and codex exec. Installing it as a Codex plugin has not been tested end to end; what was tested is its hooks loaded into a project.

Can an admin require the plugin?

Yes, with the Installed policy in the ChatGPT admin. Codex requirements.toml cannot require a plugin.

Does Codex send token counts?

When they can be read. Token cost is always an estimate at list price and never appears on an invoice.

What about Cursor?

There is a Cursor plugin, but it has never been run against a real Cursor session. Treat Cursor as not supported until someone has checked that time arrives.

Every integration →

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