
Arcade cabinet as a smart-home device
A living-room arcade cabinet where everything except running the retro games is offloaded to a configurable container on the home server. The cabinet itself does one job. Configuration, library, themes, brightness, and repair all happen over the network, so the device is set up and changed with almost no input on the machine itself. It is a smart-home device that happens to play games.
- The cabinet is an MCP server: Joy and Home Assistant can list games, launch them, change themes, and dim the screensaver over the network
- Repair agents run on the cabinet and are exposed over the network as a first-class feature; a broken config or a stale emulator gets diagnosed and fixed from the server, not with a keyboard on the floor
- A config-as-code repo re-renders the emulator configs before every launch so nothing drifts
- The remote library pushes games over a tunnel with checksums and resumable transfers
- Joystick plus two buttons must reach every screen; anything else is filed as a theme bug
- Prime directive: emulation keeps working with the network cable cut. Chaos soak of eight hours of injected partitions and daemon kills, zero violations
The cabinet is the thinnest possible client. Everything worth changing lives where an agent can reach it.
- Python
- Linux
- MCP
- WebSocket
- RetroArch
- Home Assistant
- Toxiproxy
Arcade cabinet, in twenty-five seconds
An arcade cabinet that's really a smart-home device: favorites first, joystick plus two buttons, and every setting, game, theme, and repair handled from the server by an agent you talk to in plain language. Cut the cable and the games still run.








