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개
- 안티-슬롭테스트가 약화되거나 오류가 숨겨지고, 임시 코드가 배포되거나 구조적 부채가 추가되는 경우 해당 변경 사항을 다시 반려합니다.
- 단위 테스트모든 변경 사항에 대해 저장소 내의 단위 테스트를 자동으로 찾아서 실행합니다.
- 브라우저 테스트2개 중 3개기본 설정과 다름변경된 내용을 기반으로 브라우저 상에서 사용자 흐름을 실행하여 검증합니다.
- 번역기본 설정과 다름변경된 문자열이 올바르게 번역되었는지, 그리고 플레이스홀더와 복수형 표현이 일치하는지를 확인합니다.
- 저장소 검사서식 지정, 파일 크기 검사, 마이그레이션, 통합 테스트 및 보안 스캔 등 사용자가 지정한 커맨드를 직접 실행합니다.
- 철저한 QA철저함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개의 저장된 검색어에 대해서만 이메일 알림을 발송합니다.
승인된 의도에서 추출됨
- 요청자
- 마야 린드크비스트
- 소유자
- 마야 린드크비스트
- 승인자
- 샘 오카포르제품 소유자
- 프리야 샤기술적 승인자
- 승인됨샘 오카포르제품 소유자
이것이 고객이 요청한 내용입니다. 푸시 알림은 나중에 처리해도 됩니다.
- 시작됨마야 린드크비스트
봄 캠페인 전에 배포해야 합니다.
- 승인됨마야 린드크비스트자동
승인된 계획에 따라 배포 계약이 자동으로 승인됩니다.
- QA 판정통과QA 에이전트
6개의 수락 기준 모두 확인되었습니다.
- 병합됨샘 오카포르
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.