Unity now ships official Codex and Claude Code plugins, but none of the skills are XR

Unity published an official plugin for OpenAI's Codex on September 16, carrying 31 engine skills written by Unity engineers, a week after doing the same for Claude Code with 29. The engine behind most of the VR games you own has started teaching coding agents its own APIs directly.

Unity's plugin listed among the partner plugins in Claude Code's directory, in Unity's own illustration. Image: Unity

Unity's argument for why this was needed is unusually candid about how these tools behave. General-purpose agents lean on forum posts and tutorials written for engine versions that no longer ship, and as Unity puts it, "the answer that surfaces is the one that gets repeated most often, rather than the one that is still true today". Code that compiles but does the wrong thing is the result.

The skills cover the engine, not the platform

Both plugins span the same nine areas: getting started and tooling, UI and text, 2D and sprites, graphics and rendering, audio, scene and gameplay, monetisation and live ops, multiplayer, and platform and localisation. One skill sets up a fresh project with the Editor, source control and packages configured, and another plans and executes a move from the Built-in Render Pipeline to the Universal Render Pipeline.

The Claude Code set covers the same ground, with URP, UI Toolkit, multiplayer, LevelPlay and Unity IAP among the 29. Unity lists the Codex plugin as compatible with Unity 6 and newer, and skills on both sides are written against Unity 6.0 or later.

The Claude Code plugin can drive the Editor

This is the part that goes beyond documentation. Unity bundles its CLI and its MCP server with the plugin, which Unity says gives the agent live Editor control: creating and modifying GameObjects, editing scenes and assets, inspecting the hierarchy and running C# directly in the project.

Installation is deliberately short. The Codex plugin goes in with one click from the OpenAI plugin directory or two terminal commands, and the Claude Code plugin installs from the terminal or from the Claude Desktop app. Neither needs per-project setup, and Unity says it will offer the plugin on other coding agents later this year.

Both follow the Unity CLI, which the company launched at Unite Seoul so developers could point an existing agent at the engine. The plugins are the next step: Unity supplying the knowledge rather than hoping the agent finds it.

There is still no XR skill

For this audience, that is the gap. Neither the 31 nor the 29 includes an XR, VR or OpenXR skill. A developer building for Quest, Steam Frame or Vision Pro gets an agent that knows Unity's rendering, UI, audio and multiplayer systems properly, and knows nothing more about XR rigs, interaction toolkits or store submission than it did last month.

Unity's case for the plugins rests on developer frustration it did not measure itself. It cites Stack Overflow's 2025 Developer Survey, in which 66% named "AI solutions that are almost right, but not quite" as their top frustration and 45% said debugging AI-generated code is more time-consuming. Unity's own claims, that a skill produces fewer errors, uses tokens more efficiently and finishes in fewer turns, come with no published benchmark.

The pairing is worth noticing on its own. Unity shipped for Anthropic's agent first and OpenAI's second, in the same fortnight OpenAI was retiring custom GPTs into the same plugin system and Anthropic was folding Cowork into the Claude app. Engine vendors are now shipping for both.

Unity says more skills are coming to both plugins. Whether any of them are XR skills is the question for anyone whose game only runs on a headset.