Tuesday, 09:00 to 14:58
Now the same day, with the record kept.
Nothing about the work changed. Every step became a node with a time on it, joined to the one that caused it. Tasks and people run along the top, the agent through the middle, your main branch along the bottom. Five more runs happened between 09:50 and 14:30. They are in the day's total, not on the drawing.
01 / Delegate
Twelve minutes after she wrote it, Maya handed it over.
At 09:02 Maya wrote PAR-482: rate-limit invites. At 09:14:20 she pressed Delegate. The agent works from the task itself, not from a pasted prompt. Nothing is copied. You can delegate a small task and keep a large one for a person, and the task shows who has it now.
02 / Watch
Every step is a dot with a time and a price.
From 09:14:52 each thing the agent did became a node. Four steps, $0.47 by 09:17:00. A step has an address you can link to, and cost sits on the step, not in a monthly total. Step three cost 14 cents. Step four cost 19.
03 / Answer
Then it hit a choice it should not make alone, and stopped.
At 09:18:07 the agent hit a choice it should not make alone and asked: per workspace or per user? Maya answered at 09:31:11. The wait was 13m 04s, and it cost nothing. A question that waits in a log reads as an agent that is slow. A question that lands in the channel and in Home reads as what it is: a decision that needs a person, with a name and a clock on it.
Where you answer
It goes to the person, where they already are.
The question goes to the channel and to Maya's Home, so she answers in one line.
- ChatIn the channel the task belongs to. Reply in a line.
- HomeUnder what needs you. Answer without opening the task.
- The taskOn PAR-482, next to the run, with who asked and when.
- Slack and emailOn Starter and above. Guests are free, so a client can answer.
04 / Account
A person approves. A person merges.
At 09:44:01 the agent opened PR #1204. CI passed 212 of 212. Tomas approved at 09:47:30 and merged at 09:49:05. The agent does not merge. The pink stretches are waiting: 3m 29s for review, 1m 35s from approval to merge. Nobody chose them. They are in the record anyway.
Receipts
Open the run. Every number has a row.
A receipt is a table. Each row is a step with its time and cost, and the invoice is built from the rows. The total adds up because it is made of them.
| Time | Step | Detail | Cost |
|---|---|---|---|
| 09:14:52 | 01 read | invites.go, ratelimit.go | $0.06 |
| 09:15:25 | 02 plan | limiter, handler, test | $0.08 |
| 09:16:15 | 03 edit | invites.go +41 -6 | $0.14 |
| 09:17:00 | 04 edit | ratelimit.go +88 -12 | $0.19 |
| 09:18:07 | 05 asked | per workspace or user? | $0.00 |
| 09:34:20 | 06 edit | invites.go +19 -4 | $0.12 |
| 09:39:30 | 07 edit | invites_test.go +66 -9 | $0.21 |
| 09:42:41 | 08 test | 212/212, no retries | $0.03 |
| 09:44:01 | 09 open PR | links to PAR-482 | $0.11 |
| Run run_8f3a, nine steps | $0.94 | ||
Waiting
Where the time actually went.
The agent worked for 16m 37s. Around it the task waited 18m 08s on people: 13m 04s for an answer, 3m 29s for review, 1m 35s for the merge. Once you can see waiting, you can move it. Put review in the morning. Name who answers for a project. This is a retro on your own team, with numbers on it, not a ranking of agents.
When it goes wrong
Seven minutes after the merge, invites started failing.
PAR-519 merged at 14:41:05. At 14:48:10 invite errors reached 4%. The alert links to the merge, the merge to the pull request, the pull request to the run. You read what the agent read, in order, and what it changed. Without the record you would know that something broke at 14:48 and that a pull request merged at 14:41. With it you know which task asked for the change and who approved it.
Undo
One click, a revert in three seconds. A person merges it.
Maya pressed Revert at 14:49:02, 52 seconds after the alert, and gave a reason. At 14:49:05, three seconds later, revert PR #1212 was open with the three files put back.
Ithura does not merge it. A person merged it on GitHub at 14:51:20, and invites worked again. The change was live for 10m 15s, from the merge at 14:41:05 to the merge of the revert. A wiki note at 14:56:30 says why.
Trust
People decide. The agent proposes.
One answer, two approvals, three merges and one revert click. Every one was a person, the revert PR included. The agent opens pull requests and stops. It does not approve its own work, and it does not revert someone else's. You can open any run, read every step in order, and compare it with the pull request that came out.
Seats
Pay for the people. Not for the runs.
Three people made every decision, so three seats. Three Pro seats are EUR 30 a month, plus $3.91 for the day's runs. Guests are never billed. The invoice has two lines you can read at a glance: seats and runs. If a month is expensive, the receipts say which task cost what.