Rollout documentation

Install

For local development, run the CLI through uv from the package:

shell

cd packages/cliuv run --extra dev rollout --help

To install it into an isolated user tool environment:

shell

uv tool install ./packages/clirollout --help

Note

The hosted app also serves installer assets at /install and /cli/rollout for production distribution.

Optional extras

The base install is lightweight. Two features pull in heavier dependencies only when you opt in:

[optimize] — installs DSPy, required for GEPA optimization runs.
[datasets] — adds Hugging Face and Parquet support for datasets pull. JSONL and CSV work with the base install.

shell

# local developmentuv run --extra dev --extra optimize rollout optimize run --helpuv run --project packages/cli --extra dev --extra datasets rollout datasets pull --help# user tool installuv tool install "./packages/cli[optimize]"uv tool install "./packages/cli[datasets]"

For production:

shell

rollout login

For local split-port development, point the browser app and the API at their respective URLs:

shell

rollout login \  --app-url http://127.0.0.1:5173 \  --api-url http://127.0.0.1:8080

--app-url is the browser app URL; --api-url is the API URL saved into ~/.rollout/config.json and used by whoami, check, and the import commands. For a single-origin deployment, --base-url still works as a shorthand:

shell

rollout login --base-url https://app.rollout.work

Note

Login opens the browser, waits for a localhost callback, and stores only a Rollout API key — it does not store WorkOS tokens or source-provider credentials.

Verify

Confirm the saved key and workspace, then send a diagnostic trace through the ingest path:

shell

rollout whoamirollout check

See Configuration for the config file, environment overrides, and per-command URL/key flags.