What does my team actually have to do?

Commit, as they already do. Someone connects the repository once. If commit messages carry the task key in the conventional-commit scope, hours attribute themselves to the task; if they don't, that's the one habit worth adopting, and it's a habit most teams already have. Clocking in and out and wiring up agent telemetry are single commands, and both are optional.

Software Delivery Performance for Humans and Agents

See how your team ships, from task to delivery. Cycle time, rework and cost, built on the tools and agents you already use.

Start free See pricing

The dashboard: 137.03 hours across 19 active days and 305 entries, above a daily chart plotting tracked hours and agent runtime as two separate lines.

Hours worked and agent runtime, never added together

Your harness reports runtime, tokens and spend; your repo reports the commits. Both land beside your team's hours. Set up an agent or connect a repo.

From recording the work to improving it.

Manual tracking captures people, badly, and stops there. Clocktopus records the whole of delivery as it happens. Every hour from a commit, every agent's runtime and spend from your own harness, all of it priced. What you get back is not only a timesheet. It is the numbers you run the team on.

See it in action

What can you achieve with Clocktopus?

The same ledger answers to three different people. Here is what each of them gets out of it.

For developers

Hand your agent the next task and let it run

start-work takes the goal's next task, names the branch after it and ties the session to it. Your agent carries the work from the first commit to the pull request, and the task keeps up without you.

Agent skills

For delivery managers

Watch tasks move from created to delivered on their own

Tasks arrive from Linear, Jira or an agent over MCP, then move through progress, review and delivery as commits and pull requests land. Nobody drags a card, so the board is never stale.

Tasks & goals

For owners

See which projects actually make money

Revenue, cost and margin per project and per person, priced at the rates that applied the day the work happened, not the ones you charge now.

Roles & rates

For developers

Never fill in a timesheet again

Your commits already carry the timestamps and the task. Clocktopus turns them into the entries, so the sheet is written before anyone asks you for it.

Automatic tracking

For delivery managers

Catch an overrun in week three, not on the invoice

Every project draws its budget down as hours and agent spend land against it, so a job going under water surfaces while scope is still a conversation.

Project budgets

For owners

Put AI spend on the P&L, not the card statement

Agent runtime and cost land against the projects and tasks they served, so the model bill stops being one number nobody can split by client.

AI agents

For delivery managers

Know where a project stands without asking

Hours arrive as the work happens rather than on Friday afternoon, so the report is current when you open it and nobody has to be chased for it.

Reports & insights

For developers

Track a whole day without leaving the terminal

Clock in, check where the day stands, set your coding agents up with telemetry and skills. One command each, and the browser stays optional.

Command line

For delivery managers

Tell a hard week from a slow one

Cycle time, time to first review and how often work goes back for another round, each pull request sized by the effort it actually took. A quiet week reads as deep work or as a review queue nobody is clearing.

Delivery metrics

See every feature, written for developers, delivery managers or owners.

// pricing

Priced like a dev tool

Your whole team free for 30 days, then one developer free forever. Pay per seat only as your team grows, every feature on every plan.

clocktopus · pricingusd

$ clocktopus price --seats 2█

planseatsprice

›free1 userfree

›team2–10 users$12.00/user/mo

›team11+ users$10.00/user/mo

# drag to size your team2 seats · team

→ 2 seats$12.00/mo

✓ every feature on every plan · see everything included →

Start free

No credit card needed. Prices in USD.

Frequently Asked Questions

Commit, as they already do. Someone connects the repository once. If commit messages carry the task key in the conventional-commit scope, hours attribute themselves to tasks; if they don't, that's the one habit worth adopting, and it's a habit most teams already have. Clocking in and out and wiring up agent telemetry are single commands, and both are optional.

Some days are all meetings and reviews with no code written. That's fine. Clocktopus shows what your commits say, so if there's nothing, that day is empty. You can manually add time for non-commit work if you need to.

Yes. Clocktopus gives you a starting point, not a final answer. You can adjust hours, reword commit messages into something client-friendly, or add notes before sharing it.

No. The hours side stands alone. Never connect an agent and you still have a priced timesheet.

One CLI command wires your coding agent's telemetry to Clocktopus. Each run reports runtime, tokens and cost against the project it worked on.

No. Agent runtime is never added to anyone’s tracked hours. Only the money joins the same project total.

Each job role carries a sell rate and a cost rate, with per-project overrides. Rates are dated, so past work is never silently repriced.

Your code never leaves your repository. The webhook sends only commit metadata: timestamps, messages and branch names. Nothing else is sent.