Skip to main content
Start with bifrost doctor and bifrost auth status --output json. They show whether the gateway is reachable, which credentials the current context holds, and whether model discovery works. Exit code 3 means an authentication or authorization failure; see exit codes.
Run bifrost auth status --output json. For inference, inference_credential_type must be enterprise-sso or virtual-key. Administrative commands need a management API key; SSO alone returns an authorization error. If the session expired, run bifrost auth login.
The management API key lacks the required scope. Run bifrost auth whoami to list its permissions, and ask an administrator to update the key’s scopes under Settings → API Keys.
Add a context with bifrost context add <name> --base-url <url> --use, or pass --base-url with credential environment variables.
auth login, auth set-virtual-key, and auth set-management-key store secrets only in a named context. Add one first.
Use an https:// URL for any host other than localhost, 127.0.0.1, or ::1.
Run bifrost doctor and bifrost models list --output json. Confirm a provider is configured and the virtual key or access profile allows the model. Under the default version: 2 semantics, an empty provider-key model allow-list or virtual-key allowed_models list denies all models in that scope; use ["*"] to allow all.
Store a virtual key with bifrost auth set-virtual-key --stdin. Gemini CLI cannot use an SSO session.
A previous bifrost configure claude left ANTHROPIC_AUTH_TOKEN in ~/.claude/settings.json. Run bifrost unconfigure claude.
The file changed after Bifrost configured it, or a previous attempt did not finish. Review the file, then rerun with --force.

​
Next steps

Enterprise setup

Sign in with SSO and add a management API key.

Coding agents

Launch Claude Code, Codex, OpenCode, or Gemini through Bifrost.