Reoclo CLI
The reoclo CLI is the terminal-native interface to your Reoclo organization. Trigger deploys, tail logs, exec commands on servers, manage applications and secrets, generate Docker registry credentials, and wire your dashboard to AI assistants, all from a single binary that runs on macOS, Linux, and Windows.
Start here
Section titled “Start here”- Install: Homebrew, install script, or binary download
- Getting Started:
reoclo login, your first deploy, common workflows - CI/CD Automation: non-interactive auth via OAuth client credentials for pipelines
- MCP Server: expose the CLI as a Model Context Protocol server for Claude, Cursor, and other AI assistants
- Upgrading: when to upgrade, breaking changes, version pinning
Commands
Section titled “Commands”Every CLI subcommand has a dedicated reference page documenting its flags, examples, and exit codes:
| Domain | Commands |
|---|---|
| Identity | login, logout, whoami, profile, keyring |
| Infrastructure | servers, apps, deployments |
| Operations | logs, exec, shell, env, domains, status-pages |
| Tooling | mcp, upgrade, completion |
Common flags
Section titled “Common flags”The CLI honors a few env vars across every command:
| Env var | Purpose |
|---|---|
REOCLO_ROOT_DOMAIN | Switch the CLI between environments: reoclo.com (prod, default), reoclo.dev (staging), reoclo.test (local HTTPS dev) |
REOCLO_API_URL | Override just the API URL (wins over REOCLO_ROOT_DOMAIN) |
REOCLO_AUTH_URL | Override just the auth URL |
REOCLO_OUTPUT | Default output format (table, json, yaml, tsv) |
REOCLO_PROJECT_DIR | Directory the .reoclo search starts from. Set it to opt out of a .reoclo that sits above your working directory |
Per-command flags like --api, --auth, and --output still take precedence over the env vars.
Get help
Section titled “Get help”Every command supports --help for inline documentation:
reoclo --helpreoclo servers --helpreoclo deployments trigger --helpFor interactive issues or feature requests, see the Reoclo CLI repository.