The Unity CLI: manage Unity from your terminal

That landed as a welcome but overdue step toward making Unity behave like modern infrastructure instead of a giant desktop app. People immediately connected it to the ugly parts of everyday Unity work: fragile CI, manual editor installs, test suites that only run inside the editor, and the inability to do parallel work cleanly because the editor wants an exclusive lock on the project directory. Several commenters said they already work around this by isolating core game logic into a separate plain C# project, using Unity mostly as the renderer and integration layer. In that setup, you can benchmark, unit test, and automate most of the important code without dragging the editor into every loop. The practical optimism was strongest around build and release automation. A shell-friendly interface means fewer brittle editor button clicks and fewer custom post-build hacks. People also highlighted a more interesting use case than just “generate code with AI”: giving tools an entry point into a running game in dev mode so they can inspect state, trigger scaffolding, and reproduce hard bugs. The argument that mattered most was not whether Unity is “doing AI now.” It was that Unity is finally exposing enough control surface for serious automation, and that could tighten the feedback loop for both humans and agents if Unity follows through with things like easier installs and container-friendly editor builds.