Unity opens its engine to Google Antigravity agents

Google has launched a plugin marketplace for Antigravity — a centralized catalog of third-party and first-party extensions for the Antigravity app and its console version. Among the launch partners is the official Unity plugin: it connects the engine to the agent in one click, after which building, simulation and realtime-3D pipeline management can be handled without leaving Antigravity.

Previously, linking an agent to an external system meant manual setup: MCP endpoints, environment variables, domain skills and custom subagents were written into separate repositories or local configs. The plugin packs up to five extensibility primitives into a single versioned bundle with a plugin.json

manifest: skills (SKILL.md), MCP servers (mcp.json), rules, lifecycle hooks (hooks.json) and custom agents — they are installed, updated and enabled as one unit. All that is left for the developer is to find Unity in the Customizations → Plugins panel or run agy plugin install.

What the agent gets

The Unity plugin is version 0.1.8-beta, under the Unity Companion License, and works with Unity 6 and newer; it is published in the Unity Technologies repository, and the agy plugin list

command helps verify the installation. Many skills drive the open editor through Unity CLI, Unity's command-line utility: the agent checks whether it is installed, installs it if needed, and adds a small Unity package through which the CLI talks to the running editor. Unity Hub users usually already have the utility — the Hub installs it automatically.

From there the agent can create GameObjects, change asset import settings, execute C# code directly in the running editor and verify the result — instead of editing scene and asset files by hand. The CLI itself also installs editors, creates and opens projects, and launches builds and tests.

Skills are pulled in automatically to match the task, but they can also be invoked manually from the slash menu. Among them are in-app purchases, rewarded videos, settings screens, pixel-art rendering, hexagonal tile palettes, troubleshooting of character display issues in TextMeshPro, and reviewing a ScriptableRendererFeature for Render Graph errors.

There is also a risk Unity warns about outright: skills edit scripts, scenes and assets directly, and not every change is logged or undoable through the editor. The recommendation is simple — keep the project under version control and commit before major edits.

Antigravity is not the only environment

The same Unity plugin is available for Claude Code, Codex and Grok — in each environment it installs with its own commands, and in Claude Code, Grok and Antigravity the skills additionally show up in the slash menu. Unity asks that bugs and suggestions be sent to its Unity Discussions forum.

Why this is happening

Unity's moves add up to a bet on a neutral interface to the editor: the console layer is exposed outward, and a thin wrapper is released for every popular agent environment. The more such environments are supported, the fewer reasons a studio has to pick an engine based on which assistant it works with. Unity's appearance in Google's catalog looks like a continuation of that line rather than a standalone deal.

From Google's side the logic mirrors it: a storefront with ready-made partner plugins removes one of the main barriers of agent environments — the need to assemble integrations for every tool a team uses by hand. Gamedev is a convenient case for such a catalog: the pipeline here is long, reproducible and poorly suited to manual routine.

If the trend continues, the line between the development environment and the agent orchestrator for game teams will blur, and the value of a particular engine will depend more and more on how carefully it exposes its operations outward — building, tests, asset import, running scenes. For modelers and programmers this means part of the work shifting from manual actions in the editor toward setting tasks and reviewing the changes the agent has made in the repository.

Ready to hand build creation over to an agent in Antigravity, or will you stick with your own script? Tell us what the plugin lacks to earn your trust.