Launching today
NanoKVM-Go is a watch-sized, serverless 4K KVM with WiFi 6 and built-in Tailscale. It acts as an open MCP server to give AI agents hardware-level screen visibility and keyboard/mouse input control over any connected laptop or mobile device.
Flowtica Scribe
Hi everyone!
NanoKVM-Go is a tiny 4K USB-C KVM that gives you hardware-level control of a real device through one USB-C cable.
That makes it interesting for computer-use agents. Software agents can operate inside an OS, but a KVM sits outside the machine. It can still show the screen, send keyboard and mouse input, and help with cases like a frozen system, BIOS setup, remote OS install, or a device that needs a real reboot.
NanoKVM-Go also exposes its KVM functions through MCP, so an agent can use the same hardware control path instead of only relying on software APIs.
The Go+ version adds local OCR and screen memory, so your screen history becomes searchable context for both humans and agents.
Maybe agents don’t always need a new computer. Sometimes they just need a hardware-level way to work with the devices we already use:
The out-of-the-OS angle is what makes this genuinely useful for computer-use agents. An in-OS agent goes blind exactly when you need it most: a kernel panic, a BIOS screen, a full-screen modal that isn't in the accessibility tree. A KVM at the pixel and HID level still sees all of that. The tradeoff is you lose every semantic hook, no DOM or a11y tree, just a 4K frame the model has to OCR and lay out itself. For that loop the number I'd care about is the capture-to-input round trip: what latency and frame rate does an agent get over the USB-C link at 4K?
the physical theft angle is what I'd want nailed down before this. if it's watch-sized, serverless, and reachable over Tailscale, the threat isn't really "agent misuse" as much as "someone finds or steals the device." is there any local auth or pairing step required before it accepts HID commands over the network, or does joining the Tailscale network + knowing it's there give you the same full keyboard/mouse control as the legitimate owner
As AI agents gain direct control over real devices, what safeguards are in place to prevent accidental actions or misuse, especially on systems handling sensitive data?
the Go+ version's local OCR/screen memory turns your screen history into searchable context - where does that index actually live, and is there a way to exclude specific windows or apps from ever being captured into it? Feels like it could end up holding some pretty sensitive stuff by accident otherwise.
The hardware boundary is the interesting part. An agent outside the OS can help when the machine is frozen, headless, or stuck before login, but that also makes the checkpoint model more important: visible session recording, easy revoke, and a hard human approval step before destructive input.
The watch-sized form factor with built-in Tailscale is genuinely clever, makes sense for something you can drop in a bag and spin up anywhere without fighting VPN configs.