Helm turns an Android phone into a remote for a Windows PC: a launcher dock, a touchpad and keyboard, the live PC screen, media and power controls, files and clipboard both ways, and a Stream Deck-style button grid. It is free, needs no account, and every connection is encrypted.
The problem
Apps that let a phone control a PC each do one part of the job. KDE Connect is good at clipboard and files, Unified Remote at app-specific remotes, Macro Deck at button grids. WinDock, the one I studied most closely, has a nice launcher dock, but it serves its controls over plain HTTP (its README says so), so anyone on the same Wi-Fi could read what you type. Its Android app is a WebView around that page.
I wanted one native app that does all of it, over a connection that only my phone can use. Helm is written from scratch: the other projects were references for ideas only, and no code was copied from them.
Decisions that shaped it
Pair once with a QR code, then never type a PIN again. The PC shows a QR holding its address, the fingerprint of its certificate and a one-time token that expires after 5 minutes. The phone connects over TLS 1.3 and trusts only that exact certificate. After the first pairing the phone signs in with its own key, kept in Android Keystore, and the PC's key is protected by Windows DPAPI. The two recognise each other after reboots, and either side can revoke the other.
Native on both sides. The PC agent is Rust, with a Tauri 2 window and a tray icon; closing the window keeps Helm running so phones stay connected. The phone app is Kotlin with Jetpack Compose, not a WebView, so it gets low-latency input, hardware video decoding, home-screen widgets and the Android share sheet.
Write the protocol before the code. Every message is documented in
PROTOCOL.mdfirst, so the PC and the phone always agree. Touchpad movement goes as small fire-and-forget frames with no id and no reply, so the cursor never waits for an answer. File data goes in binary frames (a 16-byte transfer id, an 8-byte offset, then the data), and every file is checked with SHA-256 before it lands inDownloads\Helm.A live screen that uses the hardware. The PC captures its screen with Windows Graphics Capture and encodes it with the GPU's H.264 encoder through Media Foundation, in low-latency mode with no B-frames. The phone decodes it in hardware. PC audio comes along as 20 ms Opus frames, and the cursor is sent separately and drawn on the phone, so it never smears. The pipeline is built for under 50 ms on 5 GHz Wi-Fi at 1080p and 60 fps.
Remote control is a big permission, so it is split up. Each phone gets a Viewer, Remote or Admin tier. Power and terminal actions need a fingerprint on the phone, ask before they run, and are written to an audit log on the PC.
Away from home, the relay sees only ciphertext. Helm can work over USB tethering, Tailscale, or a relay that is a small Cloudflare Worker. The encrypted phone-to-PC session runs inside the relay tunnel, so the relay passes bytes it cannot read.
Updates that refuse tampered files. Both apps check for a new release, download it and verify an Ed25519 signature before installing. A file that does not match is refused.
Built phase by phase, each with a gate. Every phase had a written acceptance test before it started. The first one: the phone finds the PC, pairs by QR, reconnects after the agent restarts without pairing again, and revokes itself. Only then did real controls start.
What changed in each release
Seven releases went out between 31 October and 7 November 2026:
- 0.1.0 preview: discovery on the home network, QR pairing over pinned TLS, trusted devices.
- 0.2.0: the desktop window and tray, auto-reconnect after a Wi-Fi change, three-finger gestures, an on-screen gamepad and a presentation mode.
- 0.3.0: a full-screen landscape touchpad, a floating keyboard, a cursor that ignores Windows pointer acceleration, full-screen sharing, connect from anywhere and in-app updates.
- 0.4.0: the phone as a Bluetooth mouse and keyboard with no Helm on the PC (Android 9 or newer), and control of the phone from the PC. The phone owner accepts every session, a notification with a Stop button stays visible, and banking apps, password fields and the lock screen stay protected.
- 0.4.1: the phone tries all of the PC's addresses at once, and the PC no longer offers VirtualBox, VPN or other virtual adapter addresses.
- 0.4.2: Swipe mode on the Screen tab, which works like using a phone: tap to click, swipe to scroll, long press to right-click.
- 0.5.0: flick scrolling, quick keys, a data saver for mobile data, signal and latency on the status line, a home-screen widget, and a PC that stays reachable after Windows restarts.
Known limits
The release notes say plainly that the newest features had not yet been tried on a real phone when they shipped, so I ask people to report what they find. The builds are not signed with a publisher certificate yet, so Windows SmartScreen asks for "More info, Run anyway" the first time. Helm needs Windows 10 or 11 and Android 8.0 or newer; there is no iPhone or Mac version.
Built with
Rust, Tauri 2, Kotlin, Jetpack Compose, TLS 1.3, WebSockets, Media Foundation (H.264), Opus, Cloudflare Workers
Originally published at helm.niranjand.in.
Top comments (0)