Coroid is an AI software factory. You describe what you need, and Coroid plans the work, writes the code, tests it, reviews it, and opens a pull request in your repository for you to approve.
These docs cover the product as it ships today. If a feature is not documented here, it is not available yet.
New here
Work through Get started in order. It takes you from an empty account to a merged pull request: create an organization, connect a repository, create a project, run a task, review the result.
Understand how it works
How a task becomes a pull request is the page everything else refers back to — the full path from your description to a PR, with every stage named.
Then Agent roles for who does what, and Specifications, which is the highest-leverage thing you can get good at. The quality of what Coroid builds is bounded by the quality of what it is asked to build.
Find your way around
| Section | What it covers |
|---|---|
| Get started | Account to first merged pull request |
| Concepts | How the system actually works |
| Projects and code | Repositories, build and test setup, context |
| The factory | Running work, schedules, Sentinel, reports |
| Quality and review | Gates, findings, evidence, browser tests |
| Organization settings | Members, keys, policy, retention |
| Billing and capacity | Slots, credits, usage, invoices |
| Integrations | Source control, chat, MCP, evidence, hooks |
| Reference | Glossary, statuses, limits, troubleshooting |
Three things worth knowing immediately
Agent slots control how many tasks run at once — not how fast one runs. A single task's duration comes from the size of the change and your test suite. See Capacity and agent slots.
NEEDS_HUMAN_REVIEW is not a failure. It means the work hit a decision only
you can make. Answer it and the task continues. See
Task statuses.
Something not behaving as expected
Start at the troubleshooting index, which maps symptoms to answers.