JetKVM

Add a JetKVM like any other KVM: type its address and QKVM recognises it. Leave the password empty if the JetKVM has none; the user name is ignored. It needs the aiortc package (pip install aiortc), because a JetKVM has no "send me a picture" request: its screen exists only as WebRTC video, so QKVM connects the way the JetKVM's own page does. Three things are different from a Comet, and they come from the device:

• One viewer at a time. A JetKVM shows its picture to a single connection. While it is on the wall, QKVM is that viewer. When someone opens the JetKVM's own console, the tile says In use elsewhere and QKVM stays away, so it never throws that person out. Show here on the tile takes the picture back (and disconnects them).
• Signing in signs others out. A JetKVM with a password has one session for everybody: when QKVM logs in, a browser logged in to that JetKVM has to log in again, and the other way round. QKVM logs in once and keeps its session for as long as it can.
• It must be reachable directly, on the LAN or over a VPN such as Tailscale. JetKVM Cloud only works from a browser signed in with Google, so QKVM cannot go through it.

The picture is decoded on the computer running QKVM, and a JetKVM sends video at the rate of the screen it watches. Measured with a 1920×1200 screen at 60 frames a second, one JetKVM takes about 15 % of one core of a desktop processor for as long as somebody has the wall open; half a minute after the last viewer has gone, QKVM disconnects and it takes nothing. Keys, typed text (US layout, ASCII only), keep-awake, Wake-on-LAN, the ATX power extension and reboot work from the action menu.