Skip to pricing
One Tuesday, delegatedPAR-482

Delegatethe task.

Read the day that followed.

?09:14 Maya delegates09:14 the agent starts09:18 the agent asks09:31 Maya answers09:34 the agent resumes09:49 Tomas merged
$0.94cost of the whole run
13m 04swaiting
Tomasmerged it at 09:49
3files changed
212checks, all pass
1question asked
09:14 Maya delegates09:14 the agent starts
$0.94cost of the run
09:18 the agent asks
13m 04swaiting
09:31 Maya answers09:34 the agent resumes
Tomasmerged it at 09:49
One place for the whole dayTasksChatHuddlesWikiBoardsSprints

PAR-482. Maya delegates at 09:14. The agent asks one question at 09:18 and waits 13m 04s. Maya answers at 09:31 and the agent resumes at 09:34. Tomas merges it at 09:49. The run costs $0.94.

13m 04sone question waited for an answer, the longest gap of the day
$3.91the whole day, seven runs, itemised to the step
212/212checks passed before Tomas approved and merged
3sfrom the revert click to a reasoned revert PR with three files restored

The problem

Without a record, the day is five dots.

Most teams already hand work to an agent. They type a prompt, wait, and get a pull request back. The result is there. The way to it is gone.

Nobody can say when the agent stopped to ask, how long it waited or who answered, or what it cost until the invoice arrives as one number with no rows. Below is the same Tuesday twice.

The same Tuesday, twice

That 13m 04s, on a day without a record and a day with one.

13m 04sThe pink stretch on the lower row at 09:18. The top row did not wait, and its pull request opened thirteen minutes sooner.
an unrecorded choice the agent stopped to ask merged the part that was put back
WITHOUT A RECORDWITH ITHURA4h 40m skipped: 5 runs, $2.34zoom: 1 s = 32 px09:0009:1009:2009:3009:4014:3014:3514:4014:4514:49:00:02:04:06:0814:5613m 04s waiting10m 15s live3 s click to revert PR123456six jobs by hand. No end drawn.PAR-482 09:02unrecorded choice 09:18#1204 merged 09:49PAR-519 14:31#1209 merged 14:41alert 14:48:10PAR-482 09:02delegate 09:14asks 09:18:07Maya answers 09:31:11#1204 +214 -31Tomas 09:47:30merged 09:49:05PAR-519 14:31delegate 14:34#1209 +31 -12Aisha 14:40:50merged 14:41:05alert 14:48:10, 4% errorsMaya reverts 14:49:023 files restored 14:49:03#1212 opened 14:49:05a person merges it 14:51:20wiki note 14:56:3009:00:00
  1. 09:02 PAR-482 writtenMaya writes the task. The same on both sides.Task text only.
  2. 09:18 the agent hits a choiceWith Ithura it stops and asks. Maya answers at 09:31:11, after 13m 04s.It picks, keeps going, and the pick leaves no trace.
  3. 09:49 PR #1204 mergedRun cost $0.94 with Ithura, itemised by step.Same code. No trace of how it got there.
  4. 14:41 PR #1209 merged198/198 tests passed. Run cost $0.63.Same code, same tests, same merge.
  5. 14:48:10 invite errors at 4%Maya reverts at 14:49:02, with her reason. Revert PR opened at 14:49:05, three seconds after the click. A person merges it at 14:51:20.Undone by hand. Nobody has drawn the end.
13m 04sthe stall, on the lower row at 09:18
5facts kept on the left, linked to nothing
32facts kept on the right, in 30 links
$3.91agent cost on the right, by task, run and step

One axis, shared. The top lane is a team with no record: real events, joined by nothing. The lower three lanes are the same work in Ithura. The break at the left is 4h 40m of other runs, $2.34 of the day's cost.

The top row is a good team. It is missing a record, not care.

Read the top row as a team that does everything right. At 09:18 the agent guessed per workspace, and the guess was correct. Its pull request is as clean as the one below it, because it is the same code. What is missing is a place where the day is written down as it happens.

Same on both rows

The tasks, the agent, the code, the tests, the reviewer, the merges and the alert at 14:48:10.

Different on the lower row

Every step, question, cost and link is written down as it happens, and the last change can be put back with one click and a reason.

Honest about the wait

Where the top row gets there faster, this page says so. Where we cannot know how long something takes by hand, we draw no number.

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.

