Sign in with rvs

The rvs CLI uses a device-login flow so you can approve a terminal session in your browser without copying your account password into the CLI.

Note

rvs gives developers browser-backed authentication without copying a reusable API token into local package-manager configuration.

Sign in

rvs auth login

Approve the request in your browser. rvs stores the resulting session credentials in your configured credential store. Run rvs auth storage doctor to inspect available secure stores.

Automation

Use an automation token where browser approval is unavailable:

export RVS_TOKEN="${TOKEN_FROM_SECRET_STORE}"

RVS_TOKEN takes precedence over keyring credentials and is not refreshed automatically.

Choose a credential

Scenario	Credential
Interactive developer terminal	rvs auth login device session
CI or unattended automation through rvs	RVS_TOKEN
pip, uv, Twine, npm, Maven, or Gradle	Matching rvs wrapper with temporary authentication

Revoke old device sessions from account settings. See rvs authentication and profiles for profile management and credential precedence.

A local profile is named CLI configuration and a credential slot; it does not define the authenticated user. After login, select the personal account or one of that user’s organizations separately with rvs account use. See accounts and package targets for multi-account selection, one-shot commands, and the optional terminal hint.