Keep Claude Code, Codex and Cursor. Add the factory.

Your developers keep the agents they already use. Coroid runs the factory around all of them: every pull request checked to the same standard, traced to the request behind it, and released the same way.

Start building Connect your editor

Start
Your developers
With Claude Code, Codex or Cursor
Work in their own editor and open a pull request.
Pull request
Coroid
From New Work, an issue, a schedule or an MCP call
Plans, builds, tests and reviews the task, then opens a pull request.
Pull request
Check
Coroid Quality Control and review
One policy and the same anti-slop rules for every pull request
Record
Made outside Coroid
Its author and date, and the checks run on its pull request
Made by Coroid
The request, the decisions, QA’s verdict and the approvals
Ship
Releases
The same gates and approvals for every version

Two ways of working meet one quality barPull request checks need the Coroid GitHub App and run once they are switched on for the project.

Do your developers have to switch tools?

No. They keep their editor, their agent and their branches. Coroid adds a second way to get work done, and checks both the same way.

Coroid works on its own branches. It never commits onto a developer’s branch.
Coroid’s agents read the same instruction files your developers’ agents read: AGENTS.md, CLAUDE.md and Cursor’s rules.
They skip the Git workflow written for local agents. Coroid creates the branch, commits, pushes and opens the pull request itself.
Nothing merges until a person approves it.

Write one AGENTS.md for both

AGENTS.md

Read by every agent

Commands

Install with `npm ci`. Test one package with `npm test -w api`.

Read by Coroid’s agents

Working in Coroid

When you run inside Coroid, Coroid creates the branch, commits, pushes and opens the pull request. Change files only, and skip “Git workflow” below.

Before you finish, run `npm run validate`.

Read by your developers’ agents

Git workflow (local agents)

Branch from `main`, in your own worktree.

Commit messages end with your assistant’s co-author line.

Run `npm run check:local`, then open the pull request with `gh pr create`.

An example AGENTS.md, written the way the guide recommends

Is a pull request from Claude Code held to the same standard?

Yes, once pull request checks are on. The checks you set in Quality Control run on every pull request, whoever or whatever wrote it.

Coroid Quality Control: Runs the project’s checks, anti-slop rules included, and reports them as one check on GitHub, with each finding marked on its line. Anti-slop blocks only what the change introduced.
Coroid Review: Coroid’s Reviewer reads the pull request and comments on the lines it questions, following your review rules. It advises by default; blocking is your choice. Coroid’s own pull requests were already reviewed inside their task.
Coroid Security: Checks each pull request for leaked credentials, made-up or malicious packages and removed access checks, and shows what the change introduced.

Switch it on

Install the Coroid GitHub App for the repository. Pull request checks do not run through a token connection.
Create the project. With the App installed, “Check the pull requests your team opens” is already ticked.
For a project you already have, switch on pull request checks in Quality Control.

How pull request checks work

Quality Control

Choose what each project is checked for. A change applies to new work as soon as you make it.

FindingsAnti-slop rule library

Organisation default3 projects follow it2 of 5

Projects4

StorefrontOwn setup4 of 5
Docs siteFollows default2 of 5
Billing APIFollows default2 of 5
Mobile appFollows default2 of 5

StorefrontOwn setup

It runs at task QA, pull requests and release validation.

Checks on every change

A change that fails a check goes back to the Developer before anyone reviews it.

Anti-slopSends a change back when it weakens tests, swallows errors, ships placeholders or adds structural debt.Adjust
Unit testsFinds and runs the repository's unit tests on every change.Adjust
Browser tests2 of 3differs from defaultRuns your browser journeys against the change.Adjust
Translationsdiffers from defaultChecks that changed strings are translated and that their placeholders and plural forms match.Adjust
Repository checksRuns your own commands, such as formatting, file size, migrations, integration tests and security scans.Adjust

Thorough QAThoroughQA collects live evidence and screenshots against the Specification. When it is off, work gets Standard QA.Adjust

The Quality Control view is a recreation of the Coroid portal. Its projects and settings are illustrative.

Can developers use Coroid without leaving their editor?

Yes. Coroid is an MCP server. Claude Code, Codex and Cursor connect with OAuth or an access token, and see only the projects and tools the connection allows.

anti_slop_rules: The project’s anti-slop rules, and a snippet that states them in AGENTS.md, so a local agent knows the bar before it writes a line.
anti_slop_scan: Scans a branch Coroid has synced, before the pull request exists. It only reads. Quality Control’s verdict on the pull request is still the one that counts.
create_taskstart_task_execution: Hands Coroid a task from the same session and follows it. Starting it waits for approval unless an automation policy covers it.
explain_code: Shows which commit last changed a line and, for a commit Coroid made, the task behind it.

