Add a Direct macOS runner

Every Oore build runs in a separate Direct macOS runner process.

The Complete profile setup enrolls one Runner on the control-plane Mac. Add another Runner only when a build needs a different Mac or toolchain.

Repository commands use the Runner account’s host permissions. A Direct runner is not a hostile-code sandbox.

What you need

• A Mac that supports the guided v0.1.42 lifecycle.
• A ready Complete or Control plane profile.
• A protected path to the control plane.
• An Owner or Admin Oore API token.
• The required repository and platform tools on the Runner Mac.

Use the Complete profile Runner

The Complete profile setup installs and verifies the local Runner service.

If that setup stopped, correct the reported problem. Then run:

oore setup

Oore resumes the recorded Complete profile. It keeps the existing access choice and verifies the local Runner.

Add a Runner profile

On the new build Mac, install the CLI:

curl -fsSL https://oore.build/install | bash

Then select the Runner profile:

~/.oore/bin/oore install --profile runner

For Complete, use its local web UI. For Control plane, connect a Web node or a configured hosted UI first.

Use that browser client to sign in to Oore. Open Settings > API tokens and create an Owner or Admin token.

Copy the token when Oore shows it. Supply that token and the ready control-plane URL during Runner setup.

Oore registers the Runner, stores its Runner credential, starts the macOS service, and verifies the service.

For headless setup, use a private setup file. See the oore setup reference.

Add build tools

Install only the tools that this Runner needs:

• Install Git before any repository build.
• Install a JDK and the Android SDK for Android builds.
• Install Xcode for iOS or macOS builds.
• Add the required credentials for signed artifacts.

Missing build tools do not block Runner setup. Oore reports the missing tool on each affected build.

Verify the result

Open Settings > Runners. Make sure that the new Runner is online.

Turn on Allow approved repositories. Then run a small build from an approved repository.

Make sure that the new Runner claims the build.

Troubleshooting

If registration fails, make sure that the control plane is ready and reachable through the protected path.

Create a current Owner or Admin token under Settings > API tokens. Then run oore setup again.

If work remains queued, inspect the Runner state in the UI. Make sure that Allow approved repositories is on.

Next step

Learn the Runner trust boundary. Then monitor Oore.