CLI
Mobius CLI
The mobius CLI is the primary way to drive Mobius from a terminal or
CI job. It speaks the same HTTP and WebSocket protocols as the
API and SDKs, and handles auth, reconnects,
pagination, and event replay for you. Source and full command reference
live in the mobius repo.
Install
On macOS with Homebrew:
brew install deepnoodle-ai/tap/mobiusThe CLI ships as a single static binary, so you can also grab a release
archive from GitHub releases
and drop it on your PATH. Verify the install:
mobius versionAuthenticate
Interactive login opens a browser, runs the device-code flow, and saves a local credential profile:
mobius auth login
mobius auth statusFor CI and sandboxed shells, skip the browser and use an API key through environment variables:
export MOBIUS_API_KEY=mbx_...
export MOBIUS_PROJECT=prodEvery command also accepts --project <handle> to target a project
explicitly.
Everyday commands
| Area | Command | What it does |
|---|---|---|
| Projects | mobius projects list | List the projects you can reach. |
| Automations | mobius automations list | Inspect automations and versions. |
| Runs | mobius runs start <handle> | Kick off a run from an automation. |
| Runs | mobius runs stream <run-id> | Follow a run's event stream live. |
| Workers | mobius worker --queues default | Run a worker that executes action steps. |
A run from scratch, end to end, looks like this:
mobius runs start quickstart-print --inputs '{"note":"hello"}'
mobius runs stream run_01...
mobius runs get run_01...Where to go next
- Quickstart: the full path from an empty project to a running, worker-backed automation.
- Automations: how steps, versions, and triggers fit together.
- Workers: running worker processes, queues, and custom actions.
- API Introduction: when you need the raw HTTP layer instead of the CLI.