Ziva for Unity

The Unity AI agent that works inside the editor

Ziva is an AI agent for Godot and other engines, and docks in the Unity Editor through Ziva Enterprise. It sees your scenes and prefabs the way you do, edits them from inside the editor, writes C#, runs your PlayMode tests, and reads the Console when something breaks.

Talk to our team

Built for Unity studios

  • Full Unity editor integration
  • AI Development Agent
  • Play mode checks with screenshots
  • Security review for your studio
  • Runs in the Unity Editor on your workstation

In the editor

An agent that can actually use Unity

An assistant that only reads your scripts is guessing at everything else - the scene, the prefabs, the values you set in the Inspector. Ziva works inside the Unity Editor, so it sees what you see, and it makes changes the same way you would: through the editor itself.

Reads your scene hierarchy

Walks the open scene, finds GameObjects by name, tag or component, and reads serialized field values off any component - instead of parsing YAML and hoping.

Edits GameObjects and prefabs

Creates, reparents and configures GameObjects, adds components, sets fields, and edits prefab assets through Unity's prefab API instead of patching the YAML.

Writes C# with project context

Generates and refactors MonoBehaviours and ScriptableObjects that know your assemblies, your existing systems and your Unity version - then waits out the domain reload and checks the compile.

Runs your tests

Drives the Unity Test Framework and reports EditMode and PlayMode results back into the chat. The agent can run the suite to check a fix before it reports back.

Reads the Console

Reads compile errors, exceptions and warnings from the Console when it checks its work. No copying a stack trace into a browser tab.

Sees the Game view

Screenshots the Game and Scene views, so a layout or shader change is judged on what it looks like rather than on what the code says it should look like.

Drives Play mode and menus

Enters and exits Play mode and invokes menu items - including the ones your own editor tooling registers, so in-house pipelines are reachable from chat.

Generates sprites and textures

Sprites and textures generated into the project and imported, plus materials, so the agent can fill a scene instead of leaving pink placeholders.

How it runs

Docked in Unity, running on your machine

Ziva ships as a Unity package. The agent panel opens as an editor window, and the process that does the work runs on the developer's workstation - not on a build server you have to trust.

01

Install the package

A Unity package your team adds like any other. Everything it needs ships inside the package, so nobody has to install extra software or set a machine up first.

02

It reads the project like the editor does

Scene hierarchy, components, assets, the Console. The agent starts from what Unity knows about the project, not from a text search over the repository.

03

It changes the project through the editor

Every edit is made the way a developer would make it, so prefab overrides and asset references don't break - and what lands in source control is a change your team can review like any other.

04

It verifies before it reports

Tests run, the Console gets read, the Game view gets screenshotted. When the agent says a thing works, that is a measurement rather than a claim about code it just wrote.

Studio pipeline

Fits the pipeline you already have

A forty-person Unity team does not have a green-field repository. The parts of Ziva that matter at that size are the ones that meet your in-house tooling and conventions where they already are.

Local history and undo

Every agent turn is checkpointed in a project-scoped history separate from your VCS, so an experiment can be rewound without touching your version control history.

Your in-house tools, as agent tools

Any MCP server becomes something the agent can call - your asset database, your build dashboard, your issue tracker, the internal CLI that only your studio has.

Your conventions, not generic Unity

The agent is briefed on your architecture docs, naming rules and review standards, so what it writes looks like the rest of your codebase.

Versus a general AI coding assistant

Copilot cannot open your scene

Copilot, Cursor and a browser tab are strong at C# in a file. None of them can see the prefab that field is serialized on, notice the missing reference, or press Play. That is the gap that produces code which compiles and a game that doesn't run.

CapabilityCopilot · Cursor · ChatGPTZiva for Unity
Writes C# from your codebase
strongest at this
plus editor context
Reads the scene hierarchy and components
sees YAML, if anything
through the editor API
Edits prefabs without corrupting overrides
text-patches the asset
Unity's prefab API
Reads the Unity Console
you paste the trace
when it checks its work
Runs EditMode and PlayMode tests
command line only
Unity Test Framework
Runs the game to verify a fix
reads code and guesses
Play mode, screenshot, Console

Ziva for Unity is available to studios through Ziva Enterprise. Contact our team for pricing and rollout.

Security and infrastructure

Where it runs and what it sends

Publisher NDAs, console dev kits and unreleased IP decide where your source is allowed to go. Here is where the agent runs and what it sends, so you can decide.

Where the agent runs

The agent runs in the Unity Editor on each developer's machine and needs the Ziva service at ziva.sh. Tell us your network rules before rollout and we will tell you what works.

Model and data choices

Review your preferred model provider, data handling terms, and whether local inference meets your requirements. Policies depend on the selected provider and services.

Security review

Share your security questionnaire and required controls. We answer them before your team signs.

Team rollout

Seats, usage, support, and commercial terms for your team are set in one enterprise agreement.

Unity AI agent FAQ

Is there an AI for Unity?
Yes. Ziva is an AI agent for Unity that docks inside the Unity Editor rather than sitting in a browser tab. It reads your scene hierarchy, GameObjects and components, edits prefabs and materials from inside the editor, writes C#, runs EditMode and PlayMode tests, and reads the Console. Ziva for Unity is available to studios through Ziva Enterprise.
What can a Unity AI agent do in the editor?
Ziva works through the Unity Editor, not only the files on disk. It reads the scene hierarchy and the components on each GameObject, creates and edits GameObjects and prefabs, writes C# and checks that it compiles, runs EditMode and PlayMode tests, and reads the Console. It can enter Play mode and capture the Game and Scene views to check its work. Each turn is checkpointed so you can undo it.
Can AI write C# for a Unity project?
Yes, and the useful part is the context. Ziva generates and refactors MonoBehaviours and ScriptableObjects with your assemblies, your existing systems and your Unity version in scope, then waits out the domain reload and checks that it actually compiled. A generic assistant writes plausible C# and stops there.
Can AI test a Unity game automatically?
Yes, at two levels. Ziva drives the Unity Test Framework so EditMode and PlayMode suites run from chat, and it can run the game in Play mode for up to 30 seconds, then check a Game view screenshot and the Console output. Unit tests tell you a function is correct; a Play mode run shows whether the game actually runs.
How is Ziva different from Unity's built-in AI?
Unity's own AI features are assistants inside Unity's product and Unity's model choices. Ziva is an agent that takes actions: it edits the scene, runs the tests, reads the Console and iterates until the task is done. It also lets you pick the model per task, such as Claude, GPT-5, Gemini or DeepSeek, or a local model through Ollama or LM Studio.
Does our Unity project get uploaded anywhere?
With a cloud model, the code and conversation context used for your task are sent to the selected model provider. Ziva never uses your code to train AI models. For local inference or specific network requirements, we’ll confirm the options for your studio. Read the privacy policy for provider and service data handling.
Which Unity versions does Ziva support?
The Unity package supports Unity 6 and later. If your production is locked to an older LTS line, tell us the version and we will confirm support for it.
How do we get Ziva for Unity?
Through Ziva Enterprise. Tell us your Unity version, team size and network rules, and we will come back with a plan for your studio.

Need it built for you?

Kena Labs builds custom simulations and digital twins, including plants rebuilt from their drawings, medical and safety trainers, and conveyor lines tested in NVIDIA Isaac Sim. If you need a full simulation or digital twin built for your project, talk to Kena Labs.

Kena Labs is a sister company of Ziva.

Talk to Kena Labs

Bring Ziva to your Unity studio

Tell us your Unity version, team size and network rules. We come back with a plan built around it.

Talk to us about Unity