--- title: Unity CLI release notes for October 2026 product: Unity command-line interface (CLI) canonical: https://docs.unity.com/en-us/unity-cli/release-notes/2026/october last_updated: 2026-11-12 generated_at: 2026-11-14T03:34:13.723Z locale: en-us --- # Unity CLI release notes for October 2026 > Learn about the Unity CLI releases in October 2026. This page contains the release notes for the Unity CLI versions released in October 2026, from newest to oldest. ## 1.0.0-beta.15 **Release date:** October 29, 2026 * **Security** * Linking a project to Unity Version Control now sends the repository request only to the organization it names, even when the organization's name contains a slash, a question mark or dots. * The CLI no longer runs a program found through a relative `PATH` entry such as `node_modules/.bin`. Only absolute `PATH` entries are searched, so a cloned repository cannot put its own `unity`, `claude`, `zip` or `tar` ahead of the real one. * Skill installs and refreshes (global and `--local`) now refuse a skill folder that contains a symbolic link or junction as a subfolder, on every platform. Before, a repository could use one to make the install write or delete files outside the project. * `unity install --resume` no longer resumes a paused Editor download on Windows, or as root (for example under `sudo`), when the current Unity release data doesn't list that Editor or gives no checksum for it. Start a fresh install instead. * `unity install-modules`, `unity editor module add` and `unity install --resume` now check a module's download against the current Unity release data before installing it on Windows, and on every platform when the module runs its own installer command. A module that can't be checked, for example while offline, isn't installed. * `unity install --resume` now takes a paused Editor download's address from the current Unity release data when it lists that version, and on Windows doesn't resume one it can't check. * `unity install` and `unity install-modules` no longer reuse or resume a file already in the download folder for a download the release data gives no checksum for. They download it again from the start, so a file someone else placed there is never installed in its place. * `sudo unity install` and `sudo unity install-modules` on macOS and Linux now check and install a copy of each download kept in a folder only root can open, so another program running as you can no longer swap the file between the checksum check and the install. As root, archives no longer restore their own file owners or permissions, and `tar` and `unzip` come only from the system folders, never from your `PATH`. * `unity ci init` workflows now run `unity license activate` with the serial in the step environment, and mask it in the GitHub Actions log, so the serial no longer appears in the process list. The service-account secrets are set only on the steps that use them, not on the whole job. * `unity build` reads the Android keystore and key alias passwords from `UNITY_ANDROID_KEYSTORE_PASSWORD` and `UNITY_ANDROID_KEY_ALIAS_PASSWORD` when you pass no `--android-keystore-password` or `--android-key-alias-password`. The flags still work and take precedence. * The Unity Editor that `unity build`, `unity test` and other batch commands start no longer inherits `UNITY_GITHUB_TOKEN` or `UNITY_GITLAB_TOKEN`. * Crash reports no longer include your account name, your project's name, or the folders of a file outside your home directory. A path outside your home keeps only its file name, and your home directory reads as `~` wherever it is. * `unity mcp` now cleans every text in the tool schemas it passes from the Unity Editor to your AI agent, not only the tool descriptions, and caps their size. It also refuses a call to a tool the Editor did not list, and stops reading an oversized tool catalog. * Unity Version Control workspace names made from a repository name now replace control characters and drop leading dashes, so a crafted repository name can no longer be read as a command option. * **Added** * `unity bug` can file an issue against a plugin: `--area` takes a plugin's name, such as `ugs` or `plastic`, and on a terminal the area question offers each plugin you have installed. A plugin area attaches that plugin's newest log files, redacted like the other logs, and every report now lists your installed plugins and their versions. * `unity doctor` names where each installed plugin writes its logs, under the external components, and as `logDirectories` in `--format json`. * `unity license server health` asks your floating license server how it is, directly on its `/v1/status` endpoint. It needs no sign-in and no licensing client. * Plugins now receive what `unity` knows when it runs them: the output format, whether they may prompt, the current Unity project and its Editor version, the active Unity Cloud organization and project, the signed-in user (never a token), whether a person, a CI system or an AI agent is running it, and the analytics and crash-report settings, as `UNITY_CLI_CTX_*` environment variables and one `UNITY_CLI_CTX_JSON` document. `UNITY_CLI_INVOKED_AS` and `UNITY_CLI_CORE_VERSION` now reach every plugin, not only built-in tools. * `unity projects audit` opens Project Auditor in your project's running Editor, ready for you to run the analysis. It first installs or updates Project Auditor and its rules package when the Editor needs them, then opens the window on the page for `--workflow` (`upgrade` by default, or `optimization`, `urp` or `coreclr`). * `unity setup qwen` installs Unity's agent plugin into Qwen Code by running `qwen extensions install Unity-Technologies/unity-agent-plugin:unity --consent`, then `qwen extensions enable unity`. Like `unity setup codex`, it reports an existing install instead of reinstalling (one Qwen Code has disabled for the current folder counts as not installed, and is turned back on), takes `--dry-run` and every output format, and fails with `QWEN_NOT_FOUND` when `qwen` isn't on your PATH. * `unity skill install opencode` installs the Unity skills into OpenCode, in `~/.config/opencode/skills`, or `.opencode/skills` with `--local`. OpenCode also loads `.claude/skills` and `.agents/skills`, so when one of those already holds a skill, it warns and skips it rather than loading two copies; pass `--yes` to install it anyway. * `unity install --download-only` downloads and verifies an Editor and its modules into the Hub's download folder without installing anything. With `--operating-system`, it can fetch another operating system's Editor, which `unity install` refused before. * `unity auth token` prints an access token from your CLI sign-in, alone on stdout, so a script or another tool can call Unity services without its own sign-in flow: `TOKEN=$(unity auth token)`. An expired token is refreshed first, a service account gets a token for its credentials, and `--json` adds the expiry. * `unity mcp --cli-tools` adds read-only tools for status, installed editors, projects, releases and doctor to the MCP server, so a client with no shell, such as Claude Desktop, can call them with no Editor running. Each answers with the command's JSON output. * `unity mcp` lists four tools for detached Editor jobs next to the Editor's own, so an agent can run work that takes longer than a tool call may wait: `job_start` starts one of the Editor's tools as a job, the way `unity command --detach` does, `job_status` reads the job, `job_wait` waits up to `timeout` seconds (30 by default, at most 45) and says whether it is still running, and `job_cancel` asks the Editor to cancel it. `--exclude-tools "job_*"` hides them. * `install.sh` and `install.ps1` now set up the coding agents they find on your machine right after installing, then show your account, license and Unity Editors. In an interactive terminal they first list the agents found, all selected, so you can untick any to leave alone. * `unity skill install ` installs the `new-unity-project` skill beside `unity-cli`, so clients that read only skills can guide a new project from an idea to a running one. A client whose plugin already provides `unity-cli` keeps leaving `new-unity-project` to the plugin too when that plugin also ships it, unless you pass `--yes`. * `unity setup all` sets up every coding agent it finds, bare `unity setup` on a terminal lets you pick which ones from a checklist, and both finish with a state block showing your account, license, editors and connectivity, with the next command for anything blocking (machine formats carry each blocker as a `notifications` entry). * `unity projects create --install-editor` installs the Editor version when it isn't installed, waits for the install, then creates the project. `--module` and `--accept-eula` pass modules and their license agreements to that install. * `unity projects create` adds Cinemachine to every new 3D project, at the newest release that supports the project's Unity version. 2D projects and templates that already include it are left as they are. `--bare` leaves it out. * `unity projects create` turns on Run In Background in the new project's Player settings, so Play mode keeps running while the Editor is not focused. `--bare` leaves it out. * `unity projects create` sets up anonymous player sign-in when it links the project to Unity Cloud. It adds the Authentication package and a startup script that signs the player in before the first scene loads, so cloud save, telemetry and other services have a player ID. * `unity docs cache add` downloads a version's documentation as Markdown for offline use: the manual by default, and the scripting API reference too with `--api`. `unity docs --content` then reads cached pages without the network, and `unity docs toc` and topic lookup use the cached page list when docs.unity.com can't be reached. * `unity setup copilot` installs Unity's agent plugin, with its Unity skills, into GitHub Copilot CLI by running `copilot plugin marketplace add Unity-Technologies/unity-agent-plugin`, then `copilot plugin install unity@unity-agent-plugin`. Like `unity setup codex`, it reports an existing install instead of reinstalling, and takes `--dry-run`. * `unity assets import --include ` imports only part of a package: the entries whose path matches, everything under a matching folder, and the folders above them. Repeat `--include` to select more, with a glob (`*` and `?` stay inside one folder, `**` spans folders) or a plain path such as `Assets/Art/Hero.png`. * The `--help` of every `unity collaboration` command now ends with examples you can copy. * The `--help` of every `unity vcs` and `unity pipeline` command now ends with examples you can copy. * The Linux deb and rpm packages now install a `unity` man page, so `man unity` lists every command, its options and the exit codes. Each release also publishes it next to its downloads as `unity.1.gz`. * `unity commands --json` now reports each command's `stability`: `stable`, `preview` or `deprecated`. A bare command group's `--json` answer carries it too. * A project can pin the unity CLI versions it supports with `cli.version` in `ProjectSettings/UnityCliConfig.json`, an npm-style range such as `"^1.0.0"`. A command run in the project with a CLI outside that range prints a warning, and in CI it stops before doing anything, with exit code 1 and error code `CLI_VERSION_OUT_OF_RANGE`. * `unity assets inspect` says whether a package is signed: `signed` in `--format json` and `ndjson`, and a `Signed:` line in the human output. It checks that a signature is present, not that it is valid. * `unity assets import` warns when a package has no signature and reports `signed` in `--format json` and `ndjson`. Pass `--require-signed` to refuse an unsigned package before the Editor starts. * `unity mcp configure` now finds entries left by the deprecated Unity MCP server from the AI Assistant package and offers to replace them, so the client keeps one Unity server. `--replace-legacy` replaces them without asking, `--dry-run` shows what would change, and `claude-code` prints the `claude mcp remove` command to run. * `unity install --set-default` makes the installed Editor the default once the install succeeds, so `unity install latest --set-default` replaces running `unity install latest` and then `unity editors default latest`. The json and ndjson result report the stored version as `data.defaultVersion`. * `unity doctor --ci --skip-license` skips the license check, for runners that get a license another way. * On macOS, each release now also publishes a notarized installer, `unity-darwin-arm64.pkg` and `unity-darwin-x64.pkg`, with the notarization ticket attached. It is the installer the Homebrew cask will use, and the cask moves to it in a follow-up. * `unity plugin install` and `unity plugin upgrade` show a plugin's license terms and ask you to accept them before anything downloads, for a plugin that has terms. A run that cannot ask, such as one with `--non-interactive`, stops with an error that names `--accept-eula`. * `unity setup claude`, `unity setup codex`, `unity setup grok` and `unity setup copilot` offer to install the Unity skills instead when the agent's CLI is missing or its plugin can't be installed. `--yes` installs them without asking. * `unity skill install ` installs every Unity skill from the Unity-Technologies/skills repository, at the commit this CLI release pins, beside the `unity-cli` skill. Each skill is checked against the pin before anything is written, and the source can't be redirected. * `unity skill show --skill new-unity-project` prints the new-unity-project skill the CLI embeds, the same way `unity skill show` prints the unity-cli skill. `--path` and `--list` work with it too. * `unity pipeline cloud-build` and `unity pipeline automation` now start, follow and act on work: `builds start`, `cancel`, `steps`, `failures`, `artifacts`, `log --follow` and `download`, and `pipelines trigger`, `jobs watch`, `logs`, `terminate`, `resume`, `approve` and `reject`. `builds cancel`, `jobs terminate` and `jobs reject` ask first unless you pass `--yes`. * **Changed** * `unity command` reaches the Editor through the Pipeline package's own connection when the Editor offers one, and over HTTP otherwise. An Editor whose Pipeline HTTP server is turned off now answers too. * `unity status` reports an Editor whose Pipeline HTTP server is turned off instead of showing it as unreachable, and `unity pipeline editors` shows each way to reach the Editor, with a `pipelineServer.endpoints` array in its JSON. * `unity pipeline upgrade` now moves a project to the Pipeline package's latest published version, so a new release is available as soon as it is published, without a CLI update. `unity pipeline install`, `unity pipeline list-versions`, `unity pipeline editors` and the Pipeline step of `unity projects create` resolve versions the same way. * When `unity cloud org`, `unity cloud project` or `unity cloud status` fails, it now prints the usual error details (the error code, the log file, and how to get more detail) and records the failure in the log, so it shows up in `unity logs` and `unity bug`. JSON output and exit codes are unchanged. * When a `unity collab` command fails, it now prints the usual error details in `--format human` (the error code, the log file, and how to get more detail) and records the failure in the log, so it shows up in `unity logs` and `unity bug`. JSON output and exit codes are unchanged. * When `unity pipeline automation` or `unity pipeline cloud-build` fails, it now prints the usual error details (the error code, the log file, and how to get more detail) and records the failure in the log, so it shows up in `unity logs` and `unity bug`. JSON output and exit codes are unchanged. * `unity skill install` now recommends `unity setup all` to set up every agent client on the machine, in place of `npx skills add Unity-Technologies/skills`. * Without `--editor-version`, `unity projects create` uses the default Editor version, else the newest installed Editor, else the latest Unity release when no Editor is installed. `--editor-version latest` and `lts` now name the newest official and LTS releases rather than the newest installed Editor. * `unity projects create` checks its prerequisites before it asks anything, downloads a template or starts the Editor: an active license always, and, while the project links to Unity Cloud, a signed-in account, a reachable network and a chosen organization when you belong to several (pass `--cloud-org` to choose). `--no-cloud` removes the Unity Cloud ones; `--bare` does not. * `unity auth login` now ends with a short summary of your machine: your account, organization, license, installed Editors and the next command to run. With `--format json` or `--format ndjson`, anything that blocks you from creating a project, such as no installed Editor or an unreachable network, is listed in the result's `notifications`. * More commands take the project as `--project-path`: `assets export`, `assets import` and `auth default` take it instead of `--project`, and `templates create`, `templates pack`, `projects link`, `projects unlink` and the `vcs` commands that act on a project accept it next to their path argument. These commands, and `recompile`, also read `UNITY_PROJECT_PATH` when no path is given. * `build run` takes the build to launch with `--build-path`, and `projects clone` takes the folder of the project to register with `--subpath`. * `pipeline install` and `pipeline upgrade` report a folder that isn't a Unity project with the same message as the other commands that connect to an Editor. * `unity templates`, `unity templates info`, `delete` and `edit` take the Editor version as `--editor-version`, like the rest of the CLI, and resolve `lts` and `latest` through the release catalog as `unity install` does. * `unity pipeline cloud-build targets`, `tooling os` and `tooling platforms` filter by Editor version with `--editor-version`. * `-e` means `--editor-path` on every command. `unity vcs merge-setup` and `unity vcs resolve` now accept it too. * `UNITY_EDITOR_VERSION` sets the Editor version on every command that takes `--editor-version`: `build`, `docs`, `install-modules`, `projects create`, `templates`, `vcs merge-setup` and `vcs resolve` now read it as well. The `pipeline cloud-build` filters don't. * An exported `UNITY_EDITOR_VERSION` or `UNITY_ARCHITECTURE` now steers `unity build`, as it already steered `run` and `test`: the flag wins, then the variable, then the project's version. `build` prints one line naming the variable when it does. * Passing a version to `--editor-path` fails with a hint to use `--editor-version`. * `releases` and `cloud projects` take `--offset ` to start a page part way through the results, the spelling every offset-paged list uses. The `releases` footer now says `Use --offset to see more`. * Every short flag now means one option on every command: `-f` is `--force`, `-i` is `--installed`, `-l` is `--list`, `-m` is `--module`, `-o` is `--output` and `-r` is `--releases`. Options that used those letters for something else show only their long name in help: `--follow`, `--input`, `--log-file`, `--modified`, `--reset` and `--output-path`. * Every `--format ndjson` stream now ends with one `{"type":"result"}` frame. Single-record commands such as `unity env`, `unity doctor`, `unity context current`, `unity editors default`, `unity install-path` and `unity diagnose update` answer with that frame alone, its `data` the same as `--format json`, and listings such as `unity logs`, `unity skills`, `unity command` and `unity install-modules --list` write their rows and then the frame. * Every row in an ndjson listing now starts with `"type":"row"`, so a script can tell a row from a `progress` or `result` frame. `unity templates` rows keep their own `type` (the template type) and carry no `"row"` marker. * Under `--format tsv`, the default when stdout is redirected, single-record commands such as `unity env`, `unity doctor`, `unity config proxy`, `unity install-path` and `unity editors default` print a `keyvalue` table with one row per field, named as in `--format json`. A script that reads `unity install-path` from a pipe now gets that table, with the path on the `path` row; use `--format json` and read `data.path` instead. * `unity logs --format tsv` and `unity skills --format tsv` now start with a header row, and `unity skills --format tsv` lists your installs instead of printing nothing. * The `command` field of `--format json` and `--format ndjson` output is now the full command path, such as `projects list` or `cloud org list`, the same in both formats and on success and failure. A script that matched on the old short names, such as `projects` or `proxy`, needs the full path instead. * Every listing now returns its rows in one shape. In `--format json`, `data` holds the rows as `items`, with `total` (`null` when the service doesn't report one), `nextPage` or `nextCursor` for the next page (`null` on the last), and `partial` (`true` when the listing stopped before it finished). * `unity doctor`, `unity env`, `unity diagnose proxy`, `unity diagnose accelerator` and `unity diagnose update` show their status as aligned label and value lines, in every language. The copy that `unity diagnose proxy` writes to the logs directory keeps its layout. * `unity pipeline editors` lists the open Unity Editors in a table, with any notes and the next step under it. When no Editor is open, it says so and suggests what to do. * With `--format tsv`, which is also the default when output is redirected, `unity cache info` prints one `key` and `value` line per field, named like its JSON fields, and `unity license status` prints the active licenses as a table with a header row, instead of sentences. * `unity cache info`, `unity auth status`, `unity license status`, `unity analytics status`, `unity config update-check`, `unity config proxy` and `unity language` show their status as aligned label and value lines, in every language. `unity license status` lists active licenses in a table, and `unity language` lists the available languages in one. * `unity projects` prints a table with a header in human output, also when its output is redirected with `--format human`. The columns that `--verbose`, `--editor-version`, `--modified`, `--cloud`, `--pipeline` and `--vcs` turn on are now table columns. * The anonymous once-per-run usage ping now stops when you turn analytics off (`unity analytics opt-out`, answering no at the first-run prompt, or turning it off in the Hub while signed in) and when `DO_NOT_TRACK` is set to any value but empty, `0` or `false`. `UNITY_NO_CLI_INVOKED_TELEMETRY` still stops it too. * The install scripts now install the latest stable release and no longer fall back to the latest beta. To install a beta, set `UNITY_CLI_CHANNEL=beta` before running the installer. * `unity self-update` keeps the last 3 versions it replaced instead of only one, and `unity self-update --rollback ` restores a specific one. `--rollback` on its own still restores the most recent. * `unity projects create`, `unity projects link` and the `unity language` picker no longer ask questions under `--non-interactive`, with `UNITY_NON_INTERACTIVE` set, or in CI, even on a terminal. `unity projects create --vcs uvcs` without `--vcs-region` then fails with an error naming `--vcs-region` instead of showing the region picker. * On a terminal, `unity editors upgrade` with no Editor named asks again which installed Editor to upgrade, `unity editor module add` asks you to accept a module's license terms (as `unity install-modules` does), `unity open` and `unity projects open` ask which project or Editor to use when several match, and the `unity collab` delete commands ask you to confirm. In CI nothing asks, even on a terminal: `unity install-modules` and `unity editor module add` then need `--accept-eula`, and a collab delete needs `--non-interactive`. * `unity mcp` now lists a title and MCP behavior hints for every Unity tool, so an agent client can run reads such as `scene get_hierarchy` without asking and still ask before anything destructive. A tool that deletes or clears data, takes `confirm`, saves a capture to a path you pick, or runs your code (`script eval`, `script eval_file`, `script run`) is marked destructive. * Unity CLI now tells you once, on its first run, that it sends crash reports and an anonymous usage ping, how to turn each off, and where to read the privacy policy. Runs in CI, scripts and agents get the same notice as one line on stderr. * Listing no longer needs a `list` word: `unity projects`, `unity templates`, `unity config`, `unity modules ` and `unity editors modules ` list on their own, with the same options and output, where they used to print their help. Bare `unity modules` and `unity editors module` now exit 2 with the missing `` error instead of printing help at exit 0. * The same goes for `unity auth accounts` (the stored accounts), `unity pipeline editors` (the running Editors), `unity cloud orgs`, `unity cloud projects`, `unity docs cache`, `unity vcs uvcs reviews`, `unity collab annotations`, `unity collab attachments `, `unity collab jira issues`, and the `unity pipeline automation` and `unity pipeline cloud-build` listings, such as `unity pipeline automation jobs` and `unity pipeline cloud-build builds`. Bare `unity collab attachments` now exits 2 with the missing `` error. * `unity projects link cloud` now describes itself as linking or connecting a local project to Unity Cloud, so `unity commands --grep "connect project cloud"` and `unity command --query "connect project cloud"` find it first. * A search that finds nothing (`unity commands --grep` and `unity command --query`) now ends with a line saying that multi-step workflows are documented in the `unity-cli` skill, and that `unity skill show` reads it. `--format json` carries the line in `hint`, and the exit code stays 0. * `unity recompile --format json` and `--format ndjson` now write the top-level `errors` and `warnings` arrays every other command writes. Each error is `{code, message}` with the compiler code (such as `CS1002`), and each warning is a `file(line,col): message` string, so a script can read compile results the same way for every command. * `unity projects create` no longer adds the Pipeline package on Unity 6000.5.0 to 6000.5.2, where it can't start, and tells you to update the Editor to 6000.5.3f1 or later. `unity status` on a project open in one of those Editors says the same instead of telling you to wait. * `unity plugin install` and `unity plugin upgrade` now install the agent skill a plugin ships into every AI client that already has the Unity skill, from `unity skill install` or the Unity agent plugin. Before, they only printed a hint to run `unity skill install`. * `unity setup all` gives clients that take only skills the full set of Unity skills, not just `unity-cli`. * **Removed** * The `list` subcommand of these groups is gone. `unity projects list`, `unity editors list`, `unity cloud org list` and the rest now fail as an unknown command, exit 2, and suggest the bare group instead. * **Breaking:** `unity projects new` is removed. Use `unity projects create --no-cloud`, which also never links to Unity Cloud. * **Breaking:** `unity list` is removed. Use `unity command`, which lists the tools the connected Editor offers. * **Fixed** * `unity auth login` now stays signed in on a Linux container or headless machine that has no Secret Service and blocks the kernel keyring, such as a Docker container with the default seccomp profile. The CLI saves the sign-in to a protected file in your user data directory, readable only by your user, and tells you once when it does. * The Windows file properties, the Linux deb and rpm packages and the npm packages now name Unity Technologies as the copyright holder and carry the Unity Terms of Service license. * On a machine without Unity Hub, a `cloudConfig.json` left by an older Hub or CLI no longer leaves the Editor on built-in default service URLs (the `environment-mismatch` warning in the CLI log). The CLI now tags and refills a cache that has no environment tag, keeping any keys it does not know. * `unity open` and the other Editor-launching commands now give the Editor the `seatinfourl`, `unauthenticatedurl`, `perf-events` and `socialdashboard` service entries, as Unity Hub does. The CLI used to refuse them as unsafe URLs even though Unity's own service config serves them that way. * While the Editor service is running, the CLI now fetches Unity's service config again every 15 minutes, as Unity Hub does, so the `cloudConfig.json` it wrote on a machine without Hub no longer goes stale. A cache Unity Hub wrote is still never touched. * `unity cloud orgs`, `unity cloud org set-default` and `unity cloud projects` no longer fail with "Unity-token exchange failed (Request failed with status code 401)" for a signed-in user whose access token the server stopped accepting before it expired. The CLI now refreshes the session and tries once more, and only asks you to run `unity auth login` when that fails too. * `unity vcs conflicts` no longer lets color or hide codes inside a file path change how the human and tsv tables look. The codes are removed from the path. * `unity shell --protocol ndjson` answers a request line with a repeated key or an unpaired surrogate escape with a `BAD_REQUEST` frame and keeps reading, instead of ending the session with an error. * Commands no longer pause for up to two seconds on their way out when usage data is turned on and the network is slow or unreachable. Sending usage data now gives up after half a second, and `DO_NOT_TRACK` skips it entirely. * `unity skill install claude-code` and `unity skill install codex` now install the skills your installed plugins ship even when an agent plugin already provides the Unity CLI skill. Before, a non-interactive run, such as an agent's headless mode, skipped those skills without saying so. * `unity shell` on a terminal remembers your commands across sessions again: press Up to recall them. Secret option values and secrets in URLs are never saved. * `unity shell` on a terminal completes commands, options and values with Tab again (press Tab twice to list the choices), and suspends with Ctrl-Z on macOS and Linux. * `unity install` refuses a module whose install or rename paths point outside the Editor's install folder, and an Editor version that is not a single folder name. A catalog can no longer make an install write or delete elsewhere. * Catalog, manifest and API responses over 64 MB are refused instead of being read into memory, and the Android license page is scanned in one pass. * `unity build`, `unity run`, `unity test`, `unity assets export`, `unity assets import`, `unity templates create` and `unity templates pack` no longer refuse a project as already open because of a leftover `Library/EditorInstance.json` whose process ID now belongs to another program, which happened in containers after an Editor was killed. When the refusal comes from that file, the message names it so you can delete it if no Editor is running. * `unity build` and `unity batch build` no longer run programs named by a project's git configuration (`core.fsmonitor`, hooks, the pager, file filters other than Git LFS, and an ssh command reached by fetching objects a partial clone lacks) when they read its revision and version. They never fetch, and they check each submodule with the same safe read, so a submodule at an unrecorded commit or with uncommitted edits still counts as a change. * With usage analytics turned on, creating a project from a downloaded or custom template no longer reports the template's file path. It reports the template's package name, or `custom` when the template has none. * On Linux, `unity vcs` conflict and diff staging, UVCS check-ins, and `unity publish` now keep their temporary files readable only by you, and refuse a folder or link another account planted in the shared temp directory. * `unity install --download-directory` and `unity install-modules --download-directory` on Windows now use an absolute path such as `C:\ws\editor` or `C:/ws/editor` as given, instead of joining it onto the current folder. * `unity build --create-profile` reads `UNITY_ARCHITECTURE` when `--architecture` isn't given, and refuses an architecture it doesn't know with the same usage error as the flag, instead of starting the Editor. * `unity --version` honors a `--format` or `--json` typed after it, as `unity version` does: `unity --version --format ndjson` now prints one result frame instead of the bare version line. * `unity docs --package --content` prints the package's local Markdown, the same as `unity docs --content`, instead of trying to open a browser. * On a machine licensed by a floating license server, `unity license status` and `unity doctor --ci` no longer report that no license is available before the Editor has leased a seat. When the server answers as healthy, both succeed and say the Editor leases a seat when it starts. * `unity license server status` reports a floating license server as reachable when the server answers as healthy but the licensing client cannot read its seat usage, which happens when nobody is signed in. * A successful `unity build` no longer lists the Editor's "Access token is unavailable" licensing line as an error. * `unity command --query` with a listing option such as `--limit` and no connected Editor now ends `--format ndjson` output with its result frame, which carries the search hints. It used to print nothing. * `unity mcp` now lists every Editor tool under a name of its own: the full command name with each space and dot written as `_`, such as `settings_player_get` and `script_eval`. On `com.unity.pipeline` 0.9, several groups shared one name (`get`, `set`, `add`), so clients dropped tools, a call could fail with "names several commands", and some clients rejected the whole server. * `unity close` now explains why it could not close an Editor when its output is redirected, for example that the project needs the `com.unity.pipeline` package or `--force`, instead of reporting only that the Editor was not closed. * A `cloud`, `collab`, `pipeline automation` or `pipeline cloud-build` command that fails because the server rejected your input (HTTP 400, 404, 409 or 422) no longer sends a crash report or points you at `unity bug`. The error message, the exit code and the json and ndjson output are unchanged. * A command that fails because you are signed out or your session expired no longer sends a crash report. The error message, the sign-in hint and the exit code are unchanged. * `unity projects` and `unity recompile` JSON and NDJSON output now escapes the C1 control characters (U+0080 to U+009F) like the other control characters, so a project path or compiler message cannot send an escape sequence to a terminal that honors them. Parsed values are unchanged. * `unity pipeline` no longer reports a Unity token exchange that returned an empty token, or got no answer, as being signed out. An empty token, or an answer it could not read, now offers the `unity bug` report like any other unexpected failure. * `unity plugins` no longer shows an out-of-date version for a plugin such as `ugs` when its saved copy of the plugin registry is more than a week old and this CLI already knows a newer version. The CLI's background refresh now also renews that saved copy once a week when no plugin is installed. * On Windows, `unity` now sends a crash report when it crashes, as it does on macOS and Linux. It was silent there before, so Windows crashes never reached us. * `unity projects info` shows the active platform for projects saved by Unity 6000.7 betas and newer Editors. Before, the platform was missing for those projects. * On Windows, `unity` stays signed in after a restart when the Hub you first signed in with was 3.21 or older. * `unity build` now shows why a player build failed, such as an output path that already exists as a folder, instead of listing only licensing log lines. * On Linux, `unity status`, `unity editors running` and `unity pipeline editors` list an Editor that Unity Hub 3.21 or older started through its per-version launch link. * `unity projects export --format ndjson` prints one JSON line with `"type":"result"`, so an ndjson reader can parse the export. * `unity install-modules` with no Editor installed now points you to `unity install ` instead of a command that does not exist. * `unity releases --limit` and `--offset` now refuse a value that is not a whole number, such as `1.5` or `5abc`, with a usage error instead of reading it as 1 or 5. * **Deprecated** * `--project` on `assets export`, `assets import` and `auth default`, `--path` on `build run`, and `--project-path` on `projects clone` still work, and print a warning naming the new spelling. * `--editor` and `-e` on `unity templates`, `-e` on `unity install-modules`, and `--unity-version` on the `pipeline cloud-build` filters still work, and print a warning naming `--editor-version`. In `--format json` the warning is in the envelope's `warnings`. * `--skip` on `releases` and `cloud projects` still works, and prints a warning naming `--offset`. In `--format json` the warning is in the envelope's `warnings`. ## 1.0.0-beta.14 **Release date:** October 21, 2026 * **Security** * The recent log in `unity doctor` now shows only the command you ran, such as `projects open`. Also, every argument you passed reads ``, so paths, project names and option values stay out of a report you paste. The log file itself doesn't change. * `unity bug --share-project` no longer follows symbolic links, so a link inside the project that points elsewhere can't put files outside the project into your report. Files the link would have reached and links to files inside the project are skipped. * On macOS and Windows, only a Unity-signed Editor started by `unity open` can get your access token from the CLI. * The programs the CLI starts for you no longer receive `UNITY_SERVICE_ACCOUNT_ID`, `UNITY_SERVICE_ACCOUNT_SECRET`, `UNITY_GITHUB_TOKEN`, or `UNITY_GITLAB_TOKEN`. The variables still reach `unity shell`'s commands, the command you run with `unity projects exec`, the Unity Editor, plug-ins, the licensing client and the identity server. * On Linux, the `unity` AppImage now copies the CLI into sealed, read-only memory when it starts and runs it from there, so the Unity auth broker can confirm it's talking to the genuine CLI. You run the AppImage as before. * On Linux, every release download of the `unity` CLI now carries a Unity signature: the standalone binary, the deb and rpm packages, the AppImage, and the npm package. It's made with the same key that signs the CLI on Windows, so the Unity auth broker can confirm it's talking to the genuine CLI. * On Linux, `unity doctor` now shows whether the running auth broker carries a valid Unity signature, in a new Signature row of the auth broker section and as `authBroker.runtime.signature` in `--json` output. * When the CLI exchanges a credential for a token, it no longer follows a redirect, even to the same host. That covers `unity auth login` with service account credentials or a browser sign-in, refreshing your sign-in, and getting a service account, Unity or Unity Version Control token. * When you run the CLI with `sudo`, it now makes you the owner of a folder it creates or repairs only when that folder sits inside a folder you already own. * On Windows, `unity self-update`, the MSIX update and `unity doctor` now run the Windows tools they need from the Windows system folder. * The CLI sends your sign-in and service-account credentials only to Unity servers. If the cached cloud configuration names any other server for them, the CLI uses the default Unity server and logs the ignored host. * `unity hub install` downloads the Hub installer only from Unity servers, and the service URLs the CLI hands to the Unity Editor are Unity servers too. A cached cloud configuration that names another server is ignored. Downloads stop after 10 redirects and no longer follow a redirect loop forever. * `unity plugin install plastic` and `unity plugin upgrade plastic` follow download redirects only to Plastic's own hosts over `https`. A redirect anywhere else fails the install. * Commands that look up Unity releases or templates, such as `unity install`, `unity releases`, `unity editors` and creating a project from a template, ask only Unity servers. A cached cloud configuration that names another server is ignored. * On macOS and Linux, the Editor identity server's socket can now be opened only by the current user, and it refuses a connection from a process running as another user. The CLI also sends its environment notice only to a socket owned and served by the current user. * `unity install`, `unity templates`, `unity upgrade` and `unity plugin install` refuse a download that redirects from an `https` address to a plain `http` one, instead of following it. `unity upgrade` stops at once instead of retrying. * `unity projects create` and `unity projects new` keep the Editor log, which can hold your access token, in a folder only you can open, and delete it when the run ends. After a failed run the log stays there, still private, so you can read it. * On Windows, the machine-wide `services-config.json` is used only when the file and every folder above it can be changed only by Administrators, SYSTEM or TrustedInstaller, as Unity Hub already requires. Otherwise the CLI uses the default licensing settings. * On Windows, `unity hub install` keeps the downloaded installer locked from its checks until it finishes its run. * `unity projects new` and `unity projects create` refuse a template archive that contains a symbolic link, a hard link, or a path outside the project. * `unity projects new` and `unity projects create` now only accept gzipped (`.tgz`) template archives. A plain `.tar` that used to work is refused as corrupt. * Template downloads ignore catalog entries whose name or version isn't a plain package name and version. * On Windows, `unity build run` no longer passes your service-account secret or source-host tokens to the player it starts, matching macOS and Linux. * The CLI no longer trusts certificates issued through the distrusted emSign intermediates, which its bundled root certificates and certificate checks could still accept. * On Windows, `unity hub install` and the commands that look for running Unity Editors now start Windows PowerShell from the Windows system folder. * Downloads no longer follow a redirect from HTTPS to plain HTTP, and `unity install` fetches a module over HTTPS even when the release catalog lists it with an `http://` address. * On Linux, removing an Editor that needs administrator rights and installing `git-lfs` through your system package manager now use `pkexec` only from a trusted system location. Otherwise the command fails with a message that it found no trusted `pkexec`. * Crash reports and displayed errors hide the value after `-accessToken`, `-password`, `-androidKeystorePass` and `-androidKeyaliasPass`, however short it is, as batch Editor output already did. * `unity bug` uploads and `unity batch` terminal output no longer show the serial number passed to the Editor with `-serial`. * On macOS, `unity uninstall` no longer lets the environment your shell started with reach the administrator shell that removes an Editor. * **Added** * `unity config path` prints where the CLI keeps its configuration: the settings file and the directory that holds it. It works in every output format; `--json` returns `{file, directory}`. * `unity terms accept ` 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. It shows the terms link and the copy installed with the Editor, then asks; pass `--yes` to accept without a prompt, which a run without a terminal requires. * The CLI now recognizes when GitHub Copilot runs it, from VS Code's agent terminal or the Copilot CLI. When the Editor is unreachable, the connection error mentions that an agent sandbox may be blocking local connections. * `unity releases --operating-system ` lists another operating system's releases, and `unity install --dry-run --operating-system ` shows what that system's Editor and modules would download, so you can plan a Windows build machine from a Mac. Without `--dry-run`, an install for another operating system stops with `CROSS_OS_INSTALL_UNSUPPORTED` and names the dry run instead. * 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. Nothing changes in the Hub. * `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". The message gives the same remedy as `status`. * `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. The message says what to do: quit, fix the errors and open the project again, or choose Enter Safe Mode in the Editor. * `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. * `unity open --accept-upgrades` (also `unity projects open`) opens a project and doesn't stop at the Editor's upgrade dialogs. As a result, an unattended open no longer hangs on "Project Upgrade Required" or the API Updater's script consent. It says yes to both: the project is upgraded to the Editor's version and Unity rewrites scripts that use obsolete APIs, with no backup prompt. * `unity install --download-directory ` (`-d`) installs a self-contained Editor into a folder you name, such as a CI workspace, and doesn't change the install path or add it to the Hub's Editor list. Modules from `-m` go into the same folder, and `unity install-modules --download-directory ` adds more later. * `unity projects create --bare` creates the project from the template without the default project scaffolding. The Unity Cloud link and `--vcs` work as usual beside it, and `--no-cloud` still turns the link off. * `unity projects create` reports each setup step it ran in a new `steps` field of its `--json` and `--ndjson` result: one entry per step, each `done`, `present` when the template already had it, `skipped` with a reason, or `failed` with an error code. * `unity open --until-ready` (and `unity projects open --until-ready`) waits until the Editor it launched is ready for commands, instead of returning right away. When a dialog stops the Editor, such as Project Upgrade Required, Script Updating Consent, Enter Safe Mode? or the Unity Editor Software Terms, it fails at once with `OPEN_BLOCKED_BY_DIALOG`, the dialog's title and what to do about it, rather than leaving a script waiting forever. * `unity mcp --tools ` exposes only the Editor tools whose names match the list, and `--exclude-tools ` hides the ones that match, so an agent's context holds only the tools you want it to use. Both take comma-separated names, and `*` matches any run of characters (`--tools "eval,capture_*"`). * The CLI tells you, at most once a day, when a plug-in you installed with `unity plugin install` has a newer version, and suggests `unity plugin upgrade`. Under `--format json` and `--format ndjson` it arrives as a `PLUGIN_UPDATE_AVAILABLE` entry in `notifications`, and over MCP in the server's instructions. * `unity command --obsolete-command-names` lists the command names from before command groups and the names that replaced them, from an Editor with a Pipeline package that serves them. * `unity --help` and the unknown-command error now end with "Not sure which command? `unity commands --grep `", so a command you can't name is one search away. * `unity setup antigravity` installs Unity's agent plug-in into Google Antigravity by running `agy plugin install https://github.com/Unity-Technologies/unity-agent-plugin`. Like `unity setup codex` and `unity setup grok`, it reports an existing install instead of reinstalling, takes `--dry-run` and every output format, and fails with `ANTIGRAVITY_NOT_FOUND` when `agy` isn't on your PATH. * `unity docs --package ` opens a package's manual for the version your project uses, read from `Packages/packages-lock.json`, for example `unity docs --package com.unity.2d.sprite`. Outside a project it opens the newest release's manual. * `unity docs toc` lists every page of the scripting API reference, or the manual with `--manual`, on docs.unity.com, so an agent can pick a real page rather than make a guess. Each page has its path and URL, in every output format. * `unity docs ` opens the local page from the Editor's Documentation module when it's installed for your project's Editor version (or the one `--editor-version` names), so it works offline. `--online` opens docs.unity.com instead, and `--url` always prints the docs.unity.com address. * `unity docs --content` prints the page's Markdown instead of opening a browser, and `--format json` wraps it with the page URL, the version and the source. Package topics read the package's local `Documentation~` Markdown, or say that no Markdown exists online yet. * `--no-header` leaves the header row out of `tsv` output, for scripts that only want the rows. * The `--json` and `--format ndjson` rows of `unity modules list`, `unity editors module list` and `unity install-modules --list` now include `downloadBytes` and `installedBytes` as integers and `isInstalled` as a boolean. Scripts should read these instead of `download`, `installed` and `status`, which are display text, and `status` is translated. * `unity projects link cloud --cloud-project --replace` switches a project that is already linked to another Unity Cloud project in one step: it writes the new link over the old one in the project's settings and the Hub's project list, with no `unity projects unlink cloud` first, and names the link it replaced (`previousLink` in JSON). Without `--cloud-project`, `--replace` takes `UNITY_CLOUD_PROJECT` or your saved default project, and fails with `REPLACE_NEEDS_CLOUD_PROJECT` when neither is set: it never creates a cloud project. * Every row of `unity commands --grep` and `unity command --query` now says what matched and how to run it: `--format json` adds `path` and `matchedOn` (`name`, `description` or `option`), and `--format tsv` adds them as its last two columns. An installed plug-in's row now shows `unity ` as its run line instead of nothing. * The `--json` and `--format ndjson` rows of `unity editors` now list an installed Editor's platforms (with `--verbose`, its modules) as the `moduleNames` array. * The `--json` and `--format ndjson` rows of `unity status` now name each Editor's project as `projectPath` and its version as `editorVersion`, and the rows of `unity editors running` name the version as `editorVersion`, the same names other commands use. * `unity command`, `unity list`, `unity job` and `unity mcp` take `--port `, `--pid ` and `--instance ` to pin one running Editor when several are open, including a Multiplayer Play Mode player by its instance name. A pin that matches no running Editor exits 12 and lists the Editors that are running. * `unity open --batchmode` starts the Editor in batch mode, with no window. Add `--until-ready` to return once it is ready for commands, with the same dialog, exit, and timeout errors as a windowed open. * `unity status` now reports an Editor in Safe Mode, which it used to leave out or show only as unreachable. The Editor's row lists its compile errors (file, line, and message) in every output format, and the command fails with `STATUS_SAFE_MODE` and exit code 6 (an Editor shown only as unreachable gave 12). * `unity logs --console` reads the running Editor's console, and `unity logs --console --follow` streams new entries as the Editor logs them until you press Ctrl-C. Burst and C# compiler errors come with their code, file, and line, `--level` and `--tail` work as they do for the CLI log, `--project-path` picks the Editor, and `--format ndjson` writes one entry per line. * `unity version --json` reports the commit a release was built from and its build date, as `commit` and `buildDate`, so a support report can be traced to the exact build. A build you compile yourself reports both as `null`. * `unity license activate` reads the license serial from the `UNITY_LICENSE_SERIAL` environment variable when you pass no `--serial` and no other activation option, so the serial stays out of the process list on shared machines. `--serial` still works and takes precedence. * When an AI coding agent runs `unity` and Unity's plug-in or skill isn't installed for it, the CLI now suggests one. In Claude Code, you get Claude Code's own one-time prompt to install the Unity plug-in. * **Changed** * `unity env` names its version row "CLI version", and its `--json` output adds `cliVersion`. `unity doctor --json` and `--format tsv` add `runtimeVersion`. * The CLI's MSIX package (the winget install) now needs Windows 10 version 21H1 or later, the same as the Unity Hub. * When their output is piped or redirected, or with `--format tsv`, `unity projects link cloud` and `unity projects unlink cloud` now print one tab-separated row: the result (`linked`, `already-linked`, `unlinked` or `not-linked`), the project path, the cloud project ID, the project name, the organization ID, and `true` when a new cloud project was created. For `unlink cloud`, the name is the one saved with the link, which is the local project's title when the CLI made the link. * `-a` now means `--architecture` on every command, and `-y` means `--yes` on every command that has `--yes`, including `unity bug mcp`, `unity mcp configure`, `unity skill install` and `unity skill refresh`. `unity projects list` and `unity projects size` show `--all` with no short flag; `-a` still works there, so existing scripts keep running. * When `unity releases` can't reach the Unity release service, the error names the host it tried and why, such as `ECONNREFUSED` or a failed secure connection, instead of "fetch failed". A connection, TLS or timeout failure also says how to set a proxy (`unity config proxy ` or `HTTPS_PROXY`), and `--json` reports the network error code in `errors[].code`. * `unity open` (also `unity projects open`) no longer passes `-acceptSoftwareTermsForThisRunOnly` to the Editor when you run it from a terminal, so the Editor shows its own Software Terms dialog to you. An unattended open (`--non-interactive`, `UNITY_NON_INTERACTIVE`, a machine `--format`, redirected output or CI) still passes it, and a copy you add with `--args` is kept. * `unity commands --grep` matches a regular expression with no time limit, so a pattern such as `(a+)+$` no longer stops with "took too long". Backreferences (`(a)\1`) and lookaround (`(?<=a)b`) are no longer supported and are refused as an invalid pattern, and an invalid pattern's error now ends with a short reason such as `unclosed group`. * `unity commands --grep` now matches plain words in any order and lists the best matches first, so `unity commands --grep 'cloud link'` finds `projects link cloud` at the top. A word in the command's own name ranks above one in its parent group, then its description, then its options. * When `unity commands --grep` or `unity command --query` can't search the Editor's Pipeline commands, because no Editor is connected, more than one is open, or it didn't answer within 3 seconds, the output ends with a line saying why and the command to run next. `unity command --query` without a connected Editor answers with that line and the number of CLI commands and plug-ins that match, and exits 0 instead of failing. * `unity projects` is now described as "Create, open, upgrade, and link local Unity projects (Unity Cloud, GitHub/GitLab)" in `unity --help`, instead of "Manage Unity projects in the Hub registry", so `unity commands --grep cloud` finds it. Use `unity projects link cloud` to link a project to Unity Cloud. * `unity projects create` adds the Pipeline package to every new project, so `unity command` works on it without a separate `unity pipeline install`. `--bare` leaves it out, and `--with-pipeline`, which used to opt in, is still accepted and does nothing. * `unity auth list` now marks accounts the CLI isn't signed in to, such as ones you signed in to only in Unity Hub, with `(not signed in to the CLI)`, and `--format json` adds `signedIn` and `signInState` to each account. When no account is active, `unity auth status` now says how many stored accounts aren't signed in to the CLI and suggests `unity auth login`, or `unity auth switch ` for one that is. * `unity auth switch` to a stored account the CLI isn't signed in to now says so and suggests `unity auth login`, and exits with code 3 and the error code `ACCOUNT_NOT_SIGNED_IN`. It used to fail with exit code 6 and an internal message about a missing token slot. * `unity auth login --help`, and `unity auth status` when you're not signed in, now say that a perpetual or legacy serial license needs no sign-in, and show the command: `unity license activate --serial `. A subscription serial still needs a signed-in user. * `-V` and `--version` print the CLI version only at the top level: `unity --version` and `unity -V` work as before. After a command they're no longer the CLI version, so `unity editors --version` now fails as an unknown option (exit 2, `INVALID_COMMAND_ARGS` under `--format json`), and a command's own `--version` means the version of what it acts on. * When the CLI hides an e-mail address in its log file or a crash report, it now keeps the domain (`[redacted]@example.com`) and removes only the part before the `@`, as the Unity Hub does. It used to replace the whole address with ``. * `unity cloud project current` now labels what it prints as the saved default project for the organization, and inside a project folder linked to a cloud project it also prints that linked project. With `--format json`, `activeCloudProjectId` still holds the default, and `defaultCloudProjectId` and `linkedCloudProjectId` are added beside it. * A template's `package/package.json` larger than 16 MiB is now refused, and the template no longer appears in `unity templates list --editor `. Real template files are a few KiB, so it only affects a damaged or hostile archive. * `unity cloud project set-default` now tells you when the project is in another of your organizations. Instead of reporting the project as unknown, the error names that organization and the `unity cloud org set-default` command that makes it active, and `--format json` carries the organization under `data.organization`. * `unity pipeline install`, `unity pipeline upgrade` and `unity projects create --with-pipeline` now save `Packages/manifest.json` in the encoding it already had, byte order mark included, and replace it in one step, so a run that stops halfway never leaves a broken manifest. They also only pin a plain version number from the Unity registry, and a manifest that repeats a top-level key is updated instead of failing. * `unity projects add` now checks a folder the way Unity Hub's Add project from disk does. It refuses a system folder, such as `/usr`, `C:\Windows` or `/Applications` itself, with `System folders can't be used as Unity projects`; a complete project inside `/Applications` or `C:\Program Files` is still added. * When the CLI can't read your signed-in account, a command now runs without the first-run analytics prompt and sends no analytics for that run, and `unity analytics opt-in` and `opt-out` exit with an error saying your choice wasn't saved, and change nothing. They also refuse when `user-settings.json` repeats a key or can't be read. * `unity skill install codex` now checks for the Unity plug-in that `unity setup codex` installs. When the plug-in is enabled and already carries the skill, the install says so and asks before writing a second copy, which Codex would load as well; without a terminal, or when you decline, it skips. * On Windows, `unity install-path --set` and `unity editors install-path --set` now answer a device path that names no drive, network share or volume, such as `\\.\pipe\name`, with `This directory does not exist.` without opening it. Drive paths, `\\?\C:\...` paths, `\\?\Volume{...}` paths and network shares are checked as before. * `unity projects create --vcs ` now refuses an IPv6 address or a host name with non-ASCII characters as an invalid provider. Use the server's ASCII host name, the one your provider CLI signs in to. * `unity projects create` and `unity projects new` now check a new project's name and location the way Unity Hub's New Project window does. A name can be at most 223 characters, which leaves room for the files Unity names after the project. * When a command isn't found, the tip now names `unity command` for the command groups, `unity command --tags` for the tags and, when the Editor's Pipeline package supports it, `unity command --obsolete-command-names` for the old names. * `unity command` with no command name now lists the Editor's command groups instead of its tags, and an Editor with an older Pipeline package still lists its tags. * `unity command ` lists the commands in that group like `--tag` does instead of printing a raw result, and command listings and results show each command as you type it (`editor.playmode start`). * `unity command editor status` and the other full command names, `unity editors playmode` and `unity recompile` still work with a Pipeline package from before command groups, and warn once to run `unity pipeline upgrade`. * `unity projects link cloud` without `--cloud-project` now links the project named by `UNITY_CLOUD_PROJECT`, then your saved default project for the organization (`unity cloud project set-default`), and creates a Unity Cloud project only when neither is set. On a terminal it asks first, with that project preselected, and it always says when it created one (`created` in `--format json`). * A plug-in killed by a signal, run as `unity ` or as a `unity-` command on your PATH, now exits with `128` plus the signal number (`139` for a segmentation fault), the way a shell reports it, instead of `1`. The CLI log now names the plug-in, its version when known, and the signal, so `unity bug` includes them. * `unity cache key` with more than one path now lists every argument you passed in its error. `unity config accelerator` now refuses an IPv6 address with an interface name, such as `[fe80::1%eth0]`, whose number depends on the machine; use the numbered zone instead, such as `[fe80::1%3]`. * `unity templates` and `unity projects create` now say plainly when the Unity Hub templates folder can't be created, or when its list of downloaded templates can’t be reset or repeats a key, instead of printing a raw system error. For example, a folder they can’t create now shows `Could not create the templates folder (PermissionDenied).` `unity templates delete` reports a custom templates folder it can't create or read the same way. * `unity projects create --template ` now refuses a template whose `package.json` repeats a key as not a valid Unity template, and `unity projects create` and `unity projects new` report the Editor version as unresolved, with how to choose one, when the newest installed Editor can't be told apart, instead of printing an internal error. `unity projects new`, `create`, `link vcs` and `unlink vcs` run from a folder that no longer exists now say `Unable to read the current directory.` unless you pass an absolute path. * `unity command` without `--timeout` now lets each Editor command use its own default timeout (for example 10 minutes for `run_tests`) instead of a flat 30 seconds, on a `com.unity.pipeline` that supports it. `--timeout ` still overrides it, and when it runs out the Editor's own timeout message is shown. * A command the Editor rejects because a modal dialog is open now fails at once instead of retrying until `--timeout` runs out. Its error, and the timeout error of a command or job that was already running when the dialog appeared, now name the dialog and the `unity command editor.dialog answer