In Brief:
- Unity unveiled its Unity 7 roadmap at Unite Seoul, adding a public API and a command-line interface that let artists, producers and developers validate assets, push builds and collaborate without full Editor access.
- A free-to-use MCP will connect coding agents such as Claude Code and Cursor directly to Unity, and the Unity CLI is available now.
- Early beta begins in December 2026, with a full release planned for the first quarter of 2027.
Unity is opening its Editor to people who never open it. At its Unite Seoul conference on July 21, the company laid out a Unity 7 roadmap built around a public API and command-line interface that let artists, producers and developers validate assets, push builds and work from their own tools without full Editor access. A free-to-use MCP will connect coding agents directly to Unity.
Unity said the pitch on X directly. “We’re opening the Editor to EVERYONE,” the company posted, adding that “a game isn't built in the Editor alone.”
We’re opening the Editor to EVERYONE
For 20 years, the Unity Editor is where a whole generation of games has taken shape. But a game isn’t built in the Editor alone.
That’s why we’re building an API and set of services that open a Unity production to the tools, roles, and@UnityView on X ↗
What the API opens up
For 20 years the Editor has been the single place work happened. The new API and services move parts of that work outside it.
Adam Smith, senior vice president of product at Unity, said a coding agent could “plug in and validate a build,” or a producer could review a scene in a browser without opening the Editor. The MCP connects large language model agents such as Claude Code and Cursor to a running project, with access to the scene hierarchy, GameObjects, component values, console output and build settings.
The CLI ships now
The Unity CLI is already out, ahead of the full release. It installs and manages editors from one binary, drives a running Editor from a script and executes live C# inside a project.
An experimental package, com.unity.pipeline, lets the CLI drive a running Editor or a dev Player build over a local API. Developers expose their own commands with a [CliCommand] attribute. The unity command eval call runs C# live inside a running Editor or Player and returns the result, with no project-level recompile or domain reload.
Because eval reaches whatever API a project can call, an agent’s reach is the same as Unity’s: rendering, physics, animation, the asset database, the Editor itself, plus whatever the team’s own code adds.
Speed and a no-break upgrade
Unity 7 runs on a modernized core using CoreCLR. It promises near-instant Play Mode, domain reloads that touch only the code that changed and shader builds up to 90% faster.
The company said the move off Unity 6 won’t require a traditional upgrade. There’s no rebuilding and no new language, and Unity said “all projects, skills, and code will carry forward smoothly into the next generation.” Smith said foundational pieces such as CoreCLR and Surface Cache GI are being shipped and production-verified inside versions of Unity 6 before they land in Unity 7.
Timing
Early beta testing begins in December 2026. The full release is scheduled for the first quarter of 2027.
Unity framed the platform for teams where people and coding agents work side by side, but said the AI tooling is optional. “If your studio has committed to keeping AI out of your creative work—you’re not on the sidelines of this release,” Smith said. “Unity 7 is built for a future where humans and coding agents can work together. But the choice is always the team’s, not the platform’s.”
“Game development is changing faster than at any point in history,” said Matt Bromberg, president and CEO of Unity. “The future belongs not to the biggest team, but to those who can use new technology to create something unique and find an audience. Unity 7 is the platform that meets this moment.”
