At Unite Seoul we showed what we’ve been building: a new API and set of services (plus the Unity CLI) that open a Unity production to your whole team and their agents, without everyone needing to work in the Editor. Producers review real builds in the browser, artists push assets from their own tools, engineers automate from the terminal, and agents validate content and trigger builds through the same API our own apps are built on. Only one person touches the Editor; everyone else works the same project from the tools they already use.
It’s in closed beta now: If your team wants in, apply here. We’re admitting teams on a rolling basis between now and general availability in November.
What this thread is for: This is the public space to talk about it: ask questions, tell us what you’d want it to do, and follow along as features ship. Teams in the closed beta have a separate channel for hands-on support, so this thread is for the wider community, not day-to-day beta troubleshooting.
How we’ll keep you posted: We’ll update this thread as new capabilities land, alongside the public roadmap. Expect bigger feature drops around each Unite moment:
You can try the developer tools today The Unity CLI is available now for installing editors, automating CI, and driving the Editor from the terminal, and it works with the agent you already use.
Explore Further
- Keynote Video
- What we’re building and why
- Roadmap
- Unity Production Pipeline Documentation
- Apply for the closed beta
This is early and it’ll change between now and GA. That’s the point of doing it in the open. Tell us what’s working, what’s missing, and what would make it genuinely useful for your team.