Set up Coroid in your editor

https://api.coroid.ai/mcp

Claude Code

claude mcp add --transport http --scope user \
  coroid https://api.coroid.ai/mcp
/mcp

Codex

codex mcp add coroid --url https://api.coroid.ai/mcp
codex mcp login coroid \
  --scopes mcp.read,mcp.work.write,mcp.execute,mcp.delivery

Cursor

// ~/.cursor/mcp.json
{ "mcpServers": {
    "coroid": { "url": "https://api.coroid.ai/mcp" } } }

Approve the connection in your browser when the client asks, and choose which projects it may reach.

Connecting Coroid, as the MCP guide shows it

Can you tell later which way a change was made?

Yes. Provenance keeps the two apart, from the pull request down to a single line of code.

Made by Coroid: The request and who made it, the decisions and who approved them, the plan, QA’s verdict on each criterion and the reviewer’s approval, linked from the pull request.
Made outside Coroid: No task records why the change was made, so you see its author and date. Coroid keeps the Quality Control runs and anti-slop scans of its pull request.

Every commit Coroid makes carries a Coroid-Task or Coroid-Plan trailer, so git blame leads back to the request.

How provenance works

TaskPlanSaved searches with email alerts

Email alerts for saved searches

ProvenanceOrigin, requester, owner, decisions and delivery

MarkdownJSON

Customers want to save a search and hear when new items match it. The first version sends email alerts only, for at most 10 saved searches per account.

From the approved intent

Requested by

Maya Lindqvist

Owner

Maya Lindqvist

Approved by

Sam OkaforProduct owner
Priya ShahTechnical approver

Origin

Prepare WorkRequested via chat5 Oct

Open conversation

Decisions

ApprovedSam OkaforProduct owner6 Oct
This is what customers asked for. Push notifications can wait.
StartedMaya Lindqvist7 Oct
Ship it before the spring campaign.
ApprovedMaya LindqvistAutomatic7 Oct
Delivery contract approved automatically from the approved plan.
QA verdictPassedQA agent8 Oct
All 6 acceptance criteria verified.
MergedSam Okafor9 Oct

Delivery

Pull requests

Pull request #142Merged bySam Okafor9c1e4a7f029 Oct

Commits

3f2b7d1a9cAgent commitcoroid/saved-search-alerts8 Oct
9c1e4a7f02Merge commit9 Oct

The provenance panel is a recreation of the Coroid portal. The people and work in it are illustrative.

Has this run on a real repository?

Yes. On 2 November 2026, on Coroid Expo, a 98,000-line product built with Claude Code and Codex. Claude Code, working for Patrik, Coroid’s founder, opened one pull request. From the same session it asked Coroid over MCP for tests, and Coroid opened the other.

Coroid Expo’s repository is private, so its pull requests are named here, not linked.

Both pull requests on 2 November 2026, times in UTC

11:12
Claude CodeBranches from main for an open item in the voice runbook: sign a voice token only for a guest who is actually in the room.
11:40
Claude CodeOpens #201.
11:40
CoroidFiles a task over MCP from the same session: add tests to the studio app, with 5 acceptance criteria.
11:41–11:51
Claude CodeQuality Control says go ahead, with 4 new findings as advice. Coroid Review approves.
11:50
CoroidA person approves the start. The Coordinator plans 8 criteria and keeps the 5 requested word for word.
11:57
Claude CodeFixes 2 of the findings and answers the other 2 on the pull request.
12:07–12:15
CoroidQA: 8 of 8 criteria pass. Quality Control says go ahead.
12:10
Claude CodeThe checks pass again on the new commit.
12:21
CoroidThe Reviewer approves, and Coroid opens #202.
13:19
BothBoth merged on a person’s go-ahead.

The two pull requests side by side
Measure	#201, from Claude Code	#202, from Coroid
Time to the pull request	28 min from the branch	31 min from the start
Change	16 files, +368 −90	3 files, +213 −1
Criteria verified	3 of 3	8 of 8
Quality Control findings in the code	4 as advice, 2 fixed	None
Model spend	A Claude Code subscription, not metered by Coroid	US$0.26 for 6.6m tokens

Quality Control advised; it did not block. Two of its findings were right and were fixed, and the developer answered the other two on the pull request.

Both shipped in Coroid Expo 0.1.1, released through Coroid after a person approved it.