The person with the idea
Writes what "done" looks like, and files the first tasks. Answers a question when an agent asks one.
Doesn't need to read code, or touch the CLI.
When an agent needs your input →For product managers with an engineering team
Your engineers are booked. The small asks can still ship.
Write the ask in plain words. An agent builds it on its own branch. Your engineers keep the review rules.
- $16.92
- Mean cost per shipped story
- 63.6 min
- Median time from brief to merge
- 7
- Real tasks filed in plain English
Cost and lead time measured across 355 shipped stories, the week of 21–27 September 2026. Task count from /examples#nocode.
The long tail
The asks that never make a sprint
A copy fix. A cut-off label. A column that shows the wrong unit. Each one is small. Each one loses to roadmap work. These are real briefs, filed in plain words, with what came back.
"Comments and Sub tasks icons should be on the same line as the title"
Stopped the counts from wrapping onto their own line and made them clickable, so clicking one jumps straight to its section.
"Ridiculous that the size is truncated on this table. Also we need to be able to view attachments... so we should be able to preview images, videos or PDF's etc in the browser in a popover/modal."
Fixed the truncated Size column and shipped an in-browser preview modal for images, video, audio, and PDFs, with zoom and a download fallback.
"Copy and number formatting issues on the Observability page: durations mix units, a percent column shows a dash for small values, a token count has no separator, a date range shows the wrong end, and one column mixes three time formats."
Gave each quantity one formatter: seconds or minutes for durations, a proper under-0.1% floor for percents, comma-separated token counts, an inclusive date range, and one time format per column.
Who does what on your team
You file. An engineer sets it up once.
One engineer connects a device and a repository. After that, you do not need that engineer to file a task.
The technical owner
Connects the first device and the first repository. One-time setup.
Doesn't need to stay involved once that first setup is done.
How do I add a device? →The approver
Signs off where a gate asks for it. Answers agent questions on tasks it operates.
Doesn't need to read every diff. The review stage already checked it.
Approvals & staying in control →Your engineers stay in control
The rules belong to the team
Your engineers can put an approval gate on the entry stage. Then a member they choose approves each task before an agent starts it. They can also require one human approval on the git host before merge. Your team can turn on these gates:
- Required fields
- Required verifications
- Checklist gates
- Approvals with separation of duties
- Dependency and close gates
- Change-size limit
Read how approvals work, every gate, and the Review debt panel, which shows how long work waits for review. When your ask is unclear, the agent asks you. See when an agent needs your input.
Write a brief your engineers would accept
Say what is wrong and how to check it
A good brief names the problem and the result you expect. Read how to write a brief. Then test yours in the brief checker, or copy one from starter briefs. Two jobs suit this page well: ship a small feature and clear the bug backlog.
What to keep off the herd
Some work still needs a person
- Work on a host besides GitHub or GitLab. The merge stage signs in with your own gh or glab today.
- A change with no way to check the result: no test, no build command, no clear acceptance criteria.
- Anything you are not ready to have a person approve. A human still approves the plan and the result.
- Access to the hosted service is invite-only right now.
FAQ
Questions product teams ask
Does an engineer have to read every change I file?
Only if your team decides so. By default, the review stage checks the code before merge. To require a person, your engineers turn on one required human approval on the git host. The merge agent can't give it, so it blocks the task and waits for a person. They can also put an approval gate on any stage.
What if the agent does not understand my ask?
It asks you. A question appears on your dashboard and on the task's page. You pick an answer and submit it. No terminal is needed. The agent usually pauses until you answer.
Will an agent's work collide with the sprint work?
Not in the working copy. Each task gets its own isolated git worktree and branch. Your engineers still review and merge the change like any other.
What do my engineers still have to do?
One engineer connects a device and a repository, once. After that, your engineers set the approval rules and read the Review debt panel. They do not need to file your tasks for you.
Pick one ask from the backlog. File it today.
Choose the smallest one. Read the cost and the diff for yourself.