April 25, 2026
Copy-paste cage match
A web-based RDP client built with Go WebAssembly and grdp
Remote Windows in your browser — fans cheer, skeptics ask where the clipboard went
TLDR: A new tool streams a Windows desktop in your browser via a small proxy, no plugins needed. The community’s obsessed with one question: will copy/paste work smoothly, or will browser permissions make it a hassle, leaving skeptics asking why use this over native apps in the first place?
A new project, grdpwasm, beams a full Windows desktop straight into your browser — no plugins, just a tiny proxy server and some Go-in-the-browser magic. The crowd? Split in two. One side is clapping for “RDP in a tab,” the other is rolling eyes. As jqpabc123 shrugs, it’s cool tech, but with remote desktop apps already on every device, why bother? That why vs wow tension fuels the thread.
Then, the plot twist: the entire comments section fixates on one thing — copy/paste. solarkraft asks the question everyone cares about: how does the clipboard behave? the_data_nerd swings in with a reality check, calling browser clipboard rules a “boring nightmare,” thanks to pop-ups, permissions, and clunky workarounds. Cue the “RDP-ception” jokes and collective groans at the idea of pasting your password and getting a permission prompt instead of productivity.
Enterprise folks jump in too: yamapikarya wonders if it works with CyberArk’s .rdp files, hinting at big-company hopes for a quick web-onboarding win. Meanwhile, security hawks point to the project’s own notes: don’t expose the proxy to the wild without protection — keep it on trusted networks and use HTTPS.
Bottom line: slick demo, serious potential, and a copy-paste cage match that’s stealing the show. The browser can stream your desktop and audio, but the community wants proof it can stream their clipboard — smoothly, silently, every time.
Key Points
- •grdpwasm provides a browser-based RDP client using Go compiled to WebAssembly and the grdp library.
- •A Go proxy bridges WebSocket connections from the browser to the RDP server’s TCP port due to browsers’ lack of raw TCP.
- •Build artifacts include main.wasm, wasm_exec.js, and a proxy server; running the proxy serves the client on :8080.
- •The client supports keyboard, mouse, and RDPSND audio via the browser’s Web Audio API, with focus requirements for input.
- •Security guidance recommends using HTTPS/WSS via a TLS-terminating reverse proxy (e.g., Nginx or Caddy); project is GPLv3 licensed and includes a grdp fork adding a Dialer to RdpClient.