Ziva for Isaac Sim

AI for Isaac Sim that works inside the simulator

Ziva is an AI agent for Godot and other engines, and works inside NVIDIA Isaac Sim 6.x as an enterprise pilot. It reads and edits the OpenUSD stage, imports URDF and MJCF robots, writes Python against the Isaac Sim API it finds running, and steps the simulation to check what it built.

Talk to our team
  • AI Development Agent
  • Reads and edits the USD stage
  • Security review for your team
  • Runs inside Isaac Sim on your workstation

In the simulator

An agent that speaks OpenUSD, not just Python

Almost nothing about an Isaac Sim project is in the Python file. The robot is an articulation on a USD stage, the sensor rig is a prim graph, and the thing that is wrong is usually a joint drive gain. An assistant that can only read text is guessing at all of it.

Reads the USD stage

Traverses the composed stage, resolves prims by path, type or API schema, and reads attribute values and transforms off them - instead of parsing a .usda layer and hoping composition resolved the way it looks.

Edits prims and references

Creates, moves, duplicates and deletes prims, sets existing attributes and adds references through Kit commands, so each edit shows up in Edit > Undo.

Writes Python against the running API

The Isaac Sim API was renamed wholesale between releases, and models trained on the old namespace confidently write code that no longer imports. The agent looks up the Isaac Sim API that is actually running and runs the script to check it. Ziva supports Isaac Sim 6.x.

Imports and tunes robots

Imports URDF and MJCF robots with the Isaac Sim importer, reads joints and drives, and sets drive targets, stiffness and damping. Other physics settings are changed through prim attributes or Python.

Reads the Kit log

Reads the warnings and errors Kit logged since Ziva loaded, including Python tracebacks, PhysX warnings and USD composition errors, so a broken stage is something it triages instead of something you paste.

Steps the sim and looks

Plays, pauses and steps physics, reads back world transforms, and captures the viewport, optionally through a camera prim, so a spawned robot that fell through the floor is caught by the agent rather than by you an hour later.

Lays out scenes from library assets

Finds props in the Isaac Sim asset library or on your Nucleus server and references them into the stage, as in the parcel-line demo above.

How rollout works

Set up for your stack, not thrown over a wall

Ziva for Isaac Sim is available to enterprise teams as a pilot. It runs on Isaac Sim 6.x on Windows and Linux and has been verified on Isaac Sim 6.1 on Windows. We set it up with your team instead of handing over a download.

01

We map your stack

Your Isaac Sim version, the robots you simulate, and what your customer contracts allow to leave the building. That decides the shape of everything after it.

02

We install Ziva for Isaac Sim

We install the Ziva extension for you. The chat docks inside Isaac Sim on Windows and opens in your browser on Linux.

03

We wire in your tooling

The agent browses your Nucleus or S3 asset root. Other tools, such as an experiment tracker, connect if they have an MCP server.

04

We check your network rules

The agent runs on each developer's machine. It signs in to Ziva and uses a hosted model or a local model through Ollama or LM Studio. Tell us your network rules and we will tell you what works.

Robotics pipeline

Fits the pipeline you already have

A robotics program has a Nucleus server, shared assets and a team's own conventions. These are the parts of it Ziva works with today.

Nucleus and your asset library

The agent works against the assets your team already publishes rather than pulling a fresh copy of the sample library into every scene.

Your in-house tools, as agent tools

Any MCP server becomes something the agent can call - your experiment tracker, your dataset store, your fleet telemetry, the internal CLI only your team has.

Checkpoints and undo

Every agent turn is checkpointed in a project-scoped history separate from your VCS, so an experiment can be rewound without a revert that touches the team. Only saved, file-backed layers are checkpointed.

Your conventions, not generic Isaac

Briefed on your extension layout, naming rules and review standards, so the code it writes reads like the rest of your repository instead of like the sample scripts.

Versus a general AI coding assistant

Copilot reads your files, not your stage

Copilot, Cursor and ChatGPT are strong at Python in a file, and NVIDIA's Isaac Sim MCP server and agent skills give them knowledge of the current Isaac Sim API. On their own they do not resolve a prim on the composed stage, see that the articulation root is on the wrong link, read the Kit log, or step the simulation. In a project where most of the state is USD, that is most of the project.

