Meta’s Immersive Web SDK 1.0 Lets AI Agents Test WebXR Apps on a Connected Quest

Meta published a developer blog on October 14 that puts a SHARPER focus on Immersive Web SDK 1.0: AI AGENTS can now RUN and PROFILE web-based VR apps on a Meta Quest headset plugged into a developer’s computer, not only inside a desktop emulator. The framework remains a website-first WebXR stack built on Three.js, and Meta says frame-rate and browser MEASUREMENTS in that LOOP come from the DEVICE itself.

The Meta Horizon OS Developers post frames 1.0 as a STABLE foundation—grabbing, locomotion, Havok physics in a Web Worker, spatial UI, and mixed reality—plus an AI-native tool suite. Every new PROJECT ships with a Model Context Protocol server and agent SKILLS so an agent can INSPECT a scene, move simulated inputs, PAUSE the engine, and SEARCH the real IWSDK API instead of guessing.

Front view of a Meta Quest 3 headset

Until now that TEST loop stayed on the desktop emulator. With 1.0, Meta says the SAME commands can drive an app on a CONNECTED Quest. In Meta’s own DEMO, an agent PLAYED every level of Hyperform on Quest 3, FIXED slowdowns, and REPLAYED until the game HELD 90 FPS. That result is a COMPANY demonstration, not an independently verified benchmark, a caveat Superpower Daily also notes.

Agentic Scene Composer and Glasses Preview

The Agentic Scene Composer lets developers and AGENTS edit the SAME 3D scene: people arrange assets visually while the agent WRITES models, materials, and BEHAVIORS in code. Meta says it used the workflow to BUILD Connect Island, an open sample with a pavilion, session stage, and day-night cycle.

Version 1.0 is also POSITIONED for Meta VR Glasses, which Meta still TARGETS for Spring 2027. Gaze acts as a POINTER—LOOK at a target, then PINCH to select—and Meta says existing ray-based buttons, menus, and grabbable objects can use that INPUT without separate gaze-specific code. On Quest 3 and 3S today, head direction stands in for eye tracking and a CROPPED view PREVIEWS the glasses’ narrower field of view; REAL eye tracking waits for the HARDWARE.

What Changed in the Release Notes

The v1.0 release notes list the technical HOOK for connected testing as --native-xr-control, which connects IWSDK XR and ECS automation to a browser-owned immersive session on Quest. They also document gaze-and-pinch through world.xr.features.gazeTracking, with DIRECT touch and ACTIVE grabs taking PRIORITY over gaze, and hand or controller rays returning if tracked gaze becomes unavailable.

Developers start with npm create @iwsdk@latest. Meta notes that teams already on 0.5 should UPDATE IWSDK packages TOGETHER and check the changelog for a few changed defaults. The Meta VR Start Developer competition, which Meta says runs through November 18, 2026 with $1M in TOTAL prizes, is open to immersive web experiences as well as native titles.

Sources: Meta Horizon OS Developers (October 14), IWSDK v1.0 release notes, and Superpower Daily.

Leave a Comment