The official Unity plugin for Codex is now live. It’s a first-party integration, written and maintained by us, so when Codex answers a Unity question the answer comes from, well, Unity.
Setup is two commands from your terminal, or one click from the Codex directory. No per-project configuration, and nothing to copy around when you move to a new machine.
What a single install gets you:
31 skills written by the Unity teams that own each feature, covering UI Toolkit and uGUI, 2D and tilemaps, URP and Shader Graph, audio, navigation and physics, IAP and LevelPlay, multiplayer, web, and localization
The unity-cli skill, so Codex can install Editors, create and open projects, and manage packages straight from the terminal
It’s built for Unity 6 and up, so that’s the version you’ll need.
This is a skills package. Each skill is instructions for how a specific job is meant to be done in Unity, so Codex works from what our engineers wrote rather than averaging out a decade of forum posts written against versions that no longer ship. It isn’t an MCP server, so it doesn’t hook into your running Editor.
Check out the documentation to get started, and the blog has the full skill list.
Agent tooling isn’t going to be everyone’s thing around here, and that’s fair. No pressure either way. But if you do give it a go, tell us what worked, what didn’t, and which skill you want next.
So it is not an MCP but it does immediately want to hook into unity. Just try now after installation and that is what it wants to do with the sample request. It seems the skills are all about going into your project and modifying it.
What about just helping with asking unity related questions?
Or for pure coding, ensuring the AI is on track with latest APIs as that is where it often falls down?
Unity has an MCP but also has a CLI, this plugin is just for the Unity skills inside the Editor as far as I know, I currently have Claude with CLI and Skills and everytime I asked for something it just gave me the info about my current Unity version.
This is a really interesting direction, especially because the skills are maintained by the Unity teams responsible for those features. Having version-aware guidance should make a meaningful difference compared with relying on generic AI knowledge that may mix older Unity workflows with current ones.
The unity-cli skill also seems particularly useful for reducing the setup friction around creating projects and managing packages.
One thing I’d be interested to see over time is how the skills handle edge cases in larger, existing projects rather than mostly greenfield workflows. That’s where context and project-specific constraints can make AI-assisted development much more challenging.
I hope the skills are updated, uitoolkit stuff like painter and it mention css gradients aren’t supporting so do it via that instead, which is outdated with 6.7 now supporting css gradients etc
perhaps updated inline with the feature changes as and when they come out so maintained that way, but whatever.
Just kidding.