Every hour you work,
every dollar your agents burn

Your agent picks up the next task and the board keeps up on its own, from the first commit to delivery. The timesheet builds itself from those commits, and your agents' runtime and spend land beside the hours against the same tasks, so what you shipped and what it took to ship it finally tell the same story.

Automatic tracking

Your commits become your timesheet

You already wrote down what you did. It's sitting in the commit log. Clocktopus receives the timestamps, works out the durations, and files the hours against the right project. Nothing to start, nothing to remember, nothing to reconstruct on Friday afternoon.

feat: add checkout flow
9:42 am
fix: rounding in totals
11:15 am
refactor: extract cart hooks
2:03 pm
Tasks & goals

The task is the brief your agent starts from

A task arrives from Linear, Jira or your agent over MCP, with its key, title and description. Your agent starts from it with the code already in context, and the task moves on its own: in progress at the first commit, in review when the pull request opens, delivered when the work reaches main. Nobody drags a card or writes a status update.

APO-171
Customers export invoices as CSV
Linear
  1. CreatedCreated in Linear
  2. In progressAgent session on apo-171-export-invoices
  3. In reviewPull request #48 opened
  4. Ready to ship#48 merged into develop
  5. DeliveredWaiting to reach main
Nobody moved this task. Every step came from git.
Agent skills

From a one-line idea to a pull request

One command installs four skills into Claude Code, Codex and OpenCode. create-task turns a line from you into a task an agent can pick up, without breaking your flow, and refine is there when you want to check it covers everything. start-work ties the session's spend to the task, branches from its key and carries it through to an open pull request. The loop runs in the harness you already use.

>/clocktopus:start-work
APO-171, 2 of 5 in “Customers export invoices”
Session linked to APO-171
Branch apo-171-export-invoices
Pull request #48 opened
create-taskstart-workrefinecreate-goal
Claude Code · Codex · OpenCode
Clock signals

Shape your day without running a timer

One clock-in when you start, one clock-out when you're done, both from the terminal. That's the entire interaction, and it keeps your commit time inside real working hours instead of stretching across a late-night push.

Tuesday8:52 am – 5:31 pm
Clocked inClocked out
Command line

Track it all without leaving the terminal

Clock in, check where the day stands, and set your coding agents up with telemetry and skills in a single command. Install it once and the browser becomes optional.

$clocktopus clock in
Clocked in at 8:52 am
$clocktopus agent setup
Hooks and skills installed for Claude Code, Codex and OpenCode
AI agents

See what your agents actually cost

Your commits stopped being proportional to your effort the day an agent started writing them. Clocktopus records the runtime, tokens and spend the harness reports, and files them against the same project and task as your hours. Agent time never inflates yours; only the dollars combine.

Agent spend by taskProject Apollo
TaskHumanAgent
APO-1426.0h$62.81
APO-1564.0h$17.34
No task1.0h$14.80
MCP access

Ask your assistant where the time went

Connect Claude, or whichever assistant you use, to Clocktopus over MCP and ask in plain language. Remote server, nothing to install. It reads your hours and can add tasks as it works, but never touches your timesheet.

Match open Jira tasks for Apollo with hours logged in Clocktopus, and flag anything behind.

APO-142 and APO-156 are over estimate (14.5h vs 6h, 9h vs 4h). The other 6 tasks are tracking on time.

MCPNever edits your timesheet · OAuth 2.1 secured
Reports & insights

Your week, on one screen

Filter your own hours by project and date range and see where the week actually went. Useful for a standup, a self-review, or working out what happened to Thursday.

Hours by projectMay
ProjectMemberDate range
Delivery metrics

Proof that the quiet week was the hard one

Two days inside one gnarly bug looks like nothing in a commit count. Clocktopus sizes each pull request on the effort behind it as well as the output, so deep work reads as deep work. On your own tab it covers your pull requests, and nobody needs a tab to see it.

Your deliveryLast 30 days
Merged
7
Cycle time
14.3h
First review
2.1h
Quick win3
Deep work2
Heavy lift2
Contested1
Compared with the team median, never with each other
Teams & permissions

Your work, not the whole company ranked

You see the projects you're on. Rates, margins and everyone else's totals stay where they belong. The tool is a record of what happened, not a leaderboard pointed at your desk.

ALAlice
Owner
BOBob
Admin
CACarol
Member
Project Apollo - restricted to 2 of 3 members
Roles & rates

Your rate is set once, by someone else

You never type a number. Your job role carries the rates, so the hours you log are priced without you touching a rate card, seeing what a client pays, or thinking about any of it again.

Job roleSell / hCost / h
Senior Engineer$180$95
Engineer$140$72
Designer$130$68
Senior Engineer rises to $195 from 1 Jul
Project budgets

See how much runway the project has

The budget sits on the project, drawn down by the hours already logged. When you're weighing whether there's room for the refactor, the answer is on the screen instead of in someone else's spreadsheet.

Project Apolloon track
$31,200 consumed$48,000 budget
Target margin
30%
Profit left
$9,400

Free for single developers.
Per-seat when the team grows.

Every feature above is included on every plan.