Documentation

Coroid documentation

Discover how to transform a description of your requirements into a reviewed pull request in your own repository.

Coroid functions as an AI software factory. You outline what you need, and Coroid then plans the work, writes the code, tests it, reviews it, and opens a pull request in your repository for your approval.

These documents detail the product as it is released today. If a feature is not covered here, it is not yet available.

New here

Work through Get started in sequence. This process guides you from an empty account to a merged pull request: create an organisation, connect a repository, create a Project, run a Task, and review the outcome.

Understand how it works

How a Task becomes a pull request serves as the reference page for all other content — detailing the complete journey from your description to a PR, with each stage clearly named.

Then Agent roles to clarify who does what, and the specification-driven development guide, which represents the most impactful skill to master. The quality of what Coroid delivers depends on the clarity of the requirements provided.

Find your way around

SectionWhat it covers
Get startedFrom Account setup to the first merged pull request
ConceptsHow the system operates in practice
Projects and codeRepositories, build and test setup, context
The factoryRunning work, schedules, Sentinel, reports
Quality and reviewGates, findings, evidence, browser tests
Organisation settingsMembers, keys, policy, retention
Billing and capacitySlots, credits, usage, invoices
IntegrationsSource control, chat, MCP, evidence, hooks
ReferenceGlossary, statuses, limits, troubleshooting

Three key points to know straight away

Agent slots determine how many Tasks can run simultaneously — not the speed at which a single Task executes. The duration of a single Task depends on the size of the change and your test suite. See Capacity and agent slots.

NEEDS_HUMAN_REVIEW is not a failure. It indicates that the work has reached a decision point requiring your input. Respond to it, and the Task will continue. See Task statuses.

Something not behaving as expected

Start at the troubleshooting index, which matches symptoms to appropriate solutions.