llms.txt
Compare with other sites' llms.txt files →# Clocktopus
> See how your team ships, from task to delivery: cycle time, rework and cost for humans and AI agents, from the tools you already use.
Hours are derived from commit metadata — timestamps, messages, branch and
author — pushed by a GitHub or Bitbucket webhook. Source code is never sent.
Agent runtime and cost are reported separately by a CLI and land against the
same project, but never inside anyone's tracked hours.
## Get started
- [What Clocktopus is](https://clocktopus.app/docs/what-is-clocktopus): The delivery ledger for humans and agents — what was delivered, and what it cost to deliver.
- [Quickstart](https://clocktopus.app/docs/quickstart): Install the CLI and run clocktopus init in your checkout — it connects the repository, your git email and your agents, then checks it all works.
## Core
- [Automatic tracking](https://clocktopus.app/docs/automatic-tracking): How commits and reviews become priced time entries, what happens when the evidence is incomplete, and how to correct a day.
- [AI agents](https://clocktopus.app/docs/ai-agents): What your coding agents cost, why that never joins your billable hours, and how it reaches a project and a task.
- [Rates and project budgets](https://clocktopus.app/docs/rates-and-budgets): How job roles price an hour, how effective dating protects last month's reports, and how budgets and margin goals judge a project.
- [Reports and insights](https://clocktopus.app/docs/reports-and-insights): Where the ledger is read back — the dashboard for the shape of a period, the reports for a specific question.
- [Delivery metrics](https://clocktopus.app/docs/delivery-metrics): What the pull request, shipment, lead time, development time, task stage and complexity widgets measure, how to read them honestly, and what they deliberately refuse to tell you.
## Setup
- [Connect a repository](https://clocktopus.app/docs/connect-a-repository): Install the GitHub App or add a webhook by hand, then attach the repository to a project.
- [Task keys](https://clocktopus.app/docs/task-keys): How a project's task key prefix and tracker key prefixes decide which keys in your branches, commits and pull requests are its tasks.
- [CLI](https://clocktopus.app/docs/cli): Set up a checkout, sign this machine in, correct the clock, and connect your AI agents — from the terminal.
- [Commit addresses](https://clocktopus.app/docs/tracked-emails): Link commits authored under a different email address to your account, and answer who wrote commits nobody recognises.
- [Member access](https://clocktopus.app/docs/member-access): Add people to an organisation and control which projects each member can see and log time to.
- [Permissions](https://clocktopus.app/docs/permissions): Who can see and do what, by organisation role — one matrix per area of the app.
- [MCP server](https://clocktopus.app/docs/mcp-server): Connect an MCP-compatible AI assistant so it can read your hours and tasks, and create tasks and plan goals, on your behalf.
- [Agent skills](https://clocktopus.app/docs/agent-skills): How tasks reach Clocktopus, how your coding agent picks one up, and how its stage moves on its own while the work happens.
- [Install as an app](https://clocktopus.app/docs/install-app): Install Clocktopus to your desktop or home screen as a Progressive Web App.
## Writing
- [Scrum is dead?](https://clocktopus.app/blog/scrum-is-dead): Building is no longer the expensive part of software, and the way we run delivery hasn't caught up. Clocktopus v1.15 introduces tasks and goals: tickets that move themselves, and agents you point at outcomes instead of chatting with.
- [One worktree per agent thread: the change that took me from 8 to 45 PRs a week](https://clocktopus.app/blog/one-worktree-per-agent-thread): I set out to test Zed as an agent harness and came back with a better workflow instead: one git worktree per thread, a hook that makes new worktrees free, a 20% inspection habit, and reviews that run overnight. 45 PRs merged, 34 hours of steering, 832M tokens. Here's what to copy.
- [Half a billion tokens in three days: who's going to pay for this?](https://clocktopus.app/blog/half-a-billion-tokens-in-three-days): One of our developers burned 574 million tokens in three days of ordinary work. That's US$413.86 of inference, against a subscription that costs a fraction of it. Clocktopus now tracks agent spend next to human hours, which makes the awkward question answerable: when the prices correct, who pays?
- [Give every project a budget (and let it end)](https://clocktopus.app/blog/give-every-project-a-budget): We've shipped rates on job roles, budgets on projects, and margin on the dashboard. And an opinion to go with it: a project should get one budget, for its whole life, and when the money runs out the project should end.
- [We blamed serverless for our latency. It was Next.js.](https://clocktopus.app/blog/cutting-latency-nextjs-to-tanstack-start): We got latency complaints and assumed serverless cold starts. We were wrong. Most of it was Next.js's own startup overhead running inside the function. Here's how we found that out, what swapping to TanStack Start fixed, and why Cloudflare Workers are next.
- [Clocktopus now speaks MCP](https://clocktopus.app/blog/clocktopus-now-speaks-mcp): Your tracked hours are now something you can just ask about. We've shipped an MCP server, so Claude, ChatGPT, or any assistant that speaks the protocol can read your time and answer questions about it, in plain English.
- [How agencies lose 6 hours a week to timesheet chasing](https://clocktopus.app/blog/agencies-lose-six-hours-to-timesheet-chasing): The expensive part of timesheets isn't filling them in. It's chasing them down. Here's the math on what manual time tracking really costs a 10-person agency, and where the hours actually go.
- [Why I stopped writing timesheets and let my git log do it](https://clocktopus.app/blog/why-i-stopped-writing-timesheets): It's 5pm on Friday, everyone's left for happy hour, and you're staring at an empty timesheet trying to remember what you did on Tuesday. The thing is, the record already exists. It's sitting in your git log.
## Optional
- [Pricing and FAQ](https://clocktopus.app/): on the home page
- [All articles](https://clocktopus.app/blog)
- [Changelog](https://clocktopus.app/changelog): what changed, release by release