Rachel Zhao - Unity
Developers start in the agent they already use, in the editor they already like, with the terminal they already have open. The Unity CLI meets you there. It’s a single binary that installs and manages Unity from the terminal and, with the Pipeline package, drives a running Editor, so scripts, CI, and coding agents all reach Unity the same way.
Since July, more than 226,000 logged-in users have used the Unity CLI, and it has logged more than 200 million events (and growing). Almost all of them are commands being run. What those commands show is a simple habit: people set Unity up, then their agent does the work.
People set it up, then hand it off #
From July 20 to October 13, 2026, about 98% of CLI runs come from coding agents and other automation. People typing at a terminal account for 0.2%, and CI pipelines for 0.3%. A small share of runs falls outside those three groups. When people do type, they are getting ready. They install the Pipeline package, open a project on the right Editor version, sign in, point their agent at Unity, and install the CLI skill. Then they hand the work over. That is what meeting developers where they work looks like in practice: Unity shows up inside the agent they already chose, and the agent takes it from there
Most of the work happens inside a live Editor #
The three commands run most:
unity commandabout124 million runs : runs a command on a connected Editor, either a built-in one or one you defined yourself.unity statusabout6.7 million : shows the live state of every connected Editor, including its project and version.unity pipeline listabout1.4 million : lists Editor instances and whether each one has the Pipeline package.
unity command alone is more than eight in ten of all events. The CLI is mostly being used to act inside a live Editor, with a check on its state now and then. Developers have started more than 1.3 million MCP sessions, the mode agents use to connect to Unity through the CLI, and opened projects more than 150,000 times.
Unity’s plugins bring official skills to agents #
Most of the CLI's usage came after Unity released official plugins for Claude Code and ** Codex**, and most recently, ** Grok**. Each plugin gives the agent skills written by Unity's own teams, including one that drives the CLI, so the agent works in Unity the way Unity intends. unity setup claude installs the Claude Code plugin for you, and the plugin also works in the Claude Code extension for VS Code. Agents without an official plugin, such as Cursor and Cline, can still work in Unity through the CLI, so you keep the agent you already use.
Claude Code is the agent used most with the CLI, followed by Codex, then other agents such as Cursor and Grok. The rest come from scripts and tools that do not identify an agent.
Where it is being used #
By signed-in users, the CLI's largest audiences are in the United States, Japan, and South Korea, followed by Germany.
What's next #
We will keep adding agents, and keep publishing what we learn. To get started, see the Unity CLI documentation and the Unity plugin documentation.
How we measured this #
All CLI figures come from Unity CLI's aggregated telemetry, July 20 to October 13, 2026, with Unity employees excluded. Developers who opt out are not counted. Each event is counted once, so retries do not inflate the totals. Country is based on the location attached to each event, and some events carry no location. The split between agents, CI, and people covers July 20 to October 13, 2026.. A run counts as CI when a x`CI environment variable is set, and as a person when both input and output are a terminal. Runs in MCP mode, runs from a known AI tool, and other piped or scripted runs count as agents and automation.