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
Your developers
With Claude Code, Codex or Cursor
Work in their own editor and open a pull request.
Pull requestCoroid
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
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.mdand 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.
AGENTS.mdCommands
Install with `npm ci`. Test one package with `npm test -w api`.
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`.
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`.
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.
- 组织默认配置3 个项目正在采用此配置2 / 5
- 门店页面自定义设置4 / 5
- 文档站点遵循默认配置2 / 5
- 计费 API遵循默认配置2 / 5
- 移动应用遵循默认配置2 / 5
- Anti-slop如果变更导致测试用例失效、错误被忽略、占位符被直接发布或产生结构性技术债务，系统会将该变更退回。
- 单元测试系统会在每次变更后，自动查找并运行代码库中的单元测试。
- 浏览器测试2 / 3与默认配置不同系统会针对变更内容执行指定的浏览器操作流程测试。
- 翻译与默认配置不同该检查项会验证变更后的字符串是否已被翻译，同时确认其中的占位符及复数形式是否匹配。
- 代码库校验系统可运行用户自定义的命令，例如代码格式化、文件大小检查、数据库迁移、集成测试以及安全扫描等。
- 全面 QA全面校验开启Thorough QA后，系统会根据规范生成实时的验证证据与截图；若未开启，则采用标准QA流程。
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.
https://api.coroid.ai/mcpclaude mcp add --transport http --scope user \ coroid https://api.coroid.ai/mcp /mcp
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/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.
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.
客户希望保存搜索结果，并在有新匹配项时收到通知。首个版本仅支持发送邮件提醒，每个账号最多可保存10条搜索记录。
源自获批的意图
- 发起请求人
- Maya Lindqvist
- 负责人
- Maya Lindqvist
- 审批人
- Sam Okafor产品负责人
- Priya Shah技术审批人
- 已批准Sam Okafor产品负责人
这是客户提出的需求。推送通知功能可延后实现。
- 已开始Maya Lindqvist
需在春季营销活动前上线。
- 已批准Maya Lindqvist自动
交付合同根据获批的计划自动获批。
- QA结论已通过QA智能体
全部6项验收标准均已验证通过。
- 已合并Sam Okafor
9c1e4a7f023f2b7d1a9c智能体提交coroid/saved-search-alerts9c1e4a7f02合并提交
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 2026年11月2日, 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 2026年11月2日, times in UTC
- 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.
- Claude CodeOpens #201.
- CoroidFiles a task over MCP from the same session: add tests to the studio app, with 5 acceptance criteria.
- Claude CodeQuality Control says go ahead, with 4 new findings as advice. Coroid Review approves.
- CoroidA person approves the start. The Coordinator plans 8 criteria and keeps the 5 requested word for word.
- Claude CodeFixes 2 of the findings and answers the other 2 on the pull request.
- CoroidQA: 8 of 8 criteria pass. Quality Control says go ahead.
- Claude CodeThe checks pass again on the new commit.
- CoroidThe Reviewer approves, and Coroid opens #202.
- BothBoth merged on a person’s go-ahead.
| 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 660万 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.