Skip to main content
The Capy desktop app ships for Linux as an AppImage, a .deb package, and a portable .tar.gz, each for x64 and arm64. Pick by distribution, not by preference: the AppImage runs anywhere, the .deb is only for Debian and Ubuntu, and the tarball is for package maintainers. Every build is listed on the download page.

​
Which download to pick

Installing the .deb on a distribution without dpkg and apt does not work and can leave the package half-installed. If that happened, sudo dpkg --remove capy cleans it up, then use the AppImage.

​
AppImage

Download the AppImage for your architecture, mark it executable, and run it:
The AppImage needs no FUSE and no extra libraries. The app updates itself: it checks for a new version a few seconds after launch and every few minutes after that, downloads it in the background, and shows an Update control in the tab band when the new version is ready to install. Keep the file where you first ran it, because the update replaces that file in place.

​
Arch Linux

The capy-bin package installs the stable release under /opt/capy with a capy launcher and a desktop entry:
Updates arrive through pacman like any other package, and the in-app updater stays inactive so the two never fight over the install. Any AUR helper works in place of yay.

​
Debian and Ubuntu

Install the .deb with apt so its dependencies resolve:
The app updates itself. When an update is ready and you choose Update, the app asks for your password once to install the new package.

​
Portable tarball

The .tar.gz unpacks to a directory containing the capy executable and its resources, with nothing else assumed about the system. It is the input for downstream packages such as capy-bin, and it never self-updates: whoever unpacked it delivers the next version, and Check for Updates says so. The same applies to an AppImage you extracted with --appimage-extract; run the AppImage file itself to get updates.

​
Signing in and the keyring

The app keeps your session encrypted with the desktop keyring (GNOME Keyring or KWallet) when one is running. On a desktop without a keyring it still signs you in and stores the session under a key built into the app, and the sign-in screen says so.

​
If an update fails

Choose Check for Updates from the Help menu to see why. A full disk is reported as Not enough disk space to update with the size the update needs; free that much space and check again. Any other failure means the update feed could not be reached, so check your connection and try again.