cluz login and terms
Sign in from a terminal or a script, show who you are, sign out, and accept the terms.
| Command | What it does |
|---|---|
cluz login | Sign in. Opens your browser. |
cluz logout | Remove the saved session from this machine. |
cluz whoami | Show the signed-in user, their teams and the API in use. |
cluz terms | Show the terms' address and say whether you accepted them. |
cluz terms accept | Accept the terms for the business or organisation you act for. |
Sign in
cluz login # GitHub in the browser
cluz login --provider gitlab # or bitbucket, google
cluz login --no-browser # print the URL to open elsewhere
cluz whoami
cluz logoutcluz login opens the API's OAuth page. After you approve, the browser is sent back to a listener the CLI runs on 127.0.0.1 with a one-time code, and the CLI trades that code plus a secret only it holds for a session. No token appears in a URL or the browser history.
The session (access token, refresh token) is saved to ~/.clusterz/config.json with mode 0600 and renews itself, so you stay signed in until you log out or the refresh token lapses (7 days without use). The CLI never prints tokens.
Saved tokens are only sent to the API they were issued by. Pointing the CLI at another API (--api-url, CLUSTERZ_API_URL) needs its own cluz login.
For CI and scripts
Skip the browser and pass a token:
CLUSTERZ_TOKEN=... cluz deploy --wait --team acme --project api
echo "$TOKEN" | cluz login --with-token # or save itThe terms
cluz terms # the terms' address, their version, and whether you accepted it
cluz terms accept # shows them, asks, and records your acceptance; --yes skips the questionClusterz changes nothing on a team for someone who has not accepted the terms in force (https://clusterz.eu/terms). cluz terms accept accepts them for the business or organisation you act for, and the record says it was made here.