What’s new in Unity CLI?
Install Editors, manage projects, automate builds and tests, and connect coding agents to Unity without the Hub desktop app.
Reviewed · Features and release highlights from Unity’s documentation.
Recent changes
Latest reviewed: 1.0.0-beta.14 ·
Better unattended workflows and more control for agents
- beta.14: Open a project with --until-ready to wait for the Editor. Blocking dialogs now report a useful error instead of leaving automation waiting indefinitely.
- beta.14: Install an Editor into a chosen workspace with --download-directory, and preview another operating system’s downloads with --dry-run --operating-system.
- beta.14: Filter which Editor tools an MCP client can see with --tools and --exclude-tools. Discover old command names and their replacements with unity command --obsolete-command-names.
- beta.14: Project creation can skip default scaffolding with --bare and reports individual setup steps in structured output. New configuration-path and Editor-terms commands support machine setup.
- beta.14: Hardened downloads, credential handling, and diagnostic output. Check the full release notes for platform-specific fixes and security changes.
- beta.12: Create projects with Pipeline already installed using --with-pipeline, wait for Editor readiness, and see package release summaries during Pipeline upgrades.
What you can do
Browse the documented feature areas. Each reference includes command details; availability depends on your installed version and project packages.
Editors and platform modules
Discover Unity releases, install or remove Editors, add platform modules, register existing installations, and choose an Editor default.
Read editors and platform modules referenceProjects, templates, and assets
Create, clone, open, and organize projects. Manage reusable templates and inspect, import, or export .unitypackage assets.
Read projects, templates, and assets referenceBuilds and tests
Run batch builds and Edit Mode or Play Mode tests, save NUnit reports, discover Build Profiles, and recompile scripts. Watch a project to repeat checks after edits.
Read builds and tests referenceAccounts, licenses, and cloud projects
Manage sign-in and local licenses, inspect organizations and projects, and link local work to Unity Cloud.
Read accounts, licenses, and cloud projects referenceUnity-aware version control
Work with Git, GitHub, GitLab, or Unity Version Control. Check .meta pairing, configure scene merging, inspect conflicts, and compare scene changes by object and component.
Read unity-aware version control referenceCollaboration
Work with Unity Collaboration annotations, attachments, thumbnails, reactions, and linked Jira issues.
Read collaboration referencePipeline and connected Editors
Install or upgrade Pipeline, discover running Editors, send commands, inspect command schemas, and track detached jobs. Cloud-build and automation commands also read hosted service information.
Read pipeline and connected editors referenceCoding agents and MCP
Expose Editor tools through Model Context Protocol, configure supported clients, and install or read Unity’s CLI skill. The command manifest gives agents structured discovery.
Read coding agents and mcp referenceDiagnostics and configuration
Check environment health, inspect logs, manage proxy and Accelerator settings, switch saved contexts, manage plugins, and find version-specific documentation.
Read diagnostics and configuration referenceStructured automation output
Use JSON, NDJSON, or TSV for scripts. Check documented exit codes and output contracts so failures and incomplete results are handled correctly.
Read structured automation output referenceUpdates and shell tools
Check the CLI version, read its changelog, and update it. Shell completion and an interactive session make repeated terminal work easier. Package-manager installs have their own update rules.
Read updates and shell tools referenceSetup and compatibility
Supports macOS 14+, Windows 10 21H1+, and supported Linux distributions with glibc 2.34+ (including Ubuntu 22.04+ and RHEL 9). Editor automation also needs Pipeline and Unity 6+. Build machines still need the right Editor, platform modules, and license.
Installation and setup instructions
Install the CLI for your operating system using the instructions above, reopen your terminal, then check your setup.
unity --version
unity --help
unity auth login
unity editors -i
unity doctor
# Discover commands for your installed version:
unity commands --grep build