deeprelay login

Authenticate with deeprelay via device flow

Synopsis

Drives an RFC 8628 device flow against the deeprelay.ai dashboard. Opens a browser to the approval URL, prompts for the user code, and on approval writes ~/.config/deeprelay/credentials.json (mode 0600).

Approval creates two keys, both saved to that file:

• a login key, used only by the deeprelay commands. It can manage API keys (full access for org admins; for members, the standard permissions plus key management). It is never printed.
• a CLI inference key named CLI inference (). It is a standard key that cannot manage keys, and it is the one deeprelay auth token prints for other tools and coding harnesses.

Re-running login rotates both CLI keys: the previous pair is revoked after the new one is saved. If the previous pair cannot be revoked (for example the API is unreachable), login still succeeds and prints a warning; revoke the old keys from the dashboard.

Examples

# Standard interactive login (opens browser)
deeprelay login

# Skip opening the browser — useful on headless machines
DEEPRELAY_BROWSER_DISABLED=1 deeprelay login

# Use the demo or staging dashboard
deeprelay login --login-base https://demo.deeprelay.ai

deeprelay login [flags]

Options

  -h, --help                help for login
      --login-base string   Dashboard base URL for device-flow approval (default "https://deeprelay.ai")

Options inherited from parent commands

      --api-base string   API base URL (override with DEEPRELAY_API_BASE env) (default "https://api.deeprelay.ai/v1")
      --debug             Enable debug logging to stderr
      --no-preflight      Skip the plan/credit check before inference requests (override with DEEPRELAY_NO_PREFLIGHT env)
  -o, --output string     Output format: table|json (default table on TTY, json otherwise) (default "table")

SEE ALSO

• deeprelay - deeprelay command-line interface