The Delivery Ledger for Humans and Agents

Commit, as they already do. Someone connects the repository once. If commit messages carry the ticket 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 read.