run-droid

Use `droid exec` with a prompt as a positional argument, file, or pipe — it runs to completion without the TUI and exits with a status code. Never call bare `droid` in automation, since that opens the interactive TUI.

Pass `-o json` and droid emits a single JSON object at the end containing result, session_id, is_error, and duration fields. Extract values with jq, for example `droid exec -o json "..." | jq -r '.result'` for the final answer.

--skip-permissions-unsafe bypasses all confirmations entirely, while --auto uses a graduated autonomy ladder from low to high. The two flags are mutually exclusive, and passing both is an error.

Capture the session_id from the JSON result of the first run, then pass it with `-s <session_id>` along with a new prompt. You can also fork a session with `--fork <id>` or resume interactively with `droid --resume`.

A non-zero exit with a permission error is the autonomy fail-fast: the requested action exceeds the configured autonomy level, and droid stops with no partial changes. In yolo mode with --skip-permissions-unsafe this does not occur.

Yes, droid must already be logged in by the human or have FACTORY_API_KEY set in the environment before invocation. If output mentions credentials, API keys, or 401 errors, abort the task entirely rather than retrying.