Signing in

Sign in to the web app in your browser and to the CLI with an API token; sign a browser in with a login link from the CLI.

The web app and the CLI sign in separately. The browser keeps a session; the CLI stores an API token.

The web app

Open https://zeonsystems.app and click Sign in. After you sign in you return to the address you asked for: a link someone sent you, or a plain app link the CLI printed, opens where it points. A login link from zeon app signs the browser in without this step.

If you cannot sign in or do not have an account, contact your organization's administrator or your Zeon contact.

To sign out, open the menu at the top right of the app and choose Log out.

The CLI

zeon login

zeon login is short for zeon auth login. It:

  1. starts a one-time listener on localhost:8765 to receive the sign-in redirect;
  2. opens your browser at the Zeon sign-in page (if the browser does not open, it prints the address to paste);
  3. after you sign in, creates an API token for the CLI (90 days by default);
  4. writes the token to ~/.zeon/.env as ZEON_API_TOKEN, readable only by you;
  5. checks the token and prints the email you are signed in as.

It waits up to five minutes for you to finish in the browser.

Where the token goes

OptionFile
(none)~/.zeon/.env, used from every directory on this machine
--local.env in the current directory; it takes precedence over ~/.zeon/.env there

zeon commit, zeon push and zeon sync never take a .env or .env.* file, at any depth, and a pull never writes or deletes one, so a token in a project folder stays on your machine.

When the CLI looks for a token it uses, in order: the ZEON_API_TOKEN environment variable, the nearest .env file in the current directory or a parent directory, then ~/.zeon/.env.

Options

OptionMeaning
--token TEXTStore an existing API token instead of opening the browser. Use it on a machine without a browser, with a token created on the API tokens page.
--name TEXTThe token's name on the API tokens page. Default: cli- followed by the host name and a timestamp.
--expires-in-days NToken lifetime, 1 to 365 days. Default 90.
--localWrite to ./.env instead of ~/.zeon/.env.

Check and sign out

zeon auth status

prints where each setting came from (the api_token masked), checks the token with the server, and prints your user id, email and organization id. zeon auth with no subcommand does the same. It exits with code 1 when no token is set or the server rejects it.

zeon logout

(short for zeon auth logout) signs this machine out:

  1. it ends the browser sessions that this token's login links started;
  2. if the token was created by a browser zeon login (CLI 1.5.5 or newer), it revokes the token on the server, so it stops working everywhere;
  3. it removes the token from ~/.zeon/.env (with --local: from ./.env) and keeps the file's other keys.

A token stored with zeon login --token, or written by an older CLI, is only removed from this machine: it stays valid until it expires. Revoke it on the API tokens page to end it at once. When the server cannot be reached, zeon logout prints one notice and still removes the local copy.

Login links from the CLI

With CLI 1.5.5 or newer, zeon app opens the web app signed in. It prints a login link:

https://zeonsystems.app/auth/link?code=...&next=/p/<project-id>/workflow-editor?...
CommandThe link opens
zeon appthe project's page
zeon app Wworkflow W's canvas beside the simulation; its run screen, with a notice, when W has no canvas
zeon app W --runworkflow W's run screen

Opening the link signs that browser in to your account without a password and goes on to the page. The link is personal: it is meant for your own browser that is not signed in yet, such as a browser pane next to a coding agent. To show other people the simulation, share the 3D viewer link from zeon open instead; it needs no sign-in.

  • One use, 5 minutes. The code works once and is valid for 5 minutes. For a fresh link, run the command again. An expired or already used link opens the sign-in page with "That link has expired. Sign in to continue."; after you sign in, the page you asked for opens.
  • The browser session. The session the link starts lasts 12 hours and is tied to the CLI token that created the link. It ends earlier when you sign out in that browser, when you run zeon down or zeon logout on the machine that printed the link, or when that token is revoked or expires.
  • The plain link. --no-login-link prints the plain app link instead; it needs a normal sign-in in that browser. The CLI also prints the plain link, with a one-line notice:, when the server does not offer login links yet, and when ZEON_APP_URL is set (a local stack or a deployed box).
  • Operator mode. Add &ui=operator to the end of the link to open the app in operator mode; the link still signs the browser in.
  • The 3D viewer link from zeon open is unchanged and is the one to share: it carries its own token and stops working after zeon down.
  • Older form. zeon open --canvas W and zeon open --workflow W still print the same login links, with a notice to use zeon app W or zeon app W --run.

Password sign-in in the browser is unchanged.

A login link is a short-lived credential: whoever opens it first is signed in as you. Open it yourself, do not paste it into a shared channel or document, and print a new one instead of reusing it.


Did this page help you?