Skip to main content

bonya login

Saves an API key (and optionally an endpoint and organization id) to the local config file, so subsequent commands don’t need --api-key/--endpoint/--organization-id or BONYA_API_KEY/BONYA_ENDPOINT/BONYA_ORGANIZATION_ID. Flags and environment variables still take priority over what’s saved — see Configuration for the full precedence order. There are two ways to log in:
Run bonya login with no --api-key. This is a device-authorization flow — the same shape as gh auth login:
It mints a login request, prints (and opens) a verification URL, and polls until you approve the login there. Nothing to copy or paste. The resulting API key is saved automatically.
If your account has no sandboxes yet, bonya login offers to create your first one and tells you how to open a shell in it.

Flags

--skip-verify and --no-browser each only affect one of the two login paths: --skip-verify does nothing without --api-key, and --no-browser does nothing with it (the --api-key path never opens a browser in the first place).

Examples

After logging in

See whoami and logout and bonya org for switching which organization your commands act in.