09:0009:1009:2009:3009:4009:5014:3014:4014:5014:5809:0509:1509:2509:3509:4514:3514:45TASKS+ PEOPLEAGENTRUNCODE(MAIN)13m 04swaiting on Mayaskipped4h 40m5 runsPAR-48209:02:00asked09:18:07Maya answers09:31:11PAR-51914:31:00errors 4%14:48:10Maya reverts14:49:02delegate09:14:20PR #120409:44:01Tomas approves09:47:30merged09:49:05delegate14:34:00PR #120914:39:55Aisha approves14:40:50merged14:41:05wiki note14:56:30
09:0009:0509:1009:1509:2009:2509:3009:3509:4009:4509:5014:3014:3514:4014:4514:5014:55TASKS+ PEOPLEAGENTRUNCODE(MAIN)13m 04sskipped4h 40m5 runsPAR-48209:02:00asked09:18:07Maya answers09:31:11PAR-51914:31:00errors 4%14:48:10Maya reverts14:49:02delegate09:14:20PR #120409:44:01Tomas approvesmerged09:49:05delegate14:34:00PR #120914:39:55Aisha approvesrevert PR #121214:49:05wiki note14:56:30
Last nodeWiki notewritten 14:56:30
Stamped14:56:30PAR-519, run_c5d7
Day cost$3.917 runs, 1 reverted
Longest stall13m 04son PAR-482

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.

09:0009:1009:0509:1509:0109:0209:0309:0409:0609:0709:0809:0909:1109:1209:1309:1409:1609:17TASKS+ PEOPLEAGENTRUNPAR-48209:02:00rate-limit invitesdelegate09:14:20run_8f3a opens04 edit09:17:00ratelimit.go +88 -12asked in chat09:18:0701 read09:14:52invites.go, ratelimit.go
09:0209:0309:1409:1509:1609:1709:18TASKS+ PEOPLEAGENTRUNCODE(MAIN)10 min skippedPAR-48209:02:00rate-limit invitesdelegate09:14:20run_8f3a opens04 edit09:17:00ratelimit.go +88 -1201 read09:14:52invites.go,ratelimit.go02 plan09:15:25limiter, handler, test03 edit09:16:15invites.go+41 -6
Written09:02:00PAR-482, by Maya
Delegated09:14:2012m 20s later
Runrun_8f3aopened on the middle lane
Cost so far$0.00nothing has run yet

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.

09:1509:1409:1609:1709:1809:19TASKS+ PEOPLEAGENTRUNaskedper workspace or user?$0.00delegaterun_8f3a opens04 editratelimit.go +88 -12$0.19asked in chat01 readinvites.go, ratelimit.go$0.0602 planlimiter, handler, test$0.0803 editinvites.go +41 -6$0.14
09:1409:1509:1609:1709:1809:19TASKS+ PEOPLEAGENTRUNCODE(MAIN)askedper workspace or user?$0.00delegaterun_8f3a opens04 editratelimit.go +88 -12$0.1901 read$0.0602 planlimiter, handler, test$0.0803 edit$0.14
Steps01 to 0409:14:52 to 09:17:00
Cost$0.47four steps
Biggest$0.19edit ratelimit.go
Edits2 files+129 -18

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.

09:2009:3009:2509:1709:1809:1909:2109:2209:2309:2409:2609:2709:2809:2909:3109:32TASKS+ PEOPLEAGENTRUN13m 04swaiting on Mayaasked09:18:07per workspace or user?Maya answers09:31:11per workspace04 edit09:17:00asked in chat09:18:07
09:1709:1809:1909:2009:2109:2209:2309:2409:2509:2609:2709:2809:2909:3009:3109:32TASKS+ PEOPLEAGENTRUNCODE(MAIN)13m 04sasked09:18:07per workspace or user?Maya answers09:31:11per workspace04 edit09:17:00ratelimit.go+88 -1203 edit09:16:15
Asked09:18:07per workspace or per user?
Answered09:31:11Maya: per workspace
Stall13m 04srun_8f3a waiting
Cost while waiting$0.00no edits made

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.

