One-line setup (size labels)

• Getting started
• One-line setup (size labels)
• Which jobs can move
• Fallback & rollback
• Build cache (Nx / Turborepo)
• Get started with your box
• Connect Claude (MCP)
• Billing
• Usage analytics & your data
• Data processors for Code review and Insights
• Help

After you install the compiler.dev GitHub App on a repository, you can move a job with one line:

jobs:
  test:
    runs-on: compiler-8cpu

• Sizes: compiler-2cpu, compiler-4cpu, compiler-8cpu and compiler-16cpu. compiler.dev sees the label in the workflow_job webhook and provisions a machine of that size for the job.
• Needs the GitHub App: the App must be installed on the repository. Without it, nothing picks the job up and it stays queued.
• No automatic fallback: with a size label, the job waits for a compiler.dev runner. It does not move back to GitHub-hosted or your own runners if compiler.dev is unavailable, or if your credit or monthly cap runs out. Add credit or raise the cap and the waiting job starts.
• The older label still works: [self-hosted, Linux, compiler-ci] keeps working.

When to use the routed setup instead. Use the setup pull request when you want automatic fallback, a gradual rollout (10%, 25%, 50% or 100% of pull requests) or Try safely comparison mode, where a copy of your jobs runs on our machines while your results still come from your own runners. With the routed setup, if compiler.dev cannot take a job, or your credit or monthly cap runs out, the job runs on the runner it used before you switched, whether that is GitHub-hosted or your own.

Same rules as everywhere: Linux build and test jobs only. Deploy and publish jobs, Windows, macOS, ARM, GPU and forked pull requests stay on your runners (see Which jobs can move).