reoclo login
reoclo login [options]Runs the OAuth 2.0 device flow. The CLI prints a short device code and opens your browser to the Reoclo dashboard. Approve the request and the CLI persists access + refresh tokens for the named profile. Tokens are refreshed automatically; you do not need to log in again until consent is revoked.
There are no API keys to paste. Headless / CI use cases should set REOCLO_AUTOMATION_KEY (an Automation Key, rca_*) — see CI/CD automation.
Options
Section titled “Options”| Flag | Default | Description |
|---|---|---|
--profile <name> | default | Name of the profile to write to. |
--api <url> | https://api.reoclo.com | API base URL. Override for staging or self-hosted Reoclo. |
--auth <url> | https://auth.reoclo.com | OAuth issuer base URL. |
--streams <url> | derived from --api | Cloudflare-bypass host used for terminal WebSockets and large uploads. |
--keyring | off | Require OS keyring storage. Fails if no keyring is available. |
--no-keyring | off | Force file storage even if a keyring is available. |
--no-browser | off | Do not auto-open the browser; print the URL only. |
Examples
Section titled “Examples”Default login:
reoclo loginLogin with the staging tenant under a named profile:
reoclo login --profile staging --api https://api.staging.reoclo.comreoclo profile use stagingHeadless host (SSH / dev container) — print the URL instead of auto-opening:
reoclo login --no-browserForce file storage on a machine where the keyring is disruptive (e.g., a shared workstation):
reoclo login --no-keyringStorage
Section titled “Storage”By default the CLI stores tokens in the OS keyring:
| Platform | Backend |
|---|---|
| macOS | Keychain |
| Linux | Secret Service (libsecret/gnome-keyring) |
| Windows | Credential Manager |
If the keyring is unavailable (typical on headless Linux without dbus), the CLI falls back to a 0600-mode file at ~/.reoclo/config.json. Run reoclo keyring status to see which backend is in use.
Non-TTY environments
Section titled “Non-TTY environments”Running reoclo login without an interactive terminal exits with:
OAuth device flow requires an interactive terminal. Use an Automation Key for CI/CD — see https://docs.reoclo.com/guides/api-keys/For CI/CD, set REOCLO_AUTOMATION_KEY in the environment instead of running reoclo login.
Related
Section titled “Related”- CLI Authentication — narrative guide to profiles, keyring, refresh
reoclo logout— remove stored credentialsreoclo whoami— show the active identityreoclo profile— manage named profilesreoclo keyring— inspect or migrate stored tokens