09:5009:4509:4209:4309:4409:4609:4709:4809:49TASKS+ PEOPLEAGENTRUNCODE(MAIN)3m 29s1m 35sPR #120409:44:01+214 -31Tomas approves09:47:30merged09:49:05by Tomas09 open PR09:44:01links to PAR-482CI 212/21209:46:12PAR-482 done09:50:11agent time 16m 37s
09:4209:4309:4409:4509:4609:4709:4809:4909:5009:51TASKS+ PEOPLEAGENTRUNCODE(MAIN)3m 29swaiting on review1m 35sPR #120409:44:01+214 -31Tomas approves09:47:30merged09:49:05by Tomas09 open PR09:44:01links to PAR-482CI 212/21209:46:12PAR-482 done09:50:11agent time 16m 37s
Pull request#1204+214 -31, three files
CI212/212passed 09:46:12
Approved09:47:30Tomas
Merged09:49:05by Tomas

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.

TimeStepDetailCost
09:14:5201 readinvites.go, ratelimit.go$0.06
09:15:2502 planlimiter, handler, test$0.08
09:16:1503 editinvites.go +41 -6$0.14
09:17:0004 editratelimit.go +88 -12$0.19
09:18:0705 askedper workspace or user?$0.00
09:34:2006 editinvites.go +19 -4$0.12
09:39:3007 editinvites_test.go +66 -9$0.21
09:42:4108 test212/212, no retries$0.03
09:44:0109 open PRlinks to PAR-482$0.11
Run run_8f3a, nine steps$0.94
09:0009:1009:2009:3009:4009:5014:3014:4014:5014:5809:0509:1509:2509:3509:4514:3514:45TASKS+ PEOPLEAGENTRUNCODE(MAIN)$2.34$0.21$0.19$0.15$0.14$0.14$0.12$0.11$0.09$0.06$0.03$0.00
09:0009:0509:1009:1509:2009:2509:3009:3509:4009:4509:5014:3014:3514:4014:4514:5014:55TASKS+ PEOPLEAGENTRUNCODE(MAIN)$2.345 runs skipped$0.21$0.19$0.15$0.14$0.14$0.12$0.12$0.11$0.09$0.08$0.08$0.06$0.03$0.03$0.02$0.00
Run run_8f3a$0.949 steps, kept
Run run_c5d7$0.63reverted
Five skipped runs$2.34not on the axis
Day total$3.917 runs

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.

09:0009:2009:3009:4009:5014:3014:4014:5014:5809:2509:2209:2709:4614:41TASKS+ PEOPLEAGENTRUNCODE(MAIN)13m 04swaiting on Mayaskipped4h 40m5 runs3m 29s1m 35s55s15sPAR-48209:02:00asked09:18:07Maya answers09:31:11PAR-51914:31:00errors 4%14:48:10Maya reverts14:49:02delegate09:14:20PR #120409:44:01Tomas approves09:47:30merged09:49:05delegate14:34:00PR #120914:39:55Aisha approves14:40:50merged14:41:05wiki note14:56:30
09:0009:1009:2009:3009:4009:5014:3014:4014:50TASKS+ PEOPLEAGENTRUNCODE(MAIN)13m 04sskipped4h 40m5 runs3m 29swaiting on review1m 35s55s15sPAR-482asked09:18:07Maya answers09:31:11PAR-51914:31:00errors 4%14:48:10Maya reverts14:49:02PR #120409:44:01merged09:49:05delegate14:34:00PR #120914:39:55Aisha approves14:40:50wiki note14:56:30
Waited, PAR-48218m 08s13m 04s + 3m 29s + 1m 35s
Worked, PAR-48216m 37sagent time
Waited, PAR-5191m 10s55s + 15s
Waiting share52%of the task's 34m 45s

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.

14:4014:5014:3514:4514:3614:3714:3814:3914:4114:4214:4314:4414:4614:4714:4814:49TASKS+ PEOPLEAGENTRUNCODE(MAIN)errors 4%14:48:10alert, run_c5d7Maya reverts14:49:02PR #120914:39:55+31 -12Aisha approves14:40:50merged14:41:0507 open PR14:39:55
14:3614:3714:3814:3914:4014:4114:4214:4314:4414:4514:4614:4714:4814:4914:50TASKS+ PEOPLEAGENTRUNCODE(MAIN)errors 4%14:48:10alert, run_c5d7Maya reverts14:49:02PR #120914:39:55+31 -12Aisha approves14:40:50merged14:41:05revert PR #121207 open PR14:39:55
Merged14:41:05PR #1209, +31 -12
Alert14:48:10invite errors at 4%
Linked runrun_c5d7$0.63, seven steps
Since merge7m 05sbefore errors hit 4%

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.

