Extensions
The core of vrOS is overlays, input, performance, and playspace. Creator tools are extensions you turn on one at a time — each one declaring the capabilities it uses, and stopped until you decide.
vrOS 2.0.0 ships that foundation first. The creator features return as extensions, incrementally, and this page says which ones and when.
How they work
A third-party extension runs in its own process. If it crashes it restarts on the policy in its own manifest, and the rest of vrOS keeps running. Built-in extensions run as supervised tasks inside the app on the same discipline.
Before an extension runs, vrOS lists what it asked for — overlays, capture, audio, the event bus, network — in plain words. You grant each one, and you can revoke any of them later in Settings → Extensions. An update that asks for something new asks again for that one thing.
Capabilities the vrOS API controls are enforced by vrOS. Network access is disclosure, not a sandbox: a native program can open a socket without asking vrOS, so the manifest declares it and you see it before you enable anything.
An extension's state lives in the vrOS store, not in the extension's process. A crash, a restart, or a reboot brings it back where it was, and SteamVR coming and going never tears it down.
vrOS is a desktop app first and so are its extensions. Sending an OSC message or firing a soundboard pad works with SteamVR closed.
An extension that is enabled but doing nothing runs no timers, polls nothing, and repaints nothing. OBS control polls stream and recording status only while a panel showing it is on screen.
Extensions install from a folder on your own machine, and the consent screen comes before the first run. Signed distribution is a later step.
Panels
Extensions ship their panels as Slint files and vrOS renders them itself — same renderer, same theme, no web engine anywhere near it.
The roster
Five extensions ship with vrOS 2.0.0. Each one starts switched off; turn it on in Settings → Extensions and its tab joins the Dash.
The VRChat OSC surface in one place: a chatbox with a typing indicator and a sound toggle, avatar parameters in and out, avatar changes, the input namespace, and the camera namespace. OSCQuery and mDNS let VRChat find it and the port it listens on. That port is bound to loopback by default, so nothing else on your network can push parameters at your avatar. The chatbox panel anchors to your wrist.
Connect to up to 16 OBS instances, local or remote, over obs-websocket. Switch scenes, start and stop the stream or the recording, toggle and lock sources, and read the stats. A compact director panel floats in front of you with the scene grid, stream and recording state, and tally.
Pads with per-entry volume and loop, played through the vrOS audio engine. One sound can reach more than one output at once, so a clip hits your headphones and a virtual mic together. Pads are commands, so you can bind them to a controller in SteamVR.
Chat on a panel with 7TV emotes, an ad manager with a heads-up ad warning in VR, and up to four live stream players you can place in your space. Signing in uses the device-code flow, so vrOS never sees your password.
Brings face tracking from a Quest Pro streaming over Steam Link into vrOS, so O·VR can send your expressions to VRChat over OSC.
Built-in extensions arrive with their capabilities already granted, except video playback and face data, which always wait for you to allow them. You can revoke any of them in Settings → Extensions, the same as a third-party one.
Building one
Extensions talk to vrOS over a local socket — JSON-RPC, one object per line — so an extension can be written in any language. First-party features are built on that same API on purpose: if VRChat OSC cannot be built on the extension API, the API is wrong.
The extension SDK is not public yet.