8086tiny

Plug in the dongle, then press Connect.

You get the PC that is running inside the dongle: FreeDOS, on an emulated 8086, over the USB cable. Both of its displays, side by side — the CGA screen and the BIOS console. Nothing here goes to a network.

Pick the dongle's port in the chooser the browser puts up.
The page hands the device's shell to the PC and shows you both screens.
Keys go to the PC as XT scan codes — arrows and F‑keys included.
Ctrl+] gives the shell back, as does Disconnect.
You can paste. Ctrl+V types the clipboard into the PC — because typing a 63‑character WPA2 key into an emulated 8086 by hand is a cruelty nobody signed up for.

On Linux, do this first. The dongle's port belongs to root:dialout and your browser is not — so the chooser will list it, you will pick it, and it will not open. One udev rule fixes it, and it takes effect on the next replug (no logout): sudo curl -fsSL https://mcu-pc.net/8086tiny.rules -o /etc/udev/rules.d/60-8086tiny.rules && sudo udevadm control --reload-rules && sudo udevadm trigger The 60- matters: the rule has to sort before systemd’s own at 70-, or the thing that reads it has already run. Ours shipped as 99- at first and was a silent no-op. Then unplug the dongle and plug it back in. Why this happens.

This browser has no WebSerial.

Reaching the dongle down the USB cable needs navigator.serial, and this browser does not expose it. Chrome, Edge and other Chromium browsers have it on desktop, and Firefox now does too. Safari does not. There is no polyfill: a web page cannot reach a serial port any other way.

If the dongle is on your network, open http://8086tiny.local/ instead — it serves this same app and talks over a WebSocket, which every browser has.

This page needs HTTPS.

WebSerial is only available in a secure context — an https:// origin, or localhost. Not over plain http://, and not from a file:// URL.

Host it, or open http://8086tiny.local/ and use the WebSocket.