Agent-Operable Engines
Agents that can look at and operate the 3D scene, not only talk about it.
Lesson
Give the agent eyes and hands on one engine at a time; the reasoning stays in the agent harness.
The lesson in full: Improving the complexity does not always help bring the ball forward; sometimes simplicity in the agent’s context survives break-neck pace better. Previous well-tuned instructions, examples and evals can look well-crafted but might confuse agents more than they help. Adding ‘enabler factors’ instead of overloading the context with intricate details often yields better results.
What it is
The Reasoning Engine gained MCP support, both for connecting to external MCP servers as well as leveraging complex internal ones. Three engines got agent-facing MCP servers I call reasoners: one over the CAD import engine, one over the Omniverse render engine, one providing the internal Surface/Twin SDK as simple and descriptive tools. These MCP servers as well as their CLI counterparts provide agents with the context and grounding they need to do value-bringing work. This is especially true for the latest class of LLMs like GPT-6 Astra and Opus 5.5 (as of 2026-10) with highly ‘spatial/multimodal reasoning’ capacities, where the work turns into not guiding them as much but rather providing them with richer context.
Tools and technologies
MCP · OpenUSD · Image-in-the-Loop · Multimodal · CLI
Lineage
Built on lessons from Multi-Agent Reasoning Engine, Standalone AI Agents, Omniverse Remote Rendering, Video Calls in XR.
Lessons carried into Spatial Intelligence for Agents, Drawings to 3D Scene.