bk auth login accepts organization and token
Introduced 2026-03-04 · score 0.96
HOW TO USE IT
When logging in with an API token, run `bk auth login` with the organization slug and token. Credentials are stored in the keychain, and `bk configure` is an alias.
bk auth login --org <organization-slug> --token <api-token>bk configure --org <organization-slug> --token <api-token>WHY THIS HELPS
Log in to Buildkite from a development environment using an organization and token.
BEFORE THIS CHANGE
Run `bk configure` and enter the organization slug and API token when prompted.
REQUIREMENTS AND LIMITATIONS
- Version: v3.31.0
- --org (required): Organization slug or UUID to request access for; required with `--token`.
- --token (required): API token to store; selects non-OAuth login and requires `--org`.
- Prerequisite: Create an API access token with access to the target organization. You must be a member of that organization to generate and use its token.
- Prerequisite: The token’s selected scopes determine its API permissions.
FIRST-PARTY EVIDENCE
- https://github.com/buildkite/cli/releases/tag/v3.31.0
- https://buildkite.com/docs/platform/cli/reference/auth
- https://buildkite.com/docs/platform/cli/configuration
- https://buildkite.com/docs/apis/managing-api-tokens
Check the installed version and the source before using it. Entry JSON