Skip to content
v0.35.2

Authentication

Full CLI reference for v0.35.2, published . Cloud features may behave differently today.

Sign in locally

Terminal window
npx vizzly login
npx vizzly whoami

Open the browser authorization page and complete sign-in. Run whoami to check the session. Use vizzly logout to clear the saved login.

Choose a cloud upload destination

Sign in, then link an upload project. Replace acme/web-app with the organization and project slugs.

Terminal window
npx vizzly project link acme/web-app

This release saves an active project credential in user storage. Selecting another project changes that active credential for other checkouts using the same Vizzly home. Pass VIZZLY_TOKEN explicitly when a job must use a particular project.

CI and automation

Store a project token in your CI secret settings. Pass it to the job as VIZZLY_TOKEN.

Terminal window
npx vizzly run "npm test" --wait

You can pass a token explicitly with --token when a single command needs a different credential. Keep actual tokens out of committed config and scripts. The project token can authenticate CI without a browser session.

Check access

Terminal window
npx vizzly orgs
npx vizzly projects --org acme

If account commands fail, check whoami and sign in again if the session expired. If an upload fails, check which project owns the token and confirm the CI job receives it.

Where credentials live

Account login is saved under ~/.vizzly/config.json.

Linked project secrets use Keychain when it is available, with file storage as a fallback. VIZZLY_DISABLE_KEYCHAIN=true opts out of Keychain for project secrets.

Set VIZZLY_HOME to put file-backed CLI state in a separate directory. This is useful for an isolated CI environment or a second account.

See uploading screenshots for options that control the build.