InukaAsith/TwinDesk

Worth a look if you juggle a computer and an Android phone and want them to feel like one machine, but treat it as a young, fast-moving project rather than a settled utility.

The problem

You have a laptop, maybe a second desktop and always a phone, and the edges between them are friction. You mail yourself a photo, retype a link, alt-tab between machines to answer a text, or run two cables for what should be one keyboard. TwinDesk's goal is to collapse that into one surface: the phone's screen and apps open in windows, calls and notifications land on the computer, and the clipboard and files move across with a shortcut. You pair once, then each device behaves like another pane of the same desk instead of a separate island.

What's different

The distinctive claim is how it connects. Instead of requiring both devices on the same Wi-Fi, it can link over USB, Bluetooth, or an on-demand Wi-Fi Direct/hotspot link, and it chooses and migrates the transport for you (connections). It pairs with a code and runs directly between devices, with no account, telemetry or cloud relay; the only outbound request is a GitHub release check you can turn off (privacy). The feature spread is unusually broad for one app: computer-to-computer input sharing, a second screen, phone calls and texts, remote/gamepad use, and a phone camera usable as a webcam for Zoom, Teams or Meet (project overview).

The costs are the interesting part. Breadth across four operating systems with different display stacks means the rough edges will likely be per-platform: on Linux, input sharing goes through evdev/uinput with a one-time Setup grant and screen capture via the desktop portal, and shared folders rely on Samba, installing it and a network-only account on first use (Linux notes). Features are off by default and nothing loads until enabled, which keeps idle overhead down (the README cites about 240 MB to 125 MB on a closed Windows instance) but means initial setup is a checklist, not a single switch.

Who should try it

Good fit: someone with a Mac or Windows machine plus an Android phone who wants notifications, calls, camera and clipboard on the desktop, and who doesn't want a vendor account for it. It's also reasonable for a two-computer desk where the second screen and shared input are the main draw.

Poor fit: anyone whose devices must be on a locked-down corporate network or managed Android fleet where installing a phone app, granting accessibility-level input access or enabling wireless debugging is not permitted. Linux users on Wayland should read the Linux notes first, since that path has extra setup and explicit caveats. A single laptop with no second device has nothing to connect.

Requirements and limitations

Supported floors are macOS 13+, Windows 10/11, Linux on X11 or Wayland, and Android 10+ (project overview). You need the app on every device you want to involve; there is no browser fallback described. Linux is the maintenance-heavy platform: Samba for shared folders and portal-based capture on Wayland mean first-run permissions and possibly a system package install. Android's deeper features may depend on wireless debugging configured once (Android notes).

Upkeep is the real question. The project is 13 days old at the time of the HotRepo record, ships numbered builds (2.4.0) and is GPL-3.0 (releases, license; build/run docs exist for macOS, Windows, Linux, NixOS and Android (project instructions)). None of that establishes how quickly cross-platform regressions get fixed. Verify the release page and Linux/Android notes for your exact OS combination before committing.

HotRepo's take

HotRepo recorded a single dated observation: on 2026-10-28, TwinDesk sat at #22 on the NEW-REPOSITORY board (新项目榜, JavaScript) with 710 total stars. That is not an overall Trending rank, not daily growth, and there is no comparable daily series. Trend persistence cannot be judged. My read: the USB/Bluetooth/direct-link pairing and phone-as-webcam angle make it more than another KVM clone, but the breadth is the risk. Check whether your specific pairing works on the release notes before trusting a whole desk to it.