# NotusCI > CI for coding agents. `verify` runs this repository's GitHub Actions workflow on your uncommitted changes in a clean Linux container and returns typed JSON. ## Set up this repository and verify Run every command from the repository root. Each command prints one JSON object on stdout. On error it prints `{"error", "code", "next"}` on stderr and exits nonzero: run `next` if it is a command, otherwise tell the human `error`. 1. Run `npx -y notusci@latest init`. 2. If the output has `"status": "action_required"`, show the human `action.url` and `action.code` and say: "Open this link, check the code matches, approve, and install the NotusCI GitHub App on this repository." Then run `npx -y notusci@latest init` again. Each run waits up to 90 seconds. Repeat until `"status": "ready"`. The link is on NotusCI's API host, `notusci-api.binh-08d.workers.dev`, which also serves the MCP server; that is expected. When GitHub asks which repositories, recommend All repositories: new repositories then work without another visit. 3. Run `npx -y notusci@latest verify` with a command timeout of at least 10 minutes. It uploads only what GitHub doesn't have yet: unpushed commits, uncommitted changes and untracked files that are not ignored. 4. If the output has `"ready": false`, run `npx -y notusci@latest wait VERIFY_ID` until `ready` is true. 5. Show the human `conclusion`. For each entry in `failures`, show `file`, `line` and `message`. 6. After a failure, fix the code and run `npx -y notusci@latest rerun-failed VERIFY_ID`. Pull requests from forks by non-collaborators wait for a one-time owner approval per contributor: when the human asks, run `npx -y notusci@latest approve RUN_ID` (or MCP `ci_approve`). If the workflow reads `${{ secrets.NAME }}`, the human sets it with `printf %s "$VALUE" | npx -y notusci@latest secret set NAME` (stdin only; never put the value in argv or chat). Only push runs receive secrets; local verifies see `''`. To run NotusCI on every push and pull request, run `npx -y notusci@latest repo set --push-workflow .github/workflows/ci.yml` (or MCP `ci_repo_set`). Every repo setting, with a description and an example, is listed at https://ci.notusworks.com/api/settings; set any of them with `ci_repo_set({ repo, settings })` or `npx -y notusci@latest repo set --settings JSON`. A push receipt's `hints`, when present, name a setting that would have helped that push and give the exact call. `npx -y notusci@latest api METHOD PATH [--data JSON]` calls any API path with the saved login; never read the token out of `auth.json`. A ship refused with `migration_approval_required` lists the migration files; review them, then run its `next` command (or MCP `ci_migrations_approve`). `init` also registers the NotusCI MCP server in Claude Code, Cursor and Codex. Use an already-available MCP connection directly; clients may require a new session to load newly registered configuration. MCP supports `ci_verify`, `ci_rerun_failed`, `ci_search_logs` and opted-in failed-filesystem `ci_exec`; see the agent docs for bounds and idempotency. ## Errors - `not_logged_in`: run `npx -y notusci@latest init`. - `app_not_installed`: run `npx -y notusci@latest init`; the human must install the App on this repository. - `not_account_owner`: tell the human another GitHub user owns this account on NotusCI. - `workflow_required`: run `verify --workflow PATH` with one of `candidates`. - `cap_reached`: tell the human the monthly limit is reached and when it resets. Do not retry. - `payment_required`: the 300-minute trial is used up. Live billing is currently disabled; stop and report that limitation. On a deployment with billing configured, CLI 0.1.2 and later support `notusci billing` for the owner’s Stripe-hosted setup. - `billing_unavailable`: this deployment cannot start billing setup. Do not ask for card data or repeatedly retry Checkout. - `base_unavailable`: push the branch (`git push -u origin HEAD`), or `git fetch --deepen=100 origin` in a shallow clone, then retry. - `missing_scope`: run `npx -y notusci@latest login --scope SCOPES` with the `scopes` given. - `unknown_setting`: use one of `valid`; https://ci.notusworks.com/api/settings describes each. ## Docs - [Agents](https://ci.notusworks.com/docs/agents.md): commands, MCP tools, scopes, result fields, production approval - [Repo settings](https://ci.notusworks.com/api/settings): JSON, each setting with a description and an example - MCP server: `https://notusci-api.binh-08d.workers.dev/mcp` (streamable HTTP, OAuth)