All of that, and the session you left running at your desk, from wherever you are.
pinmesh-2.2.2-claude-setup.exe · 38M · Windows 10 or later, 64-bit.
SHA-256 d6ca4aa73be5ac7b5da13ac9a07c8d3beafdd83f00d6a99b0c3b2689e6ae5f32
The browser refuses the download, and Windows covers the screen with a blue panel when you run it. Both are saying one thing: this installer has no code-signing certificate, because it has not been through Microsoft's signing yet. Neither is about what is inside the file.
Both hide the way past. In the browser it is beside the blocked download — the ⋯ menu in Edge, an arrow in Chrome. On the blue panel it is a small link, and the button that runs it anyway appears underneath.
The SHA-256 above is how you check that what you downloaded is what we published.
Installation asks for administrator once, to register a service and configure routes. Sign-in happens afterwards in the app, not during — an icon appears in the notification area when the installer finishes, and the app window opens from it.
pinmesh-2.2.2-claude.pkg · 39M · macOS 13 or later, Apple silicon (M1 or newer).
SHA-256 d6d2b045aa66cc1314e26b7cff86048cea5e999c35f12dc803464da960f069c7
The installer is not notarized by Apple yet, so the first time you open it macOS says it cannot verify it and will not open it. That is about where the file came from, not about what is inside it.
The way past is in System Settings. Open Privacy & Security, scroll down, and press Open Anyway beside the installer's name. Then open the installer again.
The SHA-256 above is how you check that what you downloaded is what we published.
Installation asks for your password once, to register a service and configure routes. Sign-in happens afterwards in the app — an icon appears in the menu bar when the installer finishes, and the app window opens from it. Letting this Mac be seen from your other machines asks for Screen Recording and Accessibility, the first time you use it.
SHA-256 79cf919389027d8fc7844c62c4c16dedb39855d7e8977b138e518a90fc6178b6
This is the same package the VPN page hands over. A Linux machine has no app window, so there is nothing to install or leave out — the package carries the session server either way, and it stays asleep until you turn sessions on.
Turn it on in /var/lib/pinmesh/settings.json with "offer_sessions": "yes", then restart the service. That machine can then be attached to from your desk.
Not Debian-derived? Download the tarball — it holds the same three binaries and an install.sh.
pinmesh-2.2.2-claude.apk · 36M · Android 8.0 or later, 64-bit ARM.
SHA-256 3e80a64574152b83990045eb6dd2bff9500bc79e455f94efb3cd2d6597028b62
It is not on Google Play yet, so the file arrives through the browser. Android asks whether that browser may install apps, and Play Protect offers to scan something it has not seen before. Both are because the app has not been through Google's review — neither is about what is inside the file.
The SHA-256 above is how you check that what you downloaded is what we published.
This is Pinmesh for VPN with terminal sessions added, as one app — if the VPN app is already on the phone, this installs over it and keeps your sign-in and this device's identity. There is no store to deliver updates, so a new release means coming back to this page.
Everything the other two do, and then the machine you actually work on. The session you left running at your desk keeps running there; your laptop, or your phone on the train, attaches to it and lets go again, and the work does not restart because you moved.
This one is for people who work at a terminal. If that is not you, the other two are the ones to watch.