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

مراقبة الجودة

حدد المعايير التي يتم وفقها فحص كل مشروع؛ يُطبق التغيير فورًا على الأعمال الجديدة بمجرد إعداده.

النتائجمكتبة قواعد مكافحة الفوضى

الإعداد الافتراضي للمؤسسة3 مشاريع تتبع هذا الإعداد.2 من أصل 5

مشاريع4

واجهة المتجرإعداد مخصص4 من أصل 5
موقع المستنداتيتبع الإعداد الافتراضي2 من أصل 5
فوترة APIيتبع الإعداد الافتراضي2 من أصل 5
تطبيق الهاتف المحموليتبع الإعداد الافتراضي2 من أصل 5

واجهة المتجرإعداد مخصص

يعمل عند فحص المهام، طلبات السحب، والتحقق من الإصدارات.

عمليات التفتيش على كل تغيير

أي تغيير يفشل في اجتياز عملية التفتيش يعود إلى المطور قبل أن يقوم أي شخص بمراجعته.

مكافحة الفوضىتُعيد التغيير إلى المصدر إذا أدى إلى إضعاف اختبارات الوحدة، أو إخفاء الأخطاء، أو نشر عناصر نائبة، أو إضافة ديون تقنية.تعديل
اختبارات الوحدةتكتشف اختبارات الوحدة الموجودة في المستودع وتنفذها مع كل تغيير يتم إدخاله.تعديل
اختبارات المتصفح2 من أصل 3يختلف عن الإعداد الافتراضيتشغل سيناريوهات التصفح الخاصة بك لتقييم التغييرات المدخلة.تعديل
الترجماتيختلف عن الإعداد الافتراضيتتحقق من ترجمة النصوص المعدلة والتأكد من تطابق العناصر النائبة وأشكال الجمع فيها.تعديل
عمليات تفتيش المستودعتنفذ الأوامر المخصصة لديك، مثل تنسيق الكود، وقياس حجم الملفات، وتشغيل اختبارات التكامل، وفحوصات الأمان.تعديل

ضمان الجودة

ضمان جودة شاملشاملتجمع أداة ضمان الجودة أدلة ولقطات شاشة حية مقارنةً بالمواصفات المحددة؛ وعند تعطيلها، يتم تطبيق إجراءات ضمان الجودة القياسية.تعديل

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

مهمةخطةعمليات البحث المحفوظة مع تنبيهات عبر البريد الإلكتروني

تنبيهات بريد إلكتروني للبحوث المحفوظة

المنشأالمصدر، مُلِّقِي الطلب، المالك، القرارات والتسليم

MarkdownJSON

يرغب العملاء في حفظ عمليات البحث وتلقي إشعارات عند تطابق عناصر جديدة معها. الإصدار الأول يرسل تنبيهات عبر البريد الإلكتروني فقط، لما يصل إلى 10 عمليات بحث محفوظة لكل حساب.

من النية المعتمدة

الجهة المطلبة

مايا ليندكفيست

المالك

مايا ليندكفيست

تمت الموافقة عليه بواسطة

سام أوكافورمالك المنتج
بريا شاهالموافق الفني

المنشأ

تحضير العملتم الطلب عبر دردشة٥ أكتوبر

محادثة مفتوحة

القرارات

تمت الموافقةسام أوكافورمالك المنتج٦ أكتوبر
هذا ما طلبه العملاء؛ إشعارات الدفع يمكن تأجيلها.
تم البدءمايا ليندكفيست٧ أكتوبر
يجب إطلاقه قبل حملة الربيع.
تمت الموافقةمايا ليندكفيستتلقائي٧ أكتوبر
تمت الموافقة على عقد التسليم تلقائيًا من الخطة المعتمدة.
حكم الاختبارتمت الموافقةوكيل الاختبار٨ أكتوبر
تم التحقق من جميع معايير القبول الستة.
تم الدمجسام أوكافور٩ أكتوبر

التسليم

طلبات السحب

طلب سحب #142تم الدمج بواسطةسام أوكافور9c1e4a7f02٩ أكتوبر

الالتزامات

3f2b7d1a9cالتزام الوكيلcoroid/saved-search-alerts٨ أكتوبر
9c1e4a7f02التزام الدمج٩ أكتوبر

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 ٢ نوفمبر ٢٠٢٦, on Coroid Expo, a ٩٨٬٠٠٠-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 ٢ نوفمبر ٢٠٢٦, 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 ٥ acceptance criteria.
١١:٤١–١١:٥١
Claude CodeQuality Control says go ahead, with ٤ new findings as advice. Coroid Review approves.
١١:٥٠
CoroidA person approves the start. The Coordinator plans ٨ criteria and keeps the ٥ requested word for word.
١١:٥٧
Claude CodeFixes ٢ of the findings and answers the other ٢ on the pull request.
١٢:٠٧–١٢:١٥
CoroidQA: ٨ of ٨ 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.

The two pull requests side by side
Measure	#201, from Claude Code	#202, from Coroid
Time to the pull request	٢٨ min from the branch	٣١ min from the start
Change	١٦ files, +٣٦٨ −٩٠	٣ files, +٢١٣ −١
Criteria verified	٣ of ٣	٨ of ٨
Quality Control findings in the code	٤ as advice, ٢ fixed	None
Model spend	A Claude Code subscription, not metered by Coroid	‏٠٫٢٦ US$ for ٦٫٦ مليون 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.