Miosbot Code

Status: rolling out. Miosbot Code is built into the engine and switches on in an update after launch. It needs a GitHub account connected to Miosbot.

What it does

Miosbot Code is the coding profile of Miosbot. Describe a tool you want, or label a GitHub issue miosbot, and Miosbot Code does the work in its own copy of the repository and opens a pull request.

• “Build a small page that lists this week’s open invoices from our spreadsheet.”
• “Fix the bug in issue 42 and open a pull request.”

How a job runs

1. The request becomes a job. Jobs survive restarts and pick up from their last checkpoint.
2. Each job gets its own working copy of the repository in a sandbox. Your GitHub token is never written into the repository.
3. Miosbot Code saves a checkpoint after each step. If a coding model hits a limit or an outage, the job continues on the next model from the last checkpoint.
4. Your project’s setup and checks run, and the results go into a proof bundle: test results, what changed, logs, and policy checks. Secrets are removed and the bundle is sealed.
5. The job ends as a pull request with the proof bundle in its description. It’s a draft by default, and always a draft when checks fail.

You stay in charge

• Miosbot Code never merges. A person reviews and merges every pull request.
• It works only in repositories on your allowlist.
• It runs a small number of jobs at a time (two by default).