Skip to content
digital_developer
Game DevUnity CLIPipeline packageUnity HubUnite Tokyo

Unity CLI 1.0 and Pipeline package leave beta, adding agent setup and CI-safe output

Unity announced at Unite Tokyo that the Unity CLI and the Pipeline package (com.unity.pipeline) are out of beta at version 1.0. The release adds stable output, agent setup commands and a compatibility commitment for 1.x.

Digital Developer Desk, 14h ago, 3 min read

Image: Unity blog

Unity says the Unity CLI and the Pipeline package are out of beta at version 1.0, announced at Unite Tokyo. The CLI is a single binary that installs and manages Editors, modules and projects from the terminal. The Pipeline package lets the CLI drive a running Editor, so a script or agent can open a project, run a command and check the result. The beta began on July 15, 2026, and Unity shipped more than 17 beta releases. If you are on the latest Unity Hub, the CLI is already installed.

Unity gives usage figures for the period since July 20. More than 350,000 logged-in users ran more than 600 million commands, and about 98% of those runs came from coding agents and other automation. Unity says many 1.0 changes began as bug reports, including commands that reported success when they had not succeeded, dialogs that blocked remote sessions, and scripts that broke when output changed shape.

For agents, unity setup installs the official plugin for Claude Code, Codex, Grok Build or Google Antigravity. unity skill install --all adds Unity's skills to every agent on the machine, including VS Code, GitHub Copilot, Qwen Code and OpenCode, and unity skill sync keeps them current. The CLI can now see and answer a dialog the Editor is waiting on, so sessions no longer hang on a hidden popup. Agents without an official plugin can still work through the CLI, as can scripts, test runners and CI jobs with no AI involved.

Several changes target automation. Every listing and stream now uses the same JSON shape, short flags mean the same thing across commands, --project-path works everywhere, and the CLI never prompts in CI. Exit codes signal when the Editor is busy, a dialog is blocking it or the network is down, and you can pin a CLI version range per project. unity build --target builds in the Editor that already has the project open, and unity pipeline cloud-build sets up cloud build targets. unity open --until-ready waits until the Editor can take commands.

Other additions include unity vcs, which names the asset behind each change in a scene or prefab and can summarize a pull request without switching branches. unity projects create adds the Pipeline package to new projects. unity projects audit runs Project Auditor and writes a report. The CLI is a native binary on macOS, Linux and Windows, available through Homebrew, winget and APT. unity self-update keeps the last three versions for rollback, and Unity lists security fixes so a cloned repository can't run its own programs in place of the real ones.

On licensing, the Build Server license now covers agents and automation as well as builds. One license per instance lets you run agents on a headless Editor or in a container, on any computer. Unity lists a Linux containerized Editor as coming soon, built for CI, build machines and agents. Next, Unity says it plans commands for AI Generators, Live Games and Build Automation, plus accounts built for agents.

Sources

Get the daily brief

The five stories that matter, every weekday morning. Free.