Documentation

Reference

Definitions, status tables, limits and a symptom index — the things you look up rather than read.

Lookup material. These pages are written to be scanned, not read start to finish.

In this section

Glossary — every term the interface uses, defined once. Start here when a word in the product does not mean what you assumed.

Task statuses — every status a task can hold, what causes it, and what to do about it. The page to open when something is sitting in a state you did not expect.

Limits and quotas — which ceilings exist, how they behave, and what happens when you reach one. No limit deletes anything.

Troubleshooting index — symptom to answer. The fastest route when something is not behaving the way you expect.

The three things worth knowing up front

If you read nothing else in this section:

  1. NEEDS_HUMAN_REVIEW is not a failure. It means a decision needs you. Answer it and the task continues.
  2. Slots control how many tasks run at once, not how fast one runs. Most "Coroid is slow" questions are really scope or test-suite questions.
  3. Nothing reaches your base branch without a pull request. Whatever else goes wrong, that property holds.