14:4014:5014:5814:4514:5514:3914:4114:4214:4314:4414:4614:4714:4814:4914:5114:5214:5314:5414:5614:57TASKS+ PEOPLEAGENTRUNCODE(MAIN)a person merges it14:51:2052salert to revert click10m 15sthe change was live55s3serrors 4%14:48:10alert, run_c5d7Maya reverts14:49:02PR #120914:39:55+31 -12Aisha approves14:40:50merged14:41:05wiki note14:56:30why it was reverted07 open PR14:39:55
14:3914:4014:4114:4214:4314:4414:4514:4614:4714:4814:4914:5014:5114:5214:5314:5414:5514:5614:5714:58TASKS+ PEOPLEAGENTRUNCODE(MAIN)a person merges it14:51:2052s10m 15sthe change was live55s3serrors 4%PR #1209Aisha approves14:40:50merged14:41:05revert PR #121214:49:05wiki note14:56:30why it was reverted07 open PR14:39:55
Alert to click52s14:48:10 to 14:49:02, Maya
Click to PR open3srevert PR #1212, 14:49:05
Merged14:51:20by a person, on GitHub
Live10m 15smerge 14:41:05 to revert merge

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.

09:0009:1009:2009:3009:4009:5014:3014:4014:5014:5809:0509:1509:2509:3509:4514:3514:45TASKS+ PEOPLEAGENTRUNCODE(MAIN)skipped4h 40m5 runsMaya answers09:31:11Maya reverts14:49:02Tomas approves09:47:30merged09:49:05Aisha approves14:40:50merged14:41:05
09:0009:0509:1009:1509:2009:2509:3009:3509:4009:4509:5014:3014:3514:4014:4514:5014:55TASKS+ PEOPLEAGENTRUNCODE(MAIN)skipped4h 40m5 runsMaya answers09:31:11Maya reverts14:49:02Tomas approvesmerged09:49:05Aisha approves14:40:50merged14:41:05
Decisions by people71 answer, 2 approvals, 3 merges, 1 revert
Approvals2Tomas, Aisha
Merges3a person each, revert PR included
Reverts1Maya, 14:49:02

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.

09:0009:1009:2009:3009:4009:5014:3014:4014:5014:5809:0509:1509:2509:3509:4514:3514:45TASKS+ PEOPLEAGENTRUNCODE(MAIN)skipped4h 40m5 runsMayaMayaTomasAisha
09:0009:0509:1009:1509:2009:2509:3009:3509:4009:4509:5014:3014:3514:4014:4514:5014:55TASKS+ PEOPLEAGENTRUNCODE(MAIN)skipped4h 40m5 runsMayaMayaTomasAisha
People3Maya, Tomas, Aisha
Pro seatEUR 10per user / month
Three seatsEUR 30per month
Run cost$3.91itemised on receipts

Who it is for

The same Tuesday, from three chairs.

Maya, who owns the task

She wrote PAR-482 at 09:02, delegated it at 09:14, answered at 09:31 and pressed Revert at 14:49. Both decisions are on the record with her name.

Tomas, who reviews

He opened PR #1204 and found a run behind it: nine steps, one question, one answer, $0.94. He approved at 09:47 and merged at 09:49.

Aisha, who gets the alert

At 14:48 she followed the alert to the merge, the pull request and the run, and read what the agent read, in order.

Start

Your first day takes an hour.

  1. 1

    Make a workspace

    Free covers three members and one project. Add a repository and invite your reviewer.

  2. 2

    Delegate one small task

    Pick something with a clear edge, write it as you would for a colleague, then press Delegate.

  3. 3

    Answer when it asks

    The question arrives in chat and on Home. Answer in a line, then review the pull request like any other.

Pricing

Pay for the people on the team.

Four plans. Prices are per user per month. Guests never take a seat on any plan. Free allows three members and up to five guests; Starter and above are unlimited. Nothing here is a quote: the price you see is the price you pay.

Free

EUR 0forever

A real workspace, sized for one or two.

  • 3 members, 1 project
  • 1 agent, 10 runs a day
  • Tasks, views & real-time collab
  • Chat with 30-day history
  • Import & export, always
  • 200 MB storage
  • 30-day activity history
  • 30-day run record
