This is community software, not a Valve update, and it is still experimental. A developer on r/SteamFrame has put together an unofficial shell that runs on the Steam Frame itself in place of SteamVR, so open-source PC VR can start with the headset instead of you launching a streaming client by hand. It comes from u/Konsti219, who posted it on r/SteamFrame on 13 November 2026 with a video demo, and the code is on GitHub at konsti219/frame-shell. I have not tried it on a Frame yet, so this is a look at what the project actually claims, and we will be trying it.
What the shell is trying to replace
If you already stream PC VR to the Frame from Linux, you have probably been piecing together a few open-source tools. WiVRn is the usual way to send the game from a PC to the headset over Wi-Fi. WayVR is what puts desktop windows into the headset. Monado is the community VR runtime that can stand in for SteamVR. The README says this shell is built from WayVR and WiVRn, and that it runs on the author’s own Frame Monado runtime instead of SteamVR. In plain terms, it is a home-made environment for the Frame, not a reskin of Valve’s menus.
The project describes itself as unofficial and experimental, which is the right starting point. This is not something you flip on from a Steam setting. It is for Steam Frame owners who want a Linux-friendly, open-source path for PC VR, and who are comfortable installing community software on the headset.
What it actually does
According to the README, once the shell is running you get a dashboard, a keyboard and a watch, plus native desktop windows and a nested Plasma desktop inside the headset. Steam and its games are in there too, including native titles, Windows games, and Android games through Valve’s Android layer on the Frame. PC VR streaming over Wi-Fi is built in, and the author lists error correction, retransmission, and foveation that follows your eye gaze. You can also bring a PC’s monitors in as windows, with laser and keyboard input, and connect several PCs at once: one presents the VR game, the others can overlay on top, and audio can come from all of them.
There is also passthrough, floor setup and eye calibration, plus eye gaze and facial expressions sent to VRChat over OSC, using the eye model from Babble Frame Runtime. Battery warnings and a performance mode for streaming are listed as well. That is a broad feature list for a community project, and I want to be clear I have not confirmed any of it on a headset. I am repeating what the repository describes, not a hands-on result.
WiVRn can already run on the Frame, but you start it yourself
The shell arrives just as WiVRn has been getting native Steam Frame support of its own. On the WiVRn GitHub issue for native Steam Frame support, maintainers say you can already grab a Frame client as a CI build from the WiVRn repository, unzip it on the headset, add it to Steam, and set the compatibility tool to Steam Linux Runtime 4 (ARM64). You can also launch that client outside Steam if you have the matching runtime. There is talk of putting the client on Steam later, but the missing piece mentioned there is store video, not the client itself.
That CI client is useful, but it is still something you start yourself. The shell’s pitch is that it takes that next step. The README says the install puts the WiVRn client, WayVR and a few helpers on the headset, then sets up a service that starts with Frame Monado. After installation, an application is added so you can start it from SteamVR’s “Launch Program” menu, which switches the headset over to the Monado session. The shell’s power menu has an option to switch back to SteamVR. In other words, you are not stuck in the community shell if you want Valve’s software again, at least as the author describes it.
Install is for tinkerers, not a one-tap plugin
I would not treat this like a Decky plugin. The requirements in the README are a Steam Frame with Frame Monado already installed, and a PC with Nix, Podman and a helper called just. From a clone of the repository, one command, just headset, cross-builds the headset side and installs it over SSH. The default login it uses is steamos@frame.local. That puts the client and helpers in your user folder and enables the service that starts with Monado.
On the PC side, the documented setup is for NixOS. You add the project as a flake input, turn on its host module, and name the user who should get the headset’s keyboard and mouse. That runs the WiVRn server and the shell’s host services, including monitor capture, input and notifications, and opens the port it needs. The headset finds PCs on the local network automatically, and the first connection is paired with a PIN, the same way WiVRn usually works. If your gaming PC is not running NixOS, the README does not currently spell out a general Windows or typical desktop-Linux install, so I am not going to invent one.
The project is licensed under GPL-3.0, because of the upstream tools it is built from. If you want more detail on how the pieces fit together, the repository also has development and architecture notes, but you do not need those just to understand what it is for.
Worth watching, with the usual community-tool caveats
Open-source PC VR on the Steam Frame has been a bit of a DIY job, and a shell that starts the stream for you is the sort of thing a lot of Linux-based Frame owners have been waiting for. It still needs a community runtime on the headset, a fairly specific PC setup, and a willingness to switch away from SteamVR. It is also brand-new as a public post, and I have not run it myself.
If that sounds like your kind of project, start with the r/SteamFrame post and the GitHub README, and read the install steps there before you touch the headset. Thanks to u/Konsti219 for posting the work, and to the r/SteamFrame community for surfacing it. We will be trying it, and I will come back to this if we can confirm how it actually feels on a Frame.
