Unity CLI 1.0 leaves beta, letting coding agents build and test in the Editor
By GameSlash
Unity’s command-line tool and local Pipeline package are now stable, connecting coding agents and scripts to a running Unity Editor.

Unity announced at Unite Tokyo on November 17 that Unity CLI 1.0 and the local Unity Pipeline package have left beta. The terminal tool lets coding agents and scripts work with a running Unity Editor, helping developers compile and test a game without repeatedly switching tools.
The command unity setup installs Unity’s official plugin for Claude Code, Codex, Grok Build or Google Antigravity. An agent can open a project, run Editor commands, enter Play Mode and inspect results; developers remain responsible for reviewing and testing its changes.

In a Unite Tokyo demonstration, Unity showed Claude Code building a first-person puzzle prototype: the agent wrote code, compiled it, read errors and playtested the project. Unity also says version 1.0 can detect blocking Editor dialogs and build through an Editor that already has the project open.
The CLI is available on Windows, macOS and Linux. Unity says current versions of Unity Hub install it; developers can consult the official documentation to get started. The separate browser-based Unity Pipeline API shown at the event remains in beta.