Skip to content

Log in

Log in before you want simulo run to submit your app to the Simulo cloud. Without a login or selected cloud environment, simulo run creates a local package but does not run it. Logging in is a one-time step: the CLI saves your credentials locally and refreshes them automatically from then on.

Terminal window
simulo login

simulo login signs you into the Simulo cloud.

The CLI binds a short-lived local server on 127.0.0.1 and opens your default browser to Simulo’s sign-in page. Sign in (or create an account), and the browser redirects back to the local server — you’ll see a confirmation page you can close. The terminal prints:

Logged in as you@example.com (org: <org-id>)

Credentials are written to ~/.simulo/credentials with permissions 0600. The CLI refreshes the access token automatically; you don’t need to log in again until the refresh token itself expires.

Terminal window
simulo whoami
Email: you@example.com
Org: <org-id>
Terminal window
simulo logout

This revokes the refresh token server-side and deletes ~/.simulo/credentials. It always clears local state, even if the server-side revoke fails.

By default, simulo login signs you into the Simulo cloud. If you’ve been given access to a separate environment — staging, say — name it with SIMULO_ENV for the login:

Terminal window
SIMULO_ENV=staging simulo login

The saved credentials record which environment you signed in against, so every later command (simulo run, simulo jobs, …) targets the same environment with nothing set. See Configure environments for the full resolution rules, including SIMULO_API_URL for pointing at a control plane directly.

Choose a validated asset from the Simulo global catalog, or validate and publish your own.