Configure environments

Commands that contact a control plane — asset, jobs, logs, result, recordings, models, outputs, view, and cancel — use the same precedence order to find it. simulo run uses that target when you are signed in or explicitly select a cloud environment; otherwise it writes a local package and does not run it.

Resolution order

1. SIMULO_API_URL — an explicit URL override. Always wins.
2. SIMULO_ENV — a named environment preset (staging or prod).
3. Saved credentials — the api_base_url recorded in ~/.simulo/credentials the last time you ran simulo login.
4. The Simulo cloud — the default target for a cloud request when nothing else is set.

The Simulo cloud (default)

simulo login          # signs in against the Simulo cloud
simulo run app.py     # cloud-bound via the saved credentials

No configuration needed. Once logged in, the saved credentials record the cloud’s URL (rule 3 above), so every subsequent command targets the same place with no environment variable set.

A named environment

SIMULO_ENV=staging simulo login
SIMULO_ENV=staging simulo run app.py

SIMULO_ENV must be set consistently across the commands in a session — set it once per shell (export SIMULO_ENV=staging) rather than per-command, so simulo login’s credentials and simulo run’s target always agree. An unrecognized value is refused with the list of supported presets rather than silently falling through.

Manual token override

SIMULO_API_TOKEN=<bearer-token> simulo jobs

For observe commands, SIMULO_API_TOKEN is a manual bearer-token override for when you’re not using simulo login at all — e.g. scripting against a control plane with a token issued out of band. Logged-in credentials take precedence when both are present.

Caution

A bearer token is refused over plaintext http:// for any non-loopback host — only 127.0.0.1/localhost may carry a token unencrypted. Point SIMULO_API_URL at a real host and it must be https://.

Checking who you’re logged in as

simulo whoami

Prints the email and active organization from your saved credentials — i.e. who you signed in as, the last time you ran simulo login. It does not re-resolve SIMULO_API_URL/SIMULO_ENV: setting those changes where the next command goes, not what simulo whoami prints. When you’re not logged in at all, it errors instead of printing an identity.