Blog

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.

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?

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 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.

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.

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.

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.