CLI install

`mbr` is the command surface for humans and agents.

The CLI is the main human and agent surface for Move Big Rocks. Use it to bootstrap owned runtimes, inspect work, evaluate fit, and operate real instances through one explicit contract.

Open install.sh Open the CLI tour

Agent-first route: Start at /agents, inspect /docs/cli, and drop into this page when you need proof, detail, or rollout guidance.

Agent-first route

Humans should usually delegate first-pass evaluation to an agent. Agents should start at /agents, use /docs/cli as the official product tour, and open /docs/graphql only when needed.

Agent-ready surface

Start with the CLI, not browser guesswork.

Preferred route: /agents, then /docs/cli, then /docs/graphql only when lower-level integration details matter.

$ mbr spec export --json
$ mbr auth whoami --json
$ mbr queues list --workspace ws_preview --json

Open GraphQL reference | Open schema.graphql

Preferred command

The preferred CLI command is `mbr`.

Machine-readable install metadata

Public bootstrap JSON and release metadata tell agents where the install surface lives.

Preview source-build install

The current installer clones the public platform repository and builds the CLI from source.

Core deployment artifacts stay separate

The CLI preview install is not the same thing as the tagged core release artifacts instance repos pin for production.

Proof

Contract docs/RELEASE_ARTIFACT_CONTRACT.md Defines the pinned artifact contract that instance repos consume.
Release platform tags Public tagged core releases that agents can inspect directly.
Build .github/workflows/_build.yml Builds services, migrations, and manifest OCI artifacts and records digests.
Release .github/workflows/production.yml Tags releases, ties git tags to OCI artifact digests, and records cross-reference details.
Implementation instance-template/mbr.instance.yaml Shows where pinned release refs live in the private instance control plane.

Same surface for humans and agents

Use the same command surface for evaluation, operation, and automation.

Quickstart

Install the CLI, then continue into evaluation.

The current public preview install clones the platform repository and builds `mbr` from source, so `git` and Go 1.26+ need to be present first.

macOS and Linux

Run the public shell installer.

$ curl -fsSL https://movebigrocks.com/install.sh | sh

Windows PowerShell

Run the public PowerShell installer.

PS> Invoke-RestMethod https://movebigrocks.com/install.ps1 | Invoke-Expression

Then continue

Create a private instance repo or target an existing runtime.

$ gh repo create acme/mbr-prod --private --template MoveBigRocks/instance-template --clone

Why the CLI matters

A stable command surface is one of the clearest ways to make a product agent-ready.

The CLI is not just convenience. It is part of the public machine contract for evaluation and operation.

Agent-friendly

Agents can discover, install, and use `mbr` without being forced into brittle browser automation.

Human-friendly

Humans get a stable command surface for owned-runtime bootstrap, inspection, and production workflows.

Shared semantics

The CLI mirrors the same operational model described on `/agents`, `/core`, and the docs.

CLI install versus core deploy

The CLI install path and the production core release path are different on purpose.

Agents should not confuse the current CLI preview installer with the core release surface used for self-hosted production. Today the public installer builds `mbr` from tagged source. Production core deploys pin the tagged `mbr-services`, `mbr-migrations`, and `mbr-manifest` artifacts in the private instance repo.

Proof bundle

Contract docs/RELEASE_ARTIFACT_CONTRACT.md Defines the pinned artifact contract that instance repos consume.
Release platform tags Public tagged core releases that agents can inspect directly.
Build .github/workflows/_build.yml Builds services, migrations, and manifest OCI artifacts and records digests.
Release .github/workflows/production.yml Tags releases, ties git tags to OCI artifact digests, and records cross-reference details.
Implementation instance-template/mbr.instance.yaml Shows where pinned release refs live in the private instance control plane.

The CLI preview install is for local human and agent tooling.
Tagged core artifacts are for deployed runtimes, not for the CLI binary itself.
Instance repos pin those core refs in `mbr.instance.yaml` and deploy them without rebuilding core.

References

Canonical next surfaces.

Each link goes to the next authoritative page, reference, or support surface.

Let agents inspect the CLI-first surface. Let humans decide trust, rollout, and boundaries.

Start from /agents, use /docs/cli as the official product tour, inspect /resources for source and proof, and review /security before making deployment or data-handling decisions.

Open /agents Open resources