Unity CLI 1.0.0.20014

What's new in 1.0.0.20014

Highlights of 1.0.0-beta.14 (full notes at the release notes URL):

• unity config path prints where the CLI keeps its configuration: the settings file and the directory that holds it.
• unity terms accept <version> accepts the Unity Editor Software Terms for an installed Editor, so it opens without the "Unity Editor Software Terms" dialog, as a container or provisioning script needs.
• The CLI now recognizes when GitHub Copilot runs it, from VS Code's agent terminal or the Copilot CLI.
• unity releases --operating-system <windows|macos|linux> lists another operating system's releases, and unity install <version> --dry-run --operating-system <os> shows what that system's Editor and modules would download, so you can plan a Windows build machine from a Mac.
• When the CLI is signed out and Unity Hub is signed in, unity auth login shows the Hub's account and the unity auth switch command that uses it in the CLI with no browser sign-in, then continues with the browser sign-in.
• unity open --until-ready (and unity projects open --until-ready) now names three dialogs the way unity status does: OPEN_BLOCKED_BY_DIALOG_SAFE_MODE for "Enter Safe Mode?" (quoting up to three compile errors from the Editor's log), OPEN_BLOCKED_BY_DIALOG_GRAPHICS_API for the Windows "Auto Graphics API Notice", and OPEN_BLOCKED_BY_DIALOG_SOFTWARE_TERMS for "Unity Editor Software Terms".
• unity status reports an Editor waiting at the "Enter Safe Mode?" prompt with its own error code, STATUS_BLOCKED_BY_DIALOG_SAFE_MODE, and quotes the first compile errors from the Editor's log when it can read them.
• unity cloud project --help now ends with a pointer to unity projects link cloud, where a local project is linked to Unity Cloud, and unity projects link cloud --help points back to unity cloud project for listing projects and setting a default.

Full release notes »