No description
  • JavaScript 33.8%
  • Python 27.8%
  • CSS 22.7%
  • HTML 10.3%
  • Nix 5.4%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
yuuhikaze 86c9ec953e feat: make keys hold like mouse buttons, refresh screenshots
Keys now send distinct down/up events through the same serialized
request chain and pointer-capture handling as clicks, so a held key
stays held instead of firing a single tap — and /api/release-all now
also tracks and releases any keys left down, not just mouse buttons.

Screenshots updated to show the [ RELEASE ] control added for the
earlier stuck-button fix.
2026-10-18 16:49:56 -05:00
docs feat: make keys hold like mouse buttons, refresh screenshots 2026-10-18 16:49:56 -05:00
static feat: make keys hold like mouse buttons, refresh screenshots 2026-10-18 16:49:56 -05:00
flake.lock feat: initial remote-pad implementation 2026-10-18 16:28:23 -05:00
flake.nix feat: initial remote-pad implementation 2026-10-18 16:28:23 -05:00
README.md feat: make keys hold like mouse buttons, refresh screenshots 2026-10-18 16:49:56 -05:00
server.py feat: make keys hold like mouse buttons, refresh screenshots 2026-10-18 16:49:56 -05:00

remote-pad

Minimal phone-controlled mouse/keyboard pad, backed by ydotool.

Built to work around KDE Connect's remote-input plugin not working under wlroots compositors (it needs the RemoteDesktop xdg-desktop-portal interface, which xdg-desktop-portal-hyprland doesn't implement yet). This talks to /dev/uinput directly through ydotoold, so it works regardless of compositor or portal support.

Screens

Mouse Keyboard
mouse view keyboard view

Both mouse buttons and every key send separate down/up events tracking the actual press, so holding either one holds it on the target (e.g. a drag in Excalidraw, or holding a key in a game) rather than firing a single tap. Requests are serialized client-side to keep down/up ordered despite network jitter, and [ RELEASE ] in the status bar force-releases everything currently held — it also fires automatically if the tab is backgrounded or closed mid-press, so nothing is left stuck down.

Requirements

  • ydotoold running and reachable at /run/ydotoold/socket
  • the user running server.py in the ydotool group (or otherwise permitted to reach that socket)

Running

With Nix:

nix run .

Or directly:

python3 server.py

Either way it listens on 0.0.0.0:1763. Open http://<host>:1763 from a phone on the same network.

Why port 1763

No firewall rule was added for this — 1763 was picked because it already falls inside the 1714-1764 TCP range KDE Connect opens, so it works without touching any host firewall config.