Connect the CLI

Before the CLI can submit hosted builds, it needs to be authorized against your Platform account. RubyEverywhere uses an OAuth-style device flow: the CLI shows you a short code, you approve it in the browser, and the CLI receives a token. No passwords or API keys pasted into a terminal.

Log in#

every platform login

The CLI starts the device flow, prints a confirmation code, and opens the approval page for you:

→ confirmation code: BRDX-7Q2F
→ opening https://platform.rubyeverywhere.com/cli/activate
→ waiting for you to approve in the browser…

Confirm you are signed in to the Platform, check that the code on screen matches the one in your terminal, and approve. The moment you do, the CLI stops waiting and stores a token scoped to the organization you approved for:

✓ logged in to Acme Inc (org_9f2c4e…)

If the browser did not open, the CLI says so. Paste the URL it printed.

Check the connection#

every platform auth status

This validates the saved token against the Platform, so it tells you not just that a credential exists locally but that it still works:

✓ logged in to https://platform.rubyeverywhere.com
→ user:  [email protected]
→ org:   Acme Inc (org_9f2c4e…)
→ token: …a91f · last used 2026-08-15 14:02:11 UTC

If the token was revoked from the dashboard, this reports it and you log in again.

Log out#

every platform logout

The token is revoked on the Platform and removed from this machine. If the Platform cannot be reached, the local credential is dropped anyway and the CLI warns you. Revoke it from Settings → Devices in the dashboard when you are back online.

One token per machine#

Each machine that logs in gets its own token, named after that machine's hostname and OS, so a laptop and a CI runner can be approved and revoked independently. Every authorized device is listed under Settings → Devices.

Pointing at another Platform#

All three commands take --url (defaulting to $EVERYWHERE_PLATFORM_URL, then production). Credentials are stored per base URL, so being logged in to a staging Platform doesn't disturb your production login:

every platform login --url https://platform.example.test

With the CLI connected, you're ready to run hosted builds.