Compare the Unity CLI and Unity Pipeline package
Learn how the Unity CLI and Unity Pipeline work together, and which tool you need to automate workflows in a running Unity Editor.
Read time 2 minutesLast updated a month ago
The Unity CLI is a standalone command-line tool that Unity Hub installs automatically. You can also install it manually on your machine. The Unity CLI manages Unity Editors and modules, opens projects, and automates Unity workflows. You can also use the CLI to install the Unity Pipeline package in your project.
The Unity Pipeline package works with the Unity CLI so you interact with a running Unity Editor. After you install the package, the CLI can connect to the Editor and execute commands in the Editor context. The CLI and Pipeline package serve different purposes, but you use them together to automate workflows in a running Unity project. For a detailed comparison, refer to the following table:
Category | Unity CLI | Unity Pipeline package |
|---|---|---|
| Type | A standalone command-line tool. | A Unity package that you install with the Unity CLI. |
| Installation | Automatically installed with Unity Hub, or install it manually on your machine independently of any Unity project. | Install in your Unity project using the Unity CLI. |
| Purpose | Use it to manage Editors and modules, open projects, and automate Unity workflows. | Use it to run an in-Editor HTTP server that the CLI connects to, so you can run commands in the Editor context. |
| Usage | Run commands in a terminal, or let an AI agent run them for you. | Run commands in the Editor through the CLI. |
| Extensibility | Install packages such as Unity Pipeline to add new commands. | Define your own commands in C# with the package's command framework. Use |
| Examples | Use | Use |