velo

What a human-plus-agent team actually gets done.

A velo window: projects down the left with their hours, a tab per agent across the top, then one row of figures — human hours, agent hours, leverage, commits, retail API cost, compute cost, what you paid and the ratio — and below it a single chart of hours per day, human under agent, the agent part shaded by what its hours cost, with commits as a line over the bars.

A generated example, not anyone's real data.

Download for macOS

Free · macOS 14 or later · Apple silicon & Intel · version 0.5.0 · 4.9 MB

No timers

Nothing to start and nothing to remember. It reads what already happened: your git history, and the session logs Claude Code, Codex and Gemini CLI already write.

Five numbers, labelled honestly

Human hours, agent hours, retail API cost, compute cost, what you paid — and leverage, the first two as a ratio. Two are facts, one is arithmetic, two are estimates, and the window says which.

One tab per agent

Claude, Codex and Gemini CLI over the same ledger. All is a union rather than a sum: an hour spent switching between two of them is one hour.

velo report

Every figure on the command line too, --json and all, so the agent making the next estimate can read how the last one went.