Install editors, automate CI, and drive a running Editor or dev build from the terminal. The Unity CLI and com.unity.pipeline package give scripts and AI agents a fast, structured way to operate Unity.

The Unity Blog offers insights, tutorials, and updates on Unity, a popular game engine used for building interactive experiences across various platforms. Covering topics such as game development, virtual reality, and augmented reality, the blog provides resources for game developers and creators. Developers can learn how to use Unity's features, tools, and APIs to build immersive games, simulations, and interactive experiences.

Unity

Unity has released a standalone Unity CLI binary that lets developers manage editors, modules, projects, and authentication entirely from the terminal without needing the UI. The CLI supports structured JSON/TSV output, clear exit codes, and service-account auth for CI pipelines. Alongside it, the experimental com.unity.pipeline package enables the CLI to drive a running Unity Editor or dev Player build over a local API. Developers can expose custom commands using a [CliCommand] attribute on static methods. A key feature, unity command eval, runs arbitrary C# code live inside a running Editor via a Roslyn-based REPL with no recompile or domain reload needed. Together, these tools create a tight feedback loop for AI agents to observe, act on, and verify changes in a live Unity project.

Meet the Unity CLI: manage Unity from your terminal

Every day, we’re getting more and more work done at the terminal, and that’s great!

Structured output, clear exit codes, and service-account auth are exactly what a useful CI tool needs. The live C# eval is powerful too, though I’d put tight guardrails around it in shared environments.

finally i can get rid of the bloat that is the hub