CoroidSu AI software factory

Your assistant sets up Coroid. You make the decisions.

We onboarded an existing product the way a new customer would, and timed every step. Claude Code followed Coroid's setup runbook, the person did the steps only a person can do, and Coroid ran the first task to a pull request.

Start freeGet the setup prompt
From sign-up to the first pull request
1 h 44 min
From submitting the first task to its pull request
25 min
Model cost of the first task, on the Free plan's included models
0 US$
Acceptance criteria the first task met
5 of 5

Recorded in production on 4 de noviembre de 2026: a new organization on the Free plan, and a private copy of Coroid Expo, a 98.000-line product built with Claude Code and Codex.

Two ways to set it up.

Both reach the same place: a project Coroid can build and test, and a first task running. The recording took the first way.

Hand it to your assistant

Open Claude Code, Codex or Cursor in your repository and give it this prompt. It follows the runbook step by step, does the inspection and the checking, and stops for you at every step only a person can do: signing up, granting access and approving changes.

The setup prompt
Set up Coroid for this repository. Follow the runbook at
https://coroid.ai/docs/export/en-US/getting-started/assistant-setup.md
step by step. Ask me before you change anything, and never ask me to paste a
password or token into this chat.

Read the runbook

Do it yourself

The same steps in the portal, with a guide for each.

  1. Create your account and organization
  2. Connect your code
  3. Create your first project
  4. Write an AGENTS.md for your agents and Coroid's
  5. Run your first task
  6. Review and merge the result
Start with the getting-started guide

Every step, with the time it took.

Clock times are from the recording, in UTC. Each step names who did it.

  1. Person

    Sign up and create the organization

    The organization stayed on the Free plan throughout: one project, the owner only, and Coroid's included models.

  2. until 21:34
    AssistantPerson

    Check the repository and draft AGENTS.md

    The assistant cloned the repository into a clean container, the way every Coroid task starts, and ran the install, the checks, the build and the tests. It found 2 gaps every task would hit: a test that needs Helm, and timeouts when packages run their tests in parallel. It proposed fixes, and a “Working in Coroid” section for AGENTS.md.

    At 21:52 the person answered its 3 questions, and it started on the setup branch.

    The first task did not wait for it. Coroid read the repository's existing AGENTS.md, kept the change inside the one package the task named, and ran that package's tests.

  3. Person

    Connect GitHub

    The person installed the Coroid GitHub App on the GitHub organization that owns the repository. The App is what lets Coroid check the pull requests your team opens.

    Blocker, fixed since

    This is where the time went. Coroid twice said GitHub had not confirmed the authorization, without saying why, and the install took 3 attempts. The walkthrough found 5 onboarding bugs, this one included, and each one is fixed.

  4. PersonCoroid

    Create the project

    The person picked the repository, kept it Synced so Coroid opens pull requests, and left “Check the pull requests your team opens” ticked, as it is by default with the GitHub App. Coroid cloned and indexed the repository without being asked.

    Coroid took its first anti-slop baseline of the main branch in 1,5 minutes, so later checks block only what a change introduces.

    From then on, Coroid Quality Control and Coroid Review checked the team's pull requests too: the assistant's setup pull request, and a Dependabot one that was already open.

    New project
    Connect a repository to start automating your development workflow with autonomous workstations
    RepositoryBrowse RepositoriesConnect with URL
    coroid-expoRepository selectedPrivate
    Default Branch
    main
    Repository mode
    Choose whether Coroid may write to GitHub.
    SyncedCoroid pushes branches and opens pull requests on GitHub.
    Local onlyCoroid only reads from GitHub. Branches, commits and reviews stay in Coroid.
    Check the pull requests your team opensCoroid Quality Control runs this project's checks on every pull request, including those your developers open with their own tools, and Coroid Review comments on the changes.
    CancelNew project
  5. until 22:31
    PersonCoroid

    Submit the first task

    The person submitted it from New Work: stop the content check reporting en-GB, which is derived from en-US, as 5039 untranslated keys. Setup had found the gap. Coroid's Architect planned the change, then the Developer, QA and Reviewer agents built, verified and approved it.

    • Developer –
    • QA –
    • Reviewer –
    Nuevo trabajo.
    Describe el resultado deseado. Coroid encontrará la forma correcta de entregarlo.
    Crear como
    AutomáticoTareaPlan
    Coroid elige el resultado, o tú puedes decidirlo.
    Proyecto
    coroid-expo
    Título del trabajo
    Stop the content check counting en-GB as untranslated
    Resumen

    content:check reports en-GB as untranslated for 5039 keys, but en-GB is derived from en-US, so those keys are not missing. Stop reporting en-GB, and keep flagging real untranslated text in the other locales.

    Done when: en-GB is no longer reported, untranslated text in the other locales is still flagged, and it is still an error under --strict.

    Adjuntar archivos
    Siguiente: cualificación. Aún no se ha creado nada.Continuar
    Recreation. It shows the descriptive title we would give the task now; the real one went in as “testing”.
  6. Coroid

    The first pull request

    25 minutes after the task went in, with no retries: 2 files in one package, +81 / −11. It met 5 of 5 acceptance criteria, QA passed it and named what it could not check, and the Reviewer approved it. Coroid Quality Control and the repository's own CI passed, and the person merged it the next morning.

    Every model call ran on the Free plan's included models, so the task cost 0,00 US$.

    Checks on the pull request
    • Coroid Quality ControlPassed
    • The repository's own CIPassed

