Sign-in commands
Sign in to the CLI through your browser, check which account and server it is using, and sign out. Pipelines keep using an API key.
These commands need cassis-cli 3.7 or newer. For when to sign in and when to use a key, see Install and configure the CLI.
login
Signs you in through a browser and saves the login in the operating system’s credential store.
# Opens your browser
cassis login
# From a container, SSH session, or coding agent: print the URL, open it on your own computer
cassis login --no-browser
The command prints the server, a verification URL, and a short code, then waits. In the browser, sign in with your Cassis account, enter the code, and approve CLI access. The approval page names your account and its permissions. Approve only a code from a login you started.
- What it grants
- The CLI acts with your current role, organization, and domain permissions. Signing in grants nothing more.
- Remote terminals
--no-browserprints the URL without opening a browser. The remote CLI waits for your approval; no port forwarding or local callback is needed. A coding agent can start the login and show you the URL and code, and you complete the sign-in yourself.- Codes
- A code expires after 10 minutes. Ctrl-C cancels the request and exits 130. A denied or expired code needs a new
cassis login. - Storage
- macOS Keychain, Windows Credential Locker, or an unlocked Linux Secret Service or KWallet session. Never the repository, and never a plain file. A remote or container environment needs its own usable store: without one,
loginstops before asking you to approve anything. Set one up, or use an API key there. No command prints the saved credentials. - Sessions
- The CLI refreshes the login on its own. By default, a login left unused for 30 days expires. When a session expired or was revoked, the command says so: run
cassis logout, thencassis login. - One account per server
loginrefuses to replace a saved login. To switch accounts, runcassis logout, thencassis login, and choose Use another account on the approval page.
Never paste a password or token into an agent chat. The agent shows you the URL and the code; the sign-in happens in your browser.
auth status
Checks the credential with the server and prints the server, account, organization, role, and where the credential comes from: a saved login or an API key. With a key scoped to one project, it also prints that project.
cassis auth status
cassis auth status is about the account. cassis status is about the project.
logout
Revokes the saved login and removes it from the credential store.
cassis logout
# Remove the local credentials when the server cannot be reached
cassis logout --local-only
- What it revokes
- This CLI login only. Your browser and MCP sessions and your API keys are untouched, and
CASSIS_API_KEYstays set: commands keep using it. - Unreachable server
- The command keeps the local credentials so you can retry, and exits 3.
--local-onlyremoves them without revoking the session, which then lasts until it expires.
Which credential a command uses
--api-key, then CASSIS_API_KEY, then the saved login. A key that is rejected never falls back to the saved login, and a command never starts a login or opens a browser on its own. Without a key or a saved login, a command exits 2.
A saved login belongs to one server. --api-url or CASSIS_API_URL selects the server (default https://app.getcassis.com), and a login saved for one server is never sent to another.
In CI, keep using an API key stored as a secret. A gateway key is not a CLI credential.