Log in

Run:

culvii login

The CLI opens a browser window pointed at Culvii's identity provider. Sign in with the Google account associated with your Culvii invite. After you authorize, the browser redirects to localhost:<random port> and the CLI confirms login on the terminal:

✓ Logged in as you@yourcompany.com
✓ Default context set: tenant=yourcompany, env=dev

The token is stored at ~/.culvii/config (mode 0600). The CLI uses it automatically for every subsequent command. You don't pass it explicitly.

Verify

culvii whoami

Expected output:

User:           you@yourcompany.com
Tenant:         yourcompany
Environments:   dev, sandbox, prod
Default context: tenant=yourcompany, env=dev

The default context is what the CLI uses when you don't pass --env or --workspace. For the tutorial, we'll work in dev, so this is correct.

When the session expires

OAuth sessions are valid for 30 days on a sliding window. When they expire, the CLI prompts you to log in again. You don't have to think about this most of the time.

To log out manually:

culvii logout

This revokes the refresh token and removes the local config file.

What this is not for

culvii login is for you, the human, running CLI commands. It is not for code running in CI, in production, or anywhere unattended. For those, you create an API key — covered later in Promote to production.

Next: Your first workflow.