Skip to main content
Sign in through the browser, exchange the code for an access token, pick an organization, and save a profile. Run this once per machine before any other command.

Synopsis

Options

Examples

1. Interactive sign-in

The CLI prints a one-time code, opens your default browser to the verification page, and waits for you to approve. After approval it polls for the token, lists your organizations, and prompts you to pick one. Output ends with ✓ Logged in as you@example.com (Acme Inc.).

2. Pre-select an organization

Matches by name (case-insensitive) or by ID. The picker is skipped entirely, which is useful for scripts that need to re-bind a profile to a known organization.

3. CI environments

For CI you typically skip auth login and use an API token instead:
A token in the environment takes precedence over any saved profile. See Authentication for the precedence table.

Response

The access token is stored in your system keyring (Keychain on macOS, libsecret on Linux, Credential Manager on Windows). The profile record on disk holds the organization ID, organization name, your email, and the auth method, never the token itself.

See also