Start on Free

Starter

EUR 5per user / month

The essentials for a small team.

  • Unlimited members & projects
  • 3 agents, unlimited runs
  • Tasks, sub-tasks & custom fields
  • Unlimited chat & activity history
  • GitHub, Slack & email-in
  • REST API & Zapier/Make
  • Guests included free
Start on Starter

Pro Recommended

EUR 10per user / month

The whole product, plus security.

  • Everything in Starter
  • Unlimited agents
  • Sprints, OKRs & roadmap
  • Wiki, boards & analytics
  • Huddles: video calls & screenshare
  • SSO, audit & custom roles
  • Webhooks & AI (your own model key)
  • Agent quality: merge rate & cost per merge
Start on Pro

Enterprise

EUR 20per user / month

Governance and scale, published price.

  • Everything in Pro
  • SCIM provisioning
  • Huddle recording & E2EE
  • IP allowlist & session policy
  • Priority support & uptime SLA
Start on Enterprise
  • Tasks
  • Chat
  • Huddles
  • Wiki
  • Boards
  • Sprints
  • Goals
  • Decisions
  • Insights
  • Agents with receipts

Start on Free and move up when the team needs it. Agent runs are not seats. The receipt shows what the model provider charged, billed to your own provider account.

Questions

What people ask first.

Does the agent merge its own work?

No. It opens a pull request and stops. A person reviews, approves and merges.

What if the agent asks a question and nobody answers?

It waits, and it costs nothing while it waits. The wait is recorded at its true length, so a stall that would have been invisible shows up with a number on it.

How is the cost worked out?

Each step records what the model provider charged for it. The receipt lists the steps and the total. Runs are not billed as seats. Your plan is the people.

What does Revert change, exactly?

It opens a normal pull request that undoes the merge, with a reason you must give, in about three seconds. Your branch rules apply, and a person merges it on GitHub like any other. The original run stays on the record, with its steps and its cost.

Which plan has single sign-on?

Pro, at EUR 10 per user per month. SCIM provisioning is Enterprise.

Why does the drawing skip the middle of the day?

It skips 4h 40m between 09:50 and 14:30, where five other runs happened. They are in the $3.91 total, and each one has its own receipt.

Who can answer the agent's question?

Anyone with access to the task. Maya answered in this story, but a teammate in the channel could have. The record shows who answered and when, and a guest can answer without costing you a seat.

Does it read my whole codebase?

The agent works inside the task it was given and the repositories connected to it. What it read is listed step by step on the run, so you can check it, and nothing it reads is hidden from the people on the team.

Can I delegate more than one task at once?

Yes. Each delegation is its own run with its own steps, question, wait and cost. On the day in this story there were seven runs, and the total is the sum of their receipts.

What happens to the record after a revert?

It stays. The run is cut back in the drawing and a short stub marks where it ended. The steps, the cost and the reason Maya gave stay readable, which is what makes the wiki note worth writing.

Do I need to change how my team reviews code?

No. Review stays a pull request, read and approved by a person under your branch rules. What changes is that the reviewer can open the run beside it and see why the diff looks the way it does.

Is this a ranking of agents?

No. The waiting view is a retro on your own team, with numbers on it. It shows where time went between people and work, so you can move review earlier or name who answers for a project.

How is a guest different from a member?

A guest can see and answer what you share with them, such as a question on a task. Guests are free on every paid plan and are never counted as seats, so a client can reply without costing you anything.

What does the free plan not include?

Free is a real workspace for one or two people: three members, one project, 30 days of chat and activity, and 200 MB of storage. Sprints, wiki, boards, Huddles and single sign-on start on Pro.

Can I leave if I do not like it?

Yes. Import and export are on every plan, Free included. Your tasks, your runs and their receipts come out as files you can keep.

Everything else in the box

TasksA delegated task is a normal task with a normal owner.
ChatQuestions from the agent land where people already read.
HuddlesVideo calls with screenshare, inside the workspace.
WikiThe page that says why sits next to its task.
Boards, sprintsAgent work counts against the same sprint as everyone's.
GitHub, SlackPull requests link back to the task and the run.

Hand over the next task.

Start on Free. Delegate one task, answer when it asks, and read the day that followed. Nobody needs to book a demo first.