Skip to main content
The autosana CLI connects local simulators, emulators, physical devices, and dev servers to Autosana so you can run flows against a build on your own machine. It also validates your code-managed flow files before you push (autosana flows validate) and runs them from the terminal (autosana run).

​
Quick install

The fastest way — installs uv if it’s missing, then the CLI. Zero prerequisites:
Upgrade any time with autosana update.

​
Other install methods

pipx:
uv:
pip (into an environment you manage):

​
Local testing dependencies

Everything above is a lightweight install that covers the flows commands and local web testing. Capturing screenshots from a simulator or physical device needs the optional local extra, which pulls in Pillow:
Add [local] only when running flows against a simulator, emulator, or physical device. Web local runs do not need it.

​
Verify

If autosana isn’t found after installing with uv, add uv’s tool directory to your PATH and restart your shell:

​
Set up prerequisites

Web local testing needs cloudflared and a running dev server. Mobile local testing also needs Node.js and Appium. autosana doctor checks the CLI dependencies and can install missing tools; autosana up --platform web checks that the dev server is reachable when the session starts.

​
Log in

Authenticate the CLI against your Autosana organization — it opens the dashboard for a one-click approval, no key copying:
AUTOSANA_API_KEY still works for CI and scripting, and always takes precedence over a stored login.

​
Upgrading

These docs describe the current release. If a command or flag from the docs is missing, upgrade:
It upgrades the CLI the same way you installed it. On a version without autosana update, re-run the installer instead:

​
Next steps