Unity CLI

Always use the latest version of the Unity CLI unless you are told to use a specific version. Newer releases regularly add commands and output fields these docs describe, so an outdated CLI fails in ways that read like the docs being wrong. Check with unity self-update --check --format json.

Find a command: search, don't grep help

Never filter unity --help or a group's help with grep. Help is long, and a grep over it drops the match or the context around it. Use the CLI's own search:

unity commands --grep license                 # built-in commands, plugins and the connected Editor's Pipeline commands
unity command --query screenshot              # the same search

unity commands --grep <pattern> and unity command --query <term> are one search. It covers the CLI's built-in commands, the plugin catalog (installed or not) and the Pipeline commands of the live connected Editor, best match first. Plain words each match in any order; regex characters make it a regular expression. Each row says how to run it (invoke): unity projects link cloud, unity command create_gameobject, unity <id> for an installed plugin, or unity plugin install <id> for one not yet installed. In --format json each row also carries kind (command, plugin, pipeline), path, description and matchedOn (name, description or option), so act on invoke rather than parsing the table.