Who did what.

The person did only what needs a person. The assistant did the reading and the checking, and Coroid did the work.

Person

The person

  • Signed up
  • Installed the GitHub App
  • Created the project
  • Answered the assistant's 3 questions
  • Submitted the first task
  • Answered one merge question
  • Retitled and merged the first pull request
Assistant

The assistant, Claude Code

  • Asked the runbook's planning questions
  • Checked a clean clone: install, type check, lint, format, content checks, build and tests
  • Fixed the 2 gaps it found in a setup pull request
  • Wrote the “Working in Coroid” section of AGENTS.md
  • Merged its setup pull request once the person agreed
  • Wrote the setup record
Coroid

Coroid

  • Cloned and indexed the repository on its own
  • Took the first anti-slop baseline
  • Checked the team's pull requests with Quality Control and Review
  • Planned, built, tested and reviewed the first task
  • Opened the first pull request

The assistant's time is your repository's.

Coroid's part ended with the first pull request. The assistant ran on: the repository's AGENTS.md asks for its full local check before any merge, so the assistant ran it for a 3-file change, and that took 95 minutes. Then it waited overnight for the person's answer. That is the repository's own rule at work, not a Coroid step, so we count it separately.

Coroid's count: sign-up to the first pull request
1 h 44 min
The assistant's own running
about 4 h 30 min
The assistant waiting for the person
7 h 51 min

What we would tell the next team.

Notes from the recording, for your own setup.

Give the first task a real title
The first task went in titled “testing”, and Coroid named the pull request after it. The person renamed it before merging. Use the title you want in your history.
Check the specification's examples
One rule in the first task's specification rested on a guess from a key's name. The rule was right, but it changed nothing. Read a specification's examples against your code before the work runs.
Know what your merge rules cost
Setup takes as long as your repository's own rules: if AGENTS.md asks for a full local test run before any merge, the assistant runs it. Tell your assistant up front how long your checks take.

What this recording does not show

  • A team's onboarding. It ran on Free, with one project and the owner only; inviting reviewers needs Professional.
  • The assistant working through Coroid's MCP server. That runbook step is optional, and it was skipped.
  • A release. The copy has no deploy target.

Continue in the docs.

The guides this recording followed, and the runbook your assistant reads.

Set up your own repository.

Start on the Free plan, with the same included models the recording used, and hand the prompt to your assistant.

Start freeRead the getting-started guide