
Unity has taken its command-line tool out of beta: version 1.0.0 of the Unity CLI is dated 12 November in the release notes, and Unity announced it at Unite Tokyo in a blog post on 17 November. The Pipeline package (com.unity.pipeline), which lets the CLI drive a running Editor, also leaves beta. The tool first shipped as a beta on 15 July and went through more than 17 beta releases.
Unity’s post says more than 350,000 signed-in users have run over 600 million commands since 20 July, and repeats that about 98% of runs come from coding agents and other automation. In October we reported Unity’s first figures, 200 million events from 226,000 users, and why that 98% means “not a person at a terminal” rather than a precise AI share. Version 1.0 is built for that audience: most of the changes concern exit codes, flags and output that scripts and agents parse.
What Unity promises for 1.x
Unity’s post commits to keeping “commands, flags and output” compatible across 1.x releases. When something must change, users get a deprecation warning and time to update before it is removed. Projects can also pin a range of CLI versions. Other behaviour now guaranteed:
- the CLI never prompts in CI;
- listings and streams use one JSON shape, and short flags mean the same thing in every command;
- exit codes tell a script whether the Editor is busy, a dialog is blocking it or the network failed;
- the CLI can detect and answer dialogs an Editor is waiting on, so scripts do not hang.
The licensing change matters for teams that already run agents on build machines. According to Unity, the Build Server license “now covers agents and automation, not only builds”, and one license per instance allows agents to run on a headless Editor or in a container. A supported headless, containerised Linux Editor is listed as coming soon, not shipped.
Exit codes and flags that changed in the last three builds
The compatibility promise starts at 1.0, so anything written against a beta should be checked. The 1.0.0 notes mark two changes as breaking:
unity recompilenow exits with code 12 instead of 7 when no Editor answers, matchingunity command;unity closeandunity projects closenow fail with exit 11 andPROJECTS_CLOSE_NOT_A_PROJECTwhen the path has noAssetsorProjectSettingsfolder. Before, they succeeded withreason: "not_open".
The same release renames build --output-path to build --output and sets one rule for every command that writes files: -o, --output names a file and --output-dir names a directory. unity uninstall with several versions and unity help with an unknown word now exit with code 2.
The two betas before it changed more. Beta 16 (3 November) added exit 17 (UNAVAILABLE) and 18 (AWAITING_INPUT), both of which used to be 6, and moved unreachable services to exit 7 (NETWORK_UNREACHABLE). It also stopped unity setup all registering the Unity MCP server for agents that can run shell commands; unity mcp configure <client> adds it back. unity command --format json now prints the result without its old envelope. Beta 17 (5 November) made unity mcp configure exit 1 instead of 6 when it cannot write a config file, made projects link vcs --rollback --delete-remote require --yes, and deprecated --git-token-stdin in favour of --git-token-from-stdin.
Sign-in, telemetry and verifying downloads
Three changes in 1.0.0 affect build machines rather than scripts. Sign-in no longer falls back to a plain file when the system credential store is unavailable, so a headless Linux runner without a keyring needs unity auth login --insecure-storage to keep the old behaviour. Each release now ships a signed SHA256SUMS.asc for checking downloads with gpg. Setting UGS_CLI_TELEMETRY_DISABLED turns off usage data and telemetry, the source of Unity’s 600 million figure. The winget package now carries stable releases only.
Unity’s post lists Claude Code, Codex, Grok Build and Google Antigravity as agents with official plugins, and says unity skill install --all also covers VS Code, GitHub Copilot, Qwen Code and OpenCode; the skills are public in Unity’s GitHub repository. Next on Unity’s list are CLI commands for AI Generators, Live Games and Build Automation, and accounts built for agents.
Disclosure: GameTales uses Claude Code, an Anthropic product named in Unity’s post, for research assistance. Anthropic had no involvement in this article, which is based on Unity’s published post and release notes.