CapabilityCopilot · Cursor · ChatGPTZiva for Isaac Sim
Writes Python from your codebase
strongest at this
plus stage context
Targets the Isaac Sim API you pinned
With NVIDIA's MCP server or skills
needed for the 6.x API
looks up the running API, then runs it
Reads prims and attributes on the stage
sees a USD layer, if anything
through the USD API
Tunes articulations and joint drives
no physics to observe
steps PhysX and measures
Reads the Kit log and PhysX warnings
you paste the traceback
since Ziva loaded
Runs the scene to verify a fix
cannot step physics or see the viewport
steps physics, viewport capture

Ziva for Isaac Sim is available to enterprise teams as a pilot. Contact our team for setup.

Security and infrastructure

Where it runs and what it sends

Customer site data, robot designs under NDA and the policies you are about to ship decide where your source and your datasets are 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 Isaac Sim 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.

AI for Isaac Sim, answered

Is there an AI agent for Isaac Sim?
Yes, several. NVIDIA offers a free Isaac Sim MCP server and agent skills for Isaac Sim 6.0 and later, which give coding agents such as Claude Code, Cursor and Codex knowledge of Isaac Sim. Community MCP servers exist too. Ziva is an agent that runs inside the simulator: it edits the open USD stage, steps physics and captures the viewport to check its work. Ziva for Isaac Sim is available to enterprise teams as a pilot. Read NVIDIA's Isaac Sim MCP docs.
Is Isaac Sim free?
NVIDIA says Isaac Sim is free to use for internal R&D and development, including commercial R&D. You need an NVIDIA AI Enterprise license only to redistribute Isaac Sim to third parties or deliver it to them as a service. Ziva for Isaac Sim is a separate enterprise product. Contact us for a pilot. Read NVIDIA's Isaac Sim license FAQ.
Why does a general AI assistant struggle with Isaac Sim?
Two reasons. First, most of an Isaac Sim project is the OpenUSD stage rather than the Python file, and a file-based assistant cannot resolve a prim, read an attribute or see that the articulation root is on the wrong link. Second, the Isaac Sim API was renamed wholesale between releases, so a model without NVIDIA's Isaac Sim MCP server or agent skills tends to write the namespace it saw most in training, which does not import on the version you are pinned to.
Does Ziva work with Isaac Lab or ROS 2?
Not yet. Ziva has no Isaac Lab or ROS 2 tools. In Isaac Sim it can write Python, run it in the simulator and step the scene to check that it runs.
Can the agent generate synthetic training data?
Not with dedicated tools yet. Ziva has no Replicator tools. The agent can write Replicator code and run it in the open Isaac Sim, but it does not run jobs on a cluster.
Does our simulation code and robot data leave our network?
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 team. Read the privacy policy for provider and service data handling.
Which Isaac Sim versions are supported?
Ziva supports Isaac Sim 6.x. NVIDIA's current release is Isaac Sim 6.2.0, from October 2026, and there is no Isaac Sim 7.0. We have verified Ziva on Isaac Sim 6.1 on Windows. It also runs on Linux, where the chat opens in your browser. Tell us your version and we will tell you whether it works.
How do we get Ziva for Isaac Sim?
Contact Ziva Enterprise. Tell us your Isaac Sim version, team size and network rules, and we will set up a pilot of the in-simulator agent.
Can Ziva build a full simulation for us?
If you need a Replicator pipeline or a full simulation built for your project, talk to Kena Labs. Kena Labs builds custom simulations and digital twins, including conveyor lines tested in NVIDIA Isaac Sim and plants rebuilt from their drawings. Kena Labs is a sister company of Ziva. Talk to Kena Labs.

Need it built for you?

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

Kena Labs is a sister company of Ziva.

Talk to Kena Labs

Bring Ziva to your Isaac Sim team

Tell us your Isaac Sim version, team size and network rules. We come back with a plan for a pilot.

Talk to us about Isaac Sim