Skip to main content
The CLI signs in through your browser using your existing Alertee account — no copy-pasting tokens. Behind the scenes it obtains a personal access token (PAT) and stores it locally at ~/.config/alertee/config.json.

​
Log in

This opens your browser to an authorization page. If you’re already signed in to the Alertee dashboard, just click Authorize; otherwise you’ll sign in first. Once approved, control returns to your terminal automatically:
Login links your default organization automatically (or your only one). Run alertee link if you want a different org.
The login uses PKCE: a one-time code is passed back to the CLI over a local loopback address, and the token is only issued after the CLI proves it started the request. The token itself never appears in a browser URL.

​
Headless / SSH sessions

If there’s no browser on the machine (e.g. a remote server), print the URL instead of trying to open one, then open it on any device:
If you belong to multiple organizations, choose which one the CLI should use:
Your selection is saved to the local config. Re-run alertee link to switch. To target a different org for a single command without re-linking, pass --org <id> before the subcommand: alertee --org <id> checks list. The env var ALERTEE_ORG does the same for a whole session (handy in CI). To use another saved account for just one command without changing the active account, pass --account <email|prefix> before the subcommand:
This is the command-scoped equivalent of ALERTEE_ACCOUNT; it does not modify the active account saved in the config file. It can be combined with --org.

​
Check status

​
Multiple accounts

The CLI stores every login, keyed by email — just run alertee login again with another account to add it, then switch between them like gh auth switch:
Each account keeps its own token and linked organization, so switching back restores the org you had linked. Switching applies immediately to the local MCP server too — it reads the active account on every tool call, no restart needed. To pin a shell session or an MCP server config to a specific account, set ALERTEE_ACCOUNT=<email>.

​
Log out

This removes that account’s credentials from ~/.config/alertee/config.json (other accounts are kept; the CLI switches to one of them automatically).

​
CI / non-interactive use

For pipelines where a browser flow isn’t possible, create a token in the dashboard (Settings → API Tokens → New token) and provide it via environment variables:
ALERTEE_TOKEN takes precedence over any stored credentials, so the CLI works without ever running alertee login.

​
Token expiry

Tokens expire after 1 year. Run alertee login again to get a new one.