Windows
Recommendedv2.27.720MB
One build per platform, all from the same source, all built in public CI with published checksums. No account, no e-mail address, no waiting page.
Latest releasev2.27.7· Released 22 October 2026
v2.27.720MB
v2.27.724MB
v2.27.7104MB
v2.27.732MB
What changed in this versionAlready have it installed? You do not need this page. The app updates itself.
The iOS app is in beta on Apple's TestFlight. Install TestFlight from the App Store, then open the invite link on your iPhone or iPad: it adds you as a tester and installs Mercy SF. Like the Android app, it is a remote control for accounts running on a server or on your own PC.
Run the installer. Mercy SF carries no code signing certificate, so Windows SmartScreen will warn about an unknown publisher: choose More info, then Run anyway. If Windows refuses outright and offers no way past it, that is Smart App Control rather than SmartScreen, and no per-file override exists for it. Take the .msi from the file list instead. It installs the same build through the Windows installer service, and it is quicker about it. If you would rather check first, compare the file against the published SHA-256 checksum.
Open the .dmg and drag Mercy SF to Applications. On the first launch, right-click the app and choose Open so macOS accepts it.
The AppImage needs no installation: mark it executable and run it. The .deb installs with your package manager.
The phone app is a remote control, not a second bot: it drives accounts running on a server or on your own PC. Android only for now, and it is installed by opening the .apk, which asks once for permission to install from this source.
The panel is the desktop app without the desktop: the same engine, driven from a browser. It runs on a server, a Raspberry Pi or the PC in the corner, and you reach it from anywhere. Two parts — the panel you look at, and the worker that plays.
One line. It picks the right build for your machine, fetches the worker and prints a setup code.
curl -fsSL https://mercysf.app/downloads/install-panel.sh | bashOne line. It picks the right build for your machine, fetches the worker and prints a setup code.
irm https://mercysf.app/downloads/install-panel.ps1 | iexOne file, nothing to install: it carries its own Node. The archive is smaller and needs Node 20 or newer already on the machine.
The part that plays. One sign-in per account, every character inside one process. Where it says --node, it is the console build doing the same job under a different name.
Panel 0.4.0
The builds carry no code-signing certificate, so Windows SmartScreen warns about an unknown publisher and a scanner occasionally calls it a trojan. It is not one — an unsigned file simply has no reputation, and a certificate is out of reach for a one-person project. Every file here has a published SHA-256; check it, and put the file through VirusTotal if you would rather see seventy opinions than one.