What Clocktopus is

Software is no longer delivered by people alone. A feature might be two hours of your attention and forty minutes of an agent running against your repository, and only one of those has ever shown up on a timesheet.

Clocktopus is the ledger for both sides. It reads the evidence work leaves behind — commits, pull request reviews, agent sessions — prices it, and puts what was delivered next to what it cost to deliver. That is what lets you quote from numbers, staff from numbers, and know which projects to stop.

These pages explain how the machine works and how to set it up. The features pages cover what it does for a developer, a delivery manager, or an owner.

Two kinds of worker, one ledger

People are tracked from git activity. Push code and the time between your commits becomes entries against the project that owns the repository. There is no timer to start and no app to switch to. Time that leaves no git trace — a call, a review outside the tooling, an afternoon of pairing — you add by hand in a weekly grid.

Agents are tracked from their own telemetry. A Claude Code session reports what it cost and how long it ran; session hooks report which repository it ran in. That spend lands against the same project, and the same ticket, as the commits it produced.

The rule that keeps it honest

Hours from the two sources are never added together.

One person steering three agents for an hour is one human hour and three agent hours. Four hours describes nothing, so no screen in Clocktopus will produce that number.

Money is different. Once your hours are priced at your cost rate, that figure and agent spend are both dollars, and their sum is what delivery actually cost. This is why rates exist in the product: without a price, human effort and machine effort have no common unit.

What it costs you to run

You do this	Clocktopus does this
Commit and push as you already do	Measures the gap between commits and files entries
Tell it when your day starts, if your hours are irregular	Uses your clock-in instead of your default hours
Point your agents at it once	Records their runtime and spend beside your hours
Set rates on job roles	Prices every hour, and every project's margin

What it is not

It is not a timer, and it is not surveillance. Clocktopus never reads your code, your prompts, or your agent transcripts — the AI agents page lists exactly what is collected and what is not.

It is also not an issue tracker. Tickets come from your commit messages (conventional-commit scopes), so there is no integration to configure and nothing to keep in sync.

Where to go next

• Quickstart — from nothing to your first entries.
• Automatic tracking — how an entry is actually calculated, and what happens when the evidence is messy.
• AI agents — what agent spend is, and how it reaches a project.
• Rates and project budgets — turning hours into revenue, cost and margin.
• Reports and insights — reading all of it back.