Core concepts
Six ideas explain how ThriveOnDev behaves: a task is made of runs, runs go through stages, review and fix review form a loop, aliases choose the agent, AI access pays for the model, and slots limit how many agents run at once.
Tasks and runs
A task is one Linear issue you handed to ThriveOnDev. A run is one start of an agent for one stage of that task. A typical task has at least two runs: one that implements the change and one that reviews it.
Every run starts in a fresh, isolated environment with access only to the repository the task targets.
Stages
Each task moves through four stages, and the Linear issue moves through your statuses with it:
| Stage | What happens | Linear status |
|---|---|---|
| Implement | The agent makes the change and opens a pull request. | In Progress |
| Review | A separate run checks the pull request. | In Review |
| Fix review | The agent addresses the findings, then the pull request is reviewed again. | In Progress, then In Review |
| Release | CI must pass, then the pull request is squash-merged. | In Release, then Done |
If your workspace requires human approval, the task waits in In Human Review between review and release.
The review loop
Review and fix review repeat until the review approves. The loop has a limit: after three automatic fix-review rounds the agent stops and leaves a comment in Linear, and a person decides what to do next. Read more in Review loop and human approval.
Aliases
An alias such as #opus or #sol names an agent and a model. Write one in an issue to choose who implements it. Your workspace also has a default developer agent and a reviewer agent. See Choose an agent with aliases.
AI access
Runs use the AI access of the person who gave the task: their Claude key or their ChatGPT sign-in for Codex. Tasks picked up through the Automatable label use the access of the person your workspace chose for automatic tasks.
Slots and the queue
Your workspace runs a limited number of agents at the same time. Each running agent takes a slot. When all slots are busy, new tasks wait in the queue and start by themselves.
Workspace
Your workspace holds your connections to Linear and GitHub, the repositories the agent may change, your people and their roles, and your settings. It has two screens: Workflow and Settings.