unity-clilisted
Install: claude install-skill tipoLi5890/unity-dev-skills
# unity-cli — the tool, its exit codes, and what it will not tell you
> **This CLI is in beta and its surface moves.** A flag that "should" exist and does not is the
> most common way a script here fails; a flag that did not exist and now does is the second.
> Re-read `unity <command> --help` when the version moves.
Documented against CLI `1.0.0-beta.9` (September 2026). **When `unity --version` is newer than
that, `--help` outranks this file.**
## Symptom → where to look
| Symptom | Go to |
|---|---|
| `unity: command not found` right after installing | §Install — open a new shell |
| A non-zero exit you must decide whether to retry; a CI step exits `2` and you cannot see which flag | §Exit codes |
| A headless `Unity -batchmode …` exits `198` ("No valid Unity Editor license"), `1`, `2` or `3` | §The other CLI → `reference/editor-binary.md` |
| A batch run that exits `0` having done nothing, or with no results file | skill `unity-debug` |
| An Editor audit (`KitAudit`, `LightingAudit`) as a CI exit code | `reference/batch-audit.md` |
| "install Unity 6000.x with the Android module", create a project | §Editors, modules, templates, projects |
| "wire Unity into an agent via MCP" | `reference/mcp-and-shell.md` |
| Every headless command fails at once on a machine that worked yesterday | §Auth and licence |
| A flag from a tutorial is rejected; a grep on the CLI's error text stopped matching | §The conventions |
| `unity run` refuses to start | §Running — it reserves some e