Get Started
Pick your platform. Windows ships packaged installers in dependency order; macOS is a developer source build today.
Check the prerequisites
Required- Windows 10 version 2004 or later (Windows 11 recommended)
- A tracked 3D display supported by DisplayXR — currently Leia SR displays (Lume Pad, Leia 3D laptops). See the compatibility matrix for the full list.
- Admin rights to run the installers (each registers under
HKLM\Software\DisplayXR)
No 3D display? You can still install everything — the runtime ships a simulated display driver (sim_display) for development on a regular monitor with WASD + mouse eye-position control.
Install the DisplayXR Runtime
RequiredThe runtime is the OpenXR layer every DisplayXR app talks to. It includes the native compositors (D3D11, D3D12, Vulkan, OpenGL) and the Windows service.
- Download DisplayXRSetup-*.exe from the runtime releases page.
- Run the installer and accept the defaults.
- On first install, the DisplayXR Service is registered and started, and
HKLM\Software\Khronos\OpenXR\1\ActiveRuntimeis set to the DisplayXR runtime JSON.
After this step, any OpenXR app on the system will route through DisplayXR. If you only want OpenXR for your own 3D-display app, you can stop here.
Install the DisplayXR Shell
OptionalThe shell is the reference spatial workspace UX — a 3D window manager that runs multiple OpenXR apps and captured 2D apps in a single head-tracked workspace. Optional; install it if you want a spatial-desktop experience.
- Download DisplayXRShellSetup-*.exe from the shell releases page.
- Run the installer. It reads
HKLM\Software\DisplayXR\Runtime\InstallPathand will refuse to install if the runtime is missing — finish step 2 first. - The shell installs into the runtime's tree and registers itself at
HKLM\Software\DisplayXR\WorkspaceControllers\shellso the runtime's service orchestrator can discover it.
OEMs and vertical integrators can ship their own workspace controllers using the same XR_EXT_spatial_workspace contract; the shell is just the reference implementation.
Install DisplayXR MCP Tools
OptionalEnables AI-agent and voice control of your spatial workspace. Optional; install it if you want Claude, ChatGPT, or other MCP clients to introspect and drive your spatial workspace.
- Download DisplayXRMCPSetup-*.exe from the MCP releases page.
- Run the installer. It writes
HKLM\Software\DisplayXR\Capabilities\MCP\Enabled = 1. - On next launch, the runtime and shell each spawn an MCP server thread. Phase A (per-app introspection) is exposed by the runtime; Phase B (workspace control) by the shell.
Per-process opt-out: set DISPLAYXR_MCP=0 before launching an app.
Verify the install
Required- Service running: open
services.mscand confirm DisplayXR Service shows as Running. - Active OpenXR runtime: from a command prompt,
reg query HKLM\Software\Khronos\OpenXR\1 /v ActiveRuntimeshould return the DisplayXR JSON path. - Shell installed (if step 3):
reg query HKLM\Software\DisplayXR\WorkspaceControllers\shellreturns its install path. DisplayXR Shell appears in the Start menu. - MCP installed (if step 4):
reg query HKLM\Software\DisplayXR\Capabilities\MCP /v Enabledreturns0x1.
First launch
RequiredLaunch DisplayXR Shell from the Start menu (or Ctrl+Space from the tray icon). The shell auto-starts the service if it isn't running, then activates the spatial workspace on your tracked 3D display.
Try the basics:
- Open a few apps — they auto-adopt as 3D-positioned windows
Ctrl+1…Ctrl+8— cycle layout presets (side-by-side, theater, carousel, helix, …)TAB— cycle focus;V— toggle 2D/3D display modeCtrl+Shift+C— capture a stereo screenshotESC— dismiss the shell and restore your normal desktop
Full keyboard reference and feature catalog: shell README.
Troubleshooting
Shell installer says the runtime isn't installed
HKLM\Software\DisplayXR\Runtime\InstallPath. If this key is missing, the runtime install didn't complete. Re-run DisplayXRSetup-*.exe as admin and confirm DisplayXR Service appears in services.msc before retrying the shell installer.OpenXR apps still route to my old runtime
HKLM\Software\Khronos\OpenXR\1\ActiveRuntime. Confirm it points to the DisplayXR JSON; some VR runtimes (SteamVR, Oculus, WMR) reset this on launch. You can force DisplayXR per-process by setting XR_RUNTIME_JSON to its JSON path.Shell launches but the display stays in 2D
V to toggle 3D mode. The shell is focus-adaptive: focusing a 2D-only app intentionally drops back to 2D. If 3D mode never engages, check that the Leia SR service is running and that the display is recognized in your vendor control panel.MCP server isn't reachable from my agent
HKLM\Software\DisplayXR\Capabilities\MCP\Enabled is 1 and that the runtime / shell were restarted after installing MCP Tools. Each app process hosts its own named-pipe MCP endpoint; the shell hosts workspace-control tools. See the MCP spec for the connection topology.Where to next
How it works
Native compositors per graphics API, the workspace controller model, and how 2D + 3D apps share one display.
Build for 3D displays
The OpenXR extensions DisplayXR adds — XR_EXT_display_info, window bindings, and the workspace surface.
See it in action
Reference apps and demos you can install alongside the runtime to verify your setup.