Sign in & auth
GBAM uses a browser-linked login flow instead of asking you to manage API keys in the terminal. When you run /login, the CLI opens your browser, the website continues the auth flow, and control is handed back to the terminal when sign-in completes.
How the flow works
- The CLI starts a temporary localhost callback server.
- The browser opens to the GBAM web experience.
- The website and auth provider complete identity verification.
- The server redirects back to the local CLI callback.
- The CLI stores the returned bearer token locally.
Local credential storage
Auth state is stored on your machine in~/.gbam/auth.jsonwith owner-only permissions where supported. If the server later returns 401, the CLI clears local auth and asks you to sign in again.