Skip to main content

​
What needs an account

Playback never authenticates. A site that embeds a Clayzo player makes no request to Clayzo.

​
Signing in on your machine

The CLI prints a URL and a short code, and opens the URL in your browser. Sign in to Clayzo, confirm the code matches, and approve the device. The terminal picks it up and prints {"authenticated": true}. The code expires if it isn’t approved within a few minutes; run the command again. Credentials are stored on the machine and refreshed automatically: Set CLAYZO_CONFIG_DIR to store them somewhere else. To sign out and revoke the device:

​
CI and servers

Create a token once, from a signed-in machine:
The token is printed once and never again. Clayzo keeps only a hash. Store it as a secret and expose it as CLAYZO_TOKEN; every protected command uses it when set.
Manage tokens from any signed-in machine:

​
Checking the setup

Reports whether the machine is authenticated, whether the installed packages and skills match, and whether an update is required. Add --json for machine-readable output.