Use cases
Use cases
The tasks below are samples, not real Issues. They show how a dispatch ends for each kind of task.
Bump a dependency
A clear, mechanical task. If the diff only touches manifests and lockfiles and CI is green, it can merge without a human.
Sample messages
- Sample task: “Bump zod to the latest 3.x and fix any type errors.”
- task-definition-eval: DELEGATABLE
- completeness-eval: DONE; CI green; auto-merged; Status Done
Add a small CI check
A real change with a judgment call in it. It gets a pull request with the verdicts and waits for a human.
Sample messages
- Sample task: “Add a typecheck job that runs tsc --noEmit on pull requests.”
- completeness-eval: DONE
- Pull request held for human merge
A task that is too vague
The run stops before any file is edited and says what is missing.
Sample messages
- Sample task: “Make the app faster.”
- task-definition-eval: BOUNCE, with the missing details
- Status Waiting+needs-you
Ask for a change on the pull request
A comment on the open pull request runs a revision on the same branch.
Sample messages
- Sample comment: “Also run the job on pushes to main.”
- Revision: agent re-run, completeness-eval DONE
- Branch force-pushed; comment with the verdict
Run your own control plane
One control repo, one Lambda relay, one self-hosted runner and a GitHub App, all under your own accounts. There is no hosted service and no account to sign up for.