Công nghệ
Unity CLI 1.0 Exits Beta for Agent-Driven Game Development

Điểm chínhUnity CLI 1.0 thoát khỏi giai đoạn beta với cam kết tương thích bao trùm tất cả các bản…
Xem thêm
- Unity CLI 1.0 thoát khỏi giai đoạn beta với cam kết tương thích bao trùm tất cả các bản phát hành 1.x.
- Các tác nhân lập trình đã điều khiển khoảng 98% trong hơn 600 triệu lệnh được chạy kể từ ngày 20 tháng 7 năm 2026.
- Giấy phép Build Server hiện bao gồm các tác nhân và tự động hóa chạy trên các Editor không giao diện hoặc container.
Unity Technologies took Unity CLI 1.0 and its Pipeline package out of beta on 17 tháng 11, 2026, announcing the release at Unite Tokyo. The tools let developers and coding agents manage Unity installations and projects, control a running Editor and check results from the terminal, with a new compatibility commitment covering 1.x releases.
The CLI entered beta on 15 tháng 7, 2026 as one binary for installing and managing Unity Editors, modules and projects. More than 17 beta releases followed, and the latest Unity Hub installs the CLI automatically. Unity said more than 350,000 logged-in users have run over 600 million commands since 20 tháng 7, 2026, with coding agents and other automation accounting for about 98% of runs. That reported usage explains why 1.0 prioritizes unattended Editor work alongside commands entered directly by developers.
Agent Setup and Editor Control
The Pipeline package lets the CLI drive a running Editor, allowing an agent to open a project, issue commands, enter Play mode and read the result. The unity setup command installs the official Unity plugin for Claude Code, Codex, Grok Build or Google Antigravity. Meanwhile, unity skill install --all provides Unity’s skills to every agent on a machine, and unity skill sync keeps them current.
Agents without an official plugin can still work with Unity through the CLI, as can scripts, test runners and CI jobs with no AI involved. That makes the command-line interface relevant to conventional development automation as well as agent-led workflows.
Several 1.0 changes address failures that can stop an unattended session. The CLI can identify and answer a dialog waiting in the Editor, preventing a script or agent from hanging on an unseen popup. The unity open --until-ready command waits until the Editor can accept commands, while distinct exit codes identify a busy Editor, a blocking dialog or a network outage.
Builds, Projects and Scripting
The unity build --target command builds in the Editor that already has the project open, and unity pipeline cloud-build sets up cloud build targets from the terminal. For version control, unity vcs identifies the asset behind each scene or prefab change and can summarize a pull request without switching branches. For new work, unity projects create adds the Pipeline package and can install the Editor required by the project.
The release also standardizes scripting behavior. Every listing and stream uses the same JSON shape, short flags have consistent meanings, --project-path works across commands, and the CLI never prompts in CI. Projects can pin a CLI version range. Unity said commands, flags and output will remain compatible across 1.x releases, with deprecation warnings and time to update before anything is removed.
The CLI is a native binary on macOS, Linux and Windows, available through Homebrew, winget and APT. Its unity self-update command retains the last three versions for rollback. Security fixes across installs, skills and project linking prevent a cloned repository from running its own programs in place of the genuine ones.
Licensing Covers Automated Work
The Build Server license now covers agents and automation in addition to builds. One license per instance allows agents to run on a headless Editor or in a container on any computer. Unity said a supported headless Unity Editor in a Linux container is coming soon for CI, build machines and agents.
Unity also plans terminal commands for AI Generators, Live Games and Build Automation, together with accounts designed for agents.
Taken together, the compatibility policy, unattended Editor controls and Build Server licensing give development teams one terminal-based route for conventional CI and agent-led work, extending the CLI’s original role in installation and project setup.













