Unity CLI and the Pipeline package reach version 1.0 with a compatibility guarantee across 1.x

  • PublicPublic
  • 17 Nov, 2026
Unity CLI and the Pipeline package reach version 1.0 with a compatibility guarantee across 1.x

The Unity CLI and the Pipeline package (com.unity.pipeline) have left beta and reached version 1.0, announced at Unite Tokyo. The CLI is a single binary that installs and manages Unity Editors, modules and projects right from the terminal. The Pipeline package lets the CLI control a running Editor on the local machine: a script or an agent can open a project, execute a command and verify the result. The latest Unity Hub already installs the CLI automatically.

During the beta, Unity shipped more than 17 releases and added official plugins for Claude Code, Codex, Grok Build and Google Antigravity. Through them, agents get skills written by Unity's own teams. The same skills are public in the Unity skills repository on GitHub, so any agent can use them. Since July 20, over 350,000 logged-in users have run more than 600 million commands, and about 98% of those runs come from AI coding agents and other automation. The typical pattern: a developer sets up Unity, and then an agent works inside a live Editor.

Studio feedback drove many fixes in 1.0. Commands no longer report success when they actually failed, dialogs no longer block remote sessions, and scripts no longer break when the output format changes. The full list of changes is available in the release notes, and it can also be viewed with the unity changelog command. Version 1.0 also comes with a stability promise: commands, flags and output format will remain compatible across all 1.x releases. If something does have to break, a deprecation warning will come first, and users will have time to move to the new option before the old one is removed.

Through the CLI, an agent opens a project, runs commands in the Editor, enters Play mode and reads the result. With the official Unity plugin, it also gets skills for specific tasks: building UI, setting up lighting or adding in-app purchases. Agents without an official plugin can still work through the CLI, as can ordinary scripts, test runners and CI jobs where no AI is involved. The Build Server license now covers not only builds but also agents and automation: one license per instance allows running agents in a headless Editor or in a container, on any computer.

Next up is a containerized Editor for Linux: an officially supported headless Unity Editor in a Linux container for CI, build machines and agents. Unity also plans to add commands to the CLI for AI Generators, Live Games and Build Automation, create accounts designed specifically for agents, and keep the frequent release cadence used during the beta.