Get RPCTION.

System requirements

Nothing here is code-signed

That is a decision for this release rather than an oversight. Certificates cost money and take time, and holding a working build back for them helps nobody, so v0.1.0 ships unsigned and says so. Every operating system reacts to that in its own way, and each one is described plainly below, including the case where the honest answer is that it will not run.

We are not going to ask you to switch a security feature off. The SHA-256 of every file is published here, so you can confirm that what you downloaded is what was built.

Windows 10 / 11 x64

Requires Windows 10 or 11, 64-bit.

1. Run the installer. It is per-user: no administrator rights, and it installs into your own profile.
2. Windows will warn you, or refuse it outright, see below.
3. RPCTION starts into the system tray and shows a short setup.
4. Windows may ask to allow screen capture. RPCTION needs it to see what you are pointing at.
5. Press CTRL SHIFT R anywhere.

Installing over 0.1.0 keeps your hotkey and your modes. The portable build is a single executable that installs nothing, useful on a machine you do not want to change.

RPCTION is currently unsigned. Windows Smart App Control may refuse the application.

Windows has two separate protections and they behave completely differently, so which one you meet decides whether you can run this at all.

SmartScreen shows “Windows protected your PC”. Choose More info, then Run anyway. That is a warning, not a virus detection: it means Windows has not seen this file signed by a known publisher.

Smart App Control refuses unsigned applications outright. There is no Run anyway, and downloading again or waiting does not help, it judges on signing, not on reputation. It is on by default on many clean Windows 11 installs. Check under Windows Security → App & browser control → Smart App Control. If it is on, this build will not run on your machine.

We are not going to suggest turning it off. It cannot be switched back on without resetting Windows, and trading a security feature away to install one small tool is a bad deal. Waiting for a signed build is the better answer.

You do not have to take our word for what you downloaded. Check it against the hash published beside it, or against SHA256SUMS, which lists every file in this release:

Get-FileHash .\RPCTION-Setup-0.1.0.exe -Algorithm SHA256

f09bf2f11d8659d80ec8ed12f9c44ffbdff91084c3843ed0d717e0c875370700

4b5d2b6a0962205a575d63d21794b2b8854b94edaf557281ed4ac60969f97f31

Removing it

Settings › Apps › Installed apps › RPCTION › Uninstall, or run the uninstaller in the install folder. It removes the application, both shortcuts and the registry entry.

Your settings are deliberately left behind, so reinstalling keeps your hotkey and modes. They live in %APPDATA%\RPCTION\settings.json - delete that folder for a completely clean removal.

Linux x86_64

Requires x86_64. Built and started on Ubuntu, other distributions are expected to work and have not been tried.

1. Download the AppImage.
2. Make it executable with chmod +x RPCTION-*.AppImage, then run it. Nothing is installed, no Node, no npm, no package manager.
3. The first start is slow. An AppImage mounts itself and decompresses as it reads, so RPCTION takes far longer to appear the first time than it does afterwards, measured at 37 seconds on a CI machine with slow storage, against under 4 seconds for the same build unpacked on disk. Give it a minute before deciding nothing happened.
4. If it truly does nothing, you are probably on a distribution that ships only FUSE 3. An AppImage needs FUSE 2 to mount itself: sudo apt install libfuse2 on Ubuntu 22.04 and later, or run it once with APPIMAGE_EXTRACT_AND_RUN=1 to unpack instead of mounting, which is also the faster way to start it every time. Both are properties of the format rather than of RPCTION.
5. Press CTRL SHIFT R anywhere, on X11. On Wayland, see below.

How much of RPCTION works depends on your session rather than your distribution. Under X11 everything is available. Under Wayland the compositor owns global shortcuts, so RPCTION’s hotkey will not fire, bind it in your desktop settings instead, and screen capture goes through the desktop portal, which asks permission each session. Linux has no equivalent of the capture-exclusion flag Windows provides, so RPCTION’s own overlay can appear in Motion exports.

The AppImage is unsigned.

That is normal for the format and no desktop will block it for that reason, which makes Linux the one platform where being unsigned costs you nothing. Check the SHA-256 below against your download and you know exactly what you have.

You do not have to take our word for what you downloaded. Check it against the hash published beside it, or against SHA256SUMS, which lists every file in this release:

sha256sum -c SHA256SUMS

29f7a23dd242a4f340e1f5dc4e7ebc8ebaefe651eb6afe75747ca6ad4696cf25

Removing it

Delete the AppImage. Your settings live in ~/.config/RPCTION/settings.json and are left behind on purpose, delete that folder for a completely clean removal.

What you get

• Text, URL, email, phone, address, table and QR recognition, all on device.
• Object extraction to a transparent PNG.
• SOURCE: read code off the screen and rebuild it locally, with its origin always stated.
• AUDIO: capture the last 2, 5, 10 or 30 seconds of what you are hearing, as a .wav.
• Motion Mode: follow something moving and export it as video, GIF, PNG sequence, or a transparent extraction.
• Thirteen modes, cycled with Tab, and a rebindable global shortcut.

What is not there yet

• Code signing on Windows.
• macOS. There is no macOS build, and this page does not offer one.
• A manual pass on any platform. Every build is produced on its own operating system, checked automatically and launched once to confirm it starts, which is a smoke test, not somebody sitting down and using it.
• Languages other than English for text recognition.
• Automatic updates. v0.1.0 does not check for new versions, which is also why it never contacts the network.

Known limitations

RPCTION performs local visual analysis and extracts selectable visual entities. It does not know what things are, there is no object classifier and no cloud model, so some scenes are genuinely ambiguous to it. Two objects of the same colour that touch, something seen through glass, a heavily compressed photograph: these can produce a selection that is not what you meant. The selection is always shown before you act on it, and you can cycle up and down the hierarchy to correct it.

The limitations page is the full, honest list, and the FAQ covers the common questions.