How a run works
A ThriveOnDev task goes from a Linear issue to a merged pull request in four stages: implement, review, fix review when needed, and release. Each stage is a separate run, and the Linear issue shows where the task is.
- ImplementAn agent makes the change in an isolated environment, runs the checks and opens a pull request.
- ReviewA separate run, on the reviewer agent your team chose, checks the pull request against the issue.
- Fix reviewWhen the review asks for changes or release checks fail, the agent fixes the pull request and it goes back to review.
- ReleaseThe reviewed pull request must pass CI. Then it is squash-merged and the issue moves to Done.
1. Implement
When you hand an issue to the agent, the issue moves to In Progress. The agent reads the issue and the linked context, clones the target repository in an isolated environment, makes the change and runs the relevant checks. It then opens a pull request that says what changed and how to verify it.
If something in the issue is unclear, the agent asks in the Linear thread and waits for your answer. The task shows as Needs you on the Workflow board until you reply.
2. Review
The issue moves to In Review, and a separate run checks the pull request against the issue. That run uses your workspace's reviewer agent, which can be a different agent from the one that wrote the code.
The review either approves the pull request or requests changes.
3. Fix review
When the review requests changes, the issue returns to In Progress and the agent addresses the findings on the same pull request. The pull request then goes back to review.
This loop has a limit. After three automatic fix-review rounds, the next rejection pauses the loop: the agent leaves a comment, the issue stays in In Review, and a person decides what to do. Change requests from people don't count toward the limit.
Optional: human approval
If your workspace requires human approval, an approved pull request moves to In Human Review and waits for an approving review in GitHub. If a person requests changes, the task goes back to fix review. See Review loop and human approval.
4. Release
The issue moves to In Release. ThriveOnDev checks that the pull request's CI passes, squash-merges the exact commit that was reviewed, deletes the branch, and moves the issue to Done.
Release never rewrites the branch. If CI fails or the pull request conflicts with the base branch, the task goes back to fix review, where the agent merges the base branch in and fixes the problem. A task can return from release this way up to three times.
Limits that apply to every run
- A run stops after 5 hours. Split larger work into several issues.
- A run can only change the repositories and branches your workspace allows.
- If all of your workspace's slots are busy, the task waits in the queue and starts by itself.