Install Oore

The download script installs only the oore CLI. It does not install services, Flutter, or the web UI.

After you choose a role with oore install, device setup starts.

The guided v0.1.42 lifecycle supports macOS on arm64 and x86_64.

Published Linux web archives are standalone assets. They are not a guided Web node installation.

1. Install the CLI

Run the script as your normal user:

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

The script verifies the signed stable release index and signed checksum manifest.

It then verifies the CLI archive SHA-256 against that manifest.

A missing or invalid signature stops the installation before any file changes.

It installs the CLI under ~/.oore and can add ~/.oore/bin to your shell path.

The script never requests administrator access. Do not prefix it with sudo.

If the script changes your path, open a new terminal or run the printed source command.

For guided setup, run:

oore install

Oore explains these five roles before it changes the device:

Role	Purpose
Complete	Run the control plane, local web UI, and builds on this device.
Control plane	Manage pipelines and runners without a local web UI or runner.
Runner	Run builds for a control plane on another device.
Web node	Serve the web UI for a control plane on another device.
CLI only	Use the CLI without local Oore services.

Complete is the default interactive choice.

For an SSH script or another headless task, select the role explicitly:

oore install --profile runner

Use --plan to review the component plan without changes:

oore install --profile runner --plan

Oore downloads the matching release bundle. It installs only the components for the selected role.

Complete and Control plane currently share one full bundle. Web node uses a web-only bundle. Runner and CLI only reuse the bootstrap CLI.

An interactive install continues to oore setup. A non-interactive install stops after component installation.

For a non-interactive installation, run setup with explicit values or a configuration file:

chmod 600 ./oore-setup.yaml
sudo -v
oore setup --config ./oore-setup.yaml

Service profiles request administrator access only during setup. Oore shows the setup plan before that request.

Without an interactive terminal, Oore never opens a password prompt. Run sudo -v before setup instead.

The CLI only profile does not need administrator access.

oore version

Setup must end with <Profile> setup is ready. Oore prints this message only after final service verification.

Use oore status to inspect the connected control plane.

For a remote Runner or Web node, pass --daemon-url <URL>.

For release channels and custom paths, read the installer reference.