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.
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:
This looks really cool, thinking about getting one. I saw Jeff Geerling talk about it on his YT channel a few weeks ago. It could definitely help speed up remote diagnostics but I'm not sure how useful the AI agent control is except in very specific crash/debug scenarios. Otherwise most people will run the agent directly on SSH.
Some of the links on the GitHub to buy are dead, I can't even see where to buy it clearly in US.
Hello@zepan congrats on the launch! I keep a headless mac mini at my parents place and teamviewer is useless the second the kernel panics. That's why i'm looking at this. Before i back it - when the target is asleep on macos, does the USB-C link wake the machine or am i staring at a black screen until someone walks over and taps a key? Cool idea, let's connect!
plugged it into my mini pc and had claude poking around the bios within minutes, wild stuff
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 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 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
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.
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 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?
About NanoKVM-Go on Product Hunt
“Give your AI agent physical control over any screen”
NanoKVM-Go launched on Product Hunt on July 8th, 2026 and earned 122 upvotes and 11 comments, placing #14 on the daily leaderboard. 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.
NanoKVM-Go was featured in Open Source (68.6k followers), Hardware (11.4k followers) and Computers (2.3k followers) on Product Hunt. Together, these topics include over 17.3k products, making this a competitive space to launch in.
Who hunted NanoKVM-Go?
NanoKVM-Go was hunted by Zac Zuo. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how NanoKVM-Go stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
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: