CLI
Command reference
The mobius CLI groups commands by product resource. This page is the map;
mobius <group> --help is the exact reference for the version installed on
your machine.
Command groups
| Group | Use it for |
|---|---|
auth | Log in, inspect profiles, select a profile, and revoke CLI credentials. |
projects | List, create, inspect, update, and delete projects. |
organizations | Inspect organization settings and administrative controls. |
agents | Manage agents, memory, inboxes, tools, skills, and messaging bindings. |
sessions | Create conversations, invoke agents, page transcripts, stream turns, nudge work, and compact history. |
loops | Create and update loop definitions and deliver HTTP triggers. |
runs | Start, inspect, cancel, resume, retry, or signal loop runs. |
actions | Manage project-owned actions, invoke one directly, and inspect invocation history. |
catalog | Discover available actions, events, and models. |
toolkits | Manage named sets of actions available to agents. |
skills | Manage reusable agent instruction packages. |
interactions | Inspect and respond to information, approval, and review requests. |
tables | Manage shared tables and their rows. |
artifacts | List, inspect, download, delete, and create signed URLs for artifacts. |
environments | Create, inspect, update, and destroy managed environments. |
api-keys | Manage API keys scoped to one project. |
org-api-keys | Manage organization-wide API keys. |
webhooks | Manage outgoing webhook subscriptions and deliveries. |
blueprints | Apply project blueprints and manage their bindings. |
worker | Run a worker process that claims jobs. |
Loop authoring uses mobius loops. Older docs and scripts may mention a legacy
automations group; current CLI releases no longer expose it. Use mobius loops --help when updating those scripts.
Create or update from a file
Resource commands that accept structured input use --file with JSON or YAML.
Flags override matching file fields, and --dry-run prints the assembled
request without sending it.
mobius loops create \
--project default \
--file review-loop.yaml \
--output json{
"id": "<loop-id>",
"handle": "review-every-pull-request",
"status": "active"
}Use --var KEY=value to substitute ${KEY} placeholders in a file before it
is sent.
Work with runs
mobius runs start review-every-pull-request --project default --output json{
"id": "<run-id>",
"status": "queued"
}mobius runs list-events <run-id> --project default --output json{
"items": [
{ "sequence": 1, "type": "run.started" },
{ "sequence": 2, "type": "step.started", "step_id": "review" }
],
"has_more": false
}Recover a failed run from its last completed checkpoint:
mobius runs resume <run-id> \
--project default \
--reason "Provider recovered" \
--output json{
"id": "<run-id>",
"status": "running",
"recovery_mode": "resume"
}Work with sessions
mobius sessions list --project default --output json
mobius sessions get <session-id> --project default --output json
mobius sessions stream <session-id> --project defaultAdd direction to an active turn:
mobius sessions nudge <session-id> \
--project default \
--content "Prepare the diff, but do not deploy." \
--output json{
"id": "<nudge-id>",
"status": "pending",
"delivery": "current_turn"
}Work with data
List artifacts, tables, and environments:
mobius artifacts list --project default --output json
mobius tables list --project default --output json
mobius environments list --project default --output jsonUse the resource help to discover write flags:
mobius tables create --help
mobius tables upsert-row --help
mobius environments create --helpRun a worker
Start one worker process for the default queue:
mobius worker --project default --queues defaultThe worker is ready after both startup messages appear:
level=INFO msg="starting worker" project=default queues=[default]
level=INFO msg="worker registered" worker_instance_id=<instance-id> heartbeat_cadence_seconds=<seconds>The process remains in the foreground while it is connected. A reconnect
message is normal during a brief network interruption. Investigate when
worker registered never appears or reconnects continue without recovery.
Create one-time credentials
Commands that create API keys or webhook secrets print the full secret only once. Capture it immediately in a secret manager.
mobius api-keys create \
--project default \
--name ci-worker \
--principal-id <principal-id> \
--output json{
"id": "<key-id>",
"name": "ci-worker",
"key": "<one-time-api-key>"
}Later list and get commands return only identifying metadata, never the full secret.
Next
- Set up credentials in Install and authenticate.
- Learn the terminal conventions in the CLI overview.
- Use the API reference when a CLI command has not yet exposed the operation you need.