Logging in

Authenticate the Koolbase CLI with your account. By default this opens your browser to sign in with Google; GitHub and email-and-password sign-in are available too.

Sign in with Google

Running koolbase login opens your browser to a Google sign-in screen. Pick your account, and you’re done — the CLI captures the result on a local loopback address and stores your session.

koolbase login

You’ll see a prompt like this, and your browser will open automatically. If it doesn’t (for example on a headless or remote machine), copy the printed URL into any browser to continue:

Opening your browser to sign in with Google...

If your browser didn't open, visit this URL to continue:

https://accounts.google.com/o/oauth2/v2/auth?client_id=...

 Logged in as [email protected]

The browser sign-in window stays open for 3 minutes. If you don’t finish in time, the CLI stops waiting and you can simply run koolbase login again.

Sign in with GitHub

If you signed up with GitHub, use the --github flag. It opens the same kind of browser flow as Google, but against GitHub:

koolbase login --github

Authorize the Koolbase CLI on GitHub’s consent screen, and the CLI captures the result on a local loopback address and stores your session — the same 3-minute window applies.

Sign in with a password

If your account has an email and password, use the --password flag to sign in without the browser:

koolbase login --password

You’ll be prompted for your email and password.

Signed up with Google or GitHub? Accounts created through Google or GitHub sign-in have no password. If you try --password on one, the CLI will tell you to use the matching provider instead, or to set a password in your dashboard settings.

Your session

A successful login stores a session that stays valid for 30 days. After that, commands will ask you to sign in again — just re-run koolbase login.

Check who you’re signed in as at any time:

koolbase whoami

And sign out when you’re done:

koolbase logout

CLI login vs. API keys

koolbase login authenticates you, for interactive use. For automation — CI pipelines, the MCP server, scripts — use an organization API key (kb_live_…) instead, which carries an explicit scope and isn’t tied to a personal session. Mint one with koolbase keys create.

Connecting another provider

You can link additional sign-in providers to your account. Once you’re signed in, run koolbase connect with a provider to add it:

koolbase connect google
koolbase connect github

This opens the same kind of browser flow as signing in, but instead of creating a session it attaches the provider to your existing account. After connecting, you can sign in with that provider next time. Connecting a provider you’ve already linked is harmless — it simply succeeds without creating a duplicate.

Signing out

koolbase logout ends your session on the server and removes the saved credentials from your machine:

koolbase logout

Your local credentials are cleared even if the server can’t be reached, so you’re never left signed in locally when you meant to sign out.

Connecting multiple sign-in methods

One Koolbase account can hold several sign-in methods — a password, Google, and GitHub can all belong to the same account. Your account is identified by the specific provider you sign in with, not just by your email address.

Because of this, if you already have an account (say, created with a password) and then try to sign in with a new provider that reports the same email, Koolbase will not automatically merge them. Instead it asks you to sign in with your existing method first, then connect the new provider deliberately:

Sign in with your existing method (for example koolbase login --password), then run koolbase connect github to link the new provider.

This is a deliberate safety measure: it prevents anyone from attaching a new login to your account just because they control an email address that happens to match yours.

You can also manage your sign-in methods from the dashboard: open Connected Accounts in settings to connect a new provider, or remove ones you no longer want. You can’t remove your only remaining sign-in method, so you’re never locked out.

Installation

Commands