Quickstart

arbe is a CLI for running and tracking agent work. This page gets you from nothing to a first successful interaction using the released binary — no repo checkout, no Homebrew, no build step.

Pick your platform, install, authenticate, run one command. About five minutes.

1. Pick your target

Platform	Target
Apple Silicon	`darwin-arm64`
Intel Mac	`darwin-x64`
Linux (x86_64)	`linux-x64`

Linux on ARM is not yet supported. See releases for the full artifact contract.

2. Download

The latest channel always points at the newest release. Set TARGET for your platform:

TARGET=darwin-arm64   # or darwin-x64, linux-x64

curl -fLO https://downloads.arbe.0sk.ar/arbe/latest/arbe-$TARGET.tar.gz
curl -fLO https://downloads.arbe.0sk.ar/arbe/latest/SHA256SUMS

latest/ is mutable — fetch the tarball and SHA256SUMS together so they describe the same build. If you need to pin to a specific version, see releases.md.

3. Verify the checksum

# Linux:
grep "arbe-$TARGET.tar.gz" SHA256SUMS | sha256sum -c -
# macOS:
grep "arbe-$TARGET.tar.gz" SHA256SUMS | shasum -a 256 -c -

Expect arbe-<target>.tar.gz: OK. If it fails, do not run the binary — re-download both files together.

4. Extract and install

tar -xzf arbe-$TARGET.tar.gz
mkdir -p ~/.local/bin
mv arbe ~/.local/bin/   # or any directory on your $PATH

If ~/.local/bin is not on your $PATH, add it to your shell rc:

export PATH="$HOME/.local/bin:$PATH"

5. Verify the install

arbe --version

Expect something like:

arbe 0.1.0 (commit 34b67d0, 2026-04-13)

The version, commit SHA, and build date are baked into the binary at compile time. Use this output in bug reports — it identifies exactly which build you have, even though latest itself moves.

6. Authenticate

arbe login

This opens a browser to complete auth and stores a token locally. For CI or non-interactive setups, use arbe login --token <value>.

Login is mandatory for any command that creates a run (arbe chat, arbe loop, arbe do). There are no anonymous fallbacks — every run belongs to a house, and every house has an owner.

7. First run

Check status to confirm the CLI is talking to the backend:

arbe status

You should see your account, active sandboxes (none yet), and an empty or short ready-task queue.

Open a one-shot chat to exercise the agent path end-to-end:

arbe chat "hello — what can you help me with?"

For an interactive session, run arbe chat with no argument.

Updating

For a released binary install, use the built-in updater:

arbe update

To check without installing:

arbe update --check

The CLI also does a passive best-effort check on normal interactive runs and prints a short notice when a newer version exists.

If you installed from source with bun link, the updater refuses and tells you to refresh your checkout instead. To stay on a specific released build, pin to a versioned URL (arbe/<version>/arbe-<version>-<target>.tar.gz) instead of latest/.

What next

CLI reference — every command and flag
Surfaces — what you can do from CLI, HTTP, and JS
Tasks — the repo-native task graph that drives day-to-day work
Releases — artifact contract, versioning policy, how releases are built