Isaac Sim

Active

An AI agent for Isaac Sim. It works in a scene with a live connection to Isaac Sim. It asks before it writes, and every run is traced.

Connect a GPU host running NVIDIA Isaac Sim with the BEHAVIOR-1K stack. Launch policy rollouts, watch episode results and videos land, and monitor the machine — a simulated world inside your scene.

Infrastructure Custom 1 asset type 6 tools

What you can connect

Add these to your scene and AI gets access.

Sim Host Sim Hosts

A GPU machine running the Isaac Sim / BEHAVIOR-1K eval stack

Tools

What the agent can do once this is connected.

Reads 4

See data. Nothing changes.

isaacsim_host_status GPU, disk, dataset, and process status of the Isaac Sim host (policy server, sim workers, downloads)..

isaacsim_list_episodes List eval runs on the host (newest first) with result/video counts and summary scores..

isaacsim_get_episode Full results of one eval run: summary or per-instance JSONs plus video artifact paths..

isaacsim_tail_log Tail a named log on the host: setup, download, policy, runner, or worker..

Writes 2

Change data in the connected system.

isaacsim_run_eval Launch a BEHAVIOR-1K rollout batch on the host (detached).

isaacsim_stop_eval Stop the running eval (runner + sim workers).

Connect Isaac Sim over MCP

Daslab is itself an MCP server.

Connect Isaac Sim in a scene, then pin that scene's URL in Claude Code, Cursor, or any MCP client. The agent there gets your Isaac Sim tools, and your approval gate and trace travel with them.

https://daslab.run/mcp/<your-world>/<your-scene>

One scene can hold Isaac Sim and everything else you connect, so a single endpoint carries them all. Set up a client.

Use cases

Run BEHAVIOR-1K evaluation rollouts from a scene
Monitor GPU fleet status and episode results
Collect rollout videos and metrics as assets

From Isaac Sim

API reference →

Similar integrations

Others in Infrastructure.

SSH Sandbox

Ready to try Isaac Sim with Daslab?

Get started with CLI