sincecutoff.com
← all changes

bk auth adds OAuth login and logout

Introduced 2026-02-11 · score 0.92

HOW TO USE IT

When working in a Buildkite repository, authenticate with `bk auth login --org <organization-slug>` to open the browser OAuth flow and store the token in the system keychain. Use `bk auth logout [<organization-slug>]` to clear credentials for an organization; the v3.24.0 command also clears its config token.

bk auth login --org <organization-slug>
bk auth login --org <organization-slug> --scopes "<scope> <scope>"
bk auth logout [<organization-slug>]

WHY THIS HELPS

Authenticate the bk CLI with OAuth when working in a repository that uses Buildkite.

BEFORE THIS CHANGE

The release note says the temporary `auth` alias for `configure` was removed; it does not document the earlier command invocation.

REQUIREMENTS AND LIMITATIONS

  • Version: v3.24.0
  • login --org <organization-slug> (required): Organization slug for OAuth login.
  • login --scopes <scopes>: OAuth scopes to request; examples include `read_user read_organizations read_clusters write_clusters`.
  • logout [<organization-slug>]: Organization slug; defaults to the currently selected organization. If neither is available, the command errors.
  • Prerequisite: Install the Buildkite CLI; v3.24.0 is the version covered by the cited command source.
  • Prerequisite: OAuth login opens a browser and stores the resulting token in the system keychain when available; it also writes the token to config for fallback/compatibility.
  • OAuth support is initial.
  • OAuth client ID is injected into built binaries.
  • Tokens remain in text-based config; removing them is still to come.
  • Docs conflict: Current auth documentation reflects newer CLI behavior: it lists login flags such as `--device` and `--token`, whereas v3.24.0 source requires `--org` and documents `--scopes`. Use the v3.24.0 source for this card.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card