Skip to main content
Cadenza uses a name + token sign-in. An administrator creates your account and issues you a token , then hands it to you out-of-band.
Authentication is only required for account-scoped commands: env action create and env action list (your actions live under your account). Scaffolding, running missions, stats, and fine-tuning all work signed-out.

​
Commands

CommandDescription
cadenza login <name> <token>Verify your credentials and save a session.
cadenza whoamiShow the currently signed-in account.
cadenza logoutForget the saved session.
cadenza login ada my-sign-in-token
# signed in as ada (8f2c…)

cadenza whoami
# signed in as ada (8f2c…)

cadenza logout
# signed out.

​
How sessions work

  • On login, your (name, token) is verified live against the backend. On success the session is written to ~/.cadenza/config.json (created owner-readable, 0600).
  • Every protected command re-validates the session live on each call, with no caching. If your token is revoked, or an admin sets your account inactive, the next command fails immediately with a clear message.
  • A deactivated account (is_active = false) is refused even with a valid token.
If you see “session expired or revoked” or “this account has been deactivated”, your credentials are no longer valid. Run cadenza login again with a fresh token from your admin.

​
Requesting a token

Don’t have a token yet? Email acparekh@stanford.edu to request one. You’ll be given a name and a token, then sign in with cadenza login <name> <token>.