Omniverse Realtime Viewer for Codex: Plan Browser Streaming

Select an Omniverse viewer path for an OpenUSD scene and define the browser, local UI and render-server responsibilities before implementation.

中文

Setup for Codex (NVIDIA plugin)

Codex with a local requirements fixture. Actual viewer rendering requires the tools and GPU environment selected by the routing references.

Open the pinned GitHub source for this version. Copy the entire `skills/omniverse-realtime-viewer/` folder with its references into your scratch project's `.agents/skills/omniverse-realtime-viewer/`.
Start Codex from that project and load the skill. Read the routing, streaming-versus-local and conventions references inside the viewer skill before choosing an architecture.

Example task

Describe this toy requirement: the user has a browser with no local USD renderer, and a separate GPU host can produce frames. Require mouse input and a connection indicator in the browser. Ask for a division of responsibilities and a stale-session checks list.

Expected result

The plan selects remote frame rendering and browser-side display, input and status. It identifies a disconnected-session UI state and avoids giving the browser sole ownership of the renderer.

Upstream documentation

Original SKILL.md on GitHub · Apache-2.0 license · Source reviewed 2026-11-15

Frequently asked question

When does an Omniverse viewer need a streaming path?

Choose it when a separate runtime renders frames and the user interacts through a client. Read the current transport and input references for the selected architecture.