OpenLogi

Installation

Install OpenLogi v0.8.15 on macOS, Linux, or Windows, then grant the access it needs.

OpenLogi supports macOS 13 or later, Linux, and Windows. Choose one installation method for your platform, then complete the platform-specific access steps.

Quit Logi Options+ before installing or launching OpenLogi

The two applications fight over HID++ access and only one can own a receiver at a time. On Linux, the same applies to Solaar.

macOS

macOS requires version 13 or later. The release DMG is signed and notarized.

Install the official Homebrew cask:

brew install --cask openlogi

To follow the latest GitHub release from the OpenLogi tap instead, install:

brew tap aprilnea/tap
brew install --cask aprilnea/tap/openlogi@latest

Install either openlogi or openlogi@latest, not both.

Download the signed, notarized DMG from the latest release. Open it and drag OpenLogi.app to /Applications.

Launch OpenLogi after installation and follow its permission prompts. Give OpenLogi Agent Accessibility and Input Monitoring; Accessibility enables gesture and button remapping, while Input Monitoring reads HID++ data, including Bluetooth-direct mice.

Grant Camera only if you want to preview a Logitech webcam. That permission belongs to the OpenLogi app, not the agent, and is separate from HID and input access.

Linux

Release packages are available as .deb, .rpm, and .pkg.tar.zst for x86_64/amd64 and arm64/aarch64. Pre-built packages require GLIBC 2.35 or later, with Ubuntu 22.04 as the baseline.

Verified release installer

Install minisign with your distribution package manager. Download the installer over HTTPS and inspect it. Run it as a normal user. Do not pipe it into a shell or run the whole script with sudo.

curl --proto '=https' --proto-redir '=https' --tlsv1.2 \
  --fail --location --silent --show-error \
  --retry 3 --retry-connrefused \
  --output openlogi-install.sh \
  https://raw.githubusercontent.com/AprilNEA/OpenLogi/master/packaging/linux/install.sh
less openlogi-install.sh
sh openlogi-install.sh
rm openlogi-install.sh

The installer selects the latest release by default. It detects the architecture and apt, dnf, yum, zypper, rpm, or pacman. It verifies the detached minisign signature and exact SHA256SUMS entry before it invokes the package manager with sudo.

OptionEffect
--version 0.8.15Install a fixed release. The installer also accepts a leading v.
--package-manager zypperOverride package-manager detection.
--no-startInstall the package without enabling or starting the user agent.
--dry-runDownload and verify the package without installing or starting the agent.

When systemd is available, the installer enables and starts openlogi-agent.service for the current user. A failed user-service start does not roll back a successful package installation.

Manual package installation

Download the matching package from the latest release, then use the matching package manager:

# Debian / Ubuntu
sudo dpkg -i openlogi-*.deb

# Fedora / RHEL
sudo rpm -i openlogi-*.rpm

# Arch Linux
sudo pacman -U openlogi-*.pkg.tar.zst

After a manual package installation, enable the agent for your user:

systemctl --user enable --now openlogi-agent.service

The release packages install udev rules. The rules grant write access to /dev/uinput, read/write access to /dev/hidraw*, and read access to the Logitech mouse /dev/input/event* node without sudo.

If access stays denied after installing rules, unplug and reconnect the receiver or mouse. The GUI's Settings → Permissions page shows the live access state.

Flatpak bundle

Each release includes a Flatpak bundle for amd64 and arm64:

flatpak install --user ./openlogi-*.flatpak

A bundle has no remote, so flatpak update has nothing to check. Download the next bundle when a new version is released.

A Flatpak cannot write host udev rules. Install the bundled rule on the host before OpenLogi can detect devices:

flatpak run --command=cat org.openlogi.OpenLogi \
  /app/share/openlogi/udev/70-openlogi.rules | \
  sudo tee /etc/udev/rules.d/70-openlogi.rules >/dev/null

sudo udevadm control --reload-rules
sudo udevadm trigger

Restart the Flatpak after granting access:

flatpak kill org.openlogi.OpenLogi

The Flatpak launches its own agent, so it has no user service to enable. Its udev rule creates /dev/uinput at boot and loads the module when OpenLogi opens the node.

NixOS

Use the repository NixOS module instead of only adding the package. The module installs OpenLogi and its udev rules, and starts the agent with the graphical session by default.

{
  inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
  inputs.openlogi = {
    url = "github:AprilNEA/OpenLogi";
    inputs.nixpkgs.follows = "nixpkgs";
  };

  outputs = { nixpkgs, openlogi, ... }: {
    nixosConfigurations.my-host = nixpkgs.lib.nixosSystem {
      system = "x86_64-linux"; # or aarch64-linux
      modules = [
        openlogi.nixosModules.default
        {
          programs.openlogi = {
            enable = true;
            launchAtLogin = true;
          };
        }
      ];
    };
  };
}

Set programs.openlogi.launchAtLogin = false to install the package and rules without starting the agent at login. You can then start it with systemctl --user start openlogi-agent.service.

Other Linux systems

For a source build, use the stable Rust toolchain. Build the four production binaries. Then run the source installer from the repository checkout as a normal user:

cargo build --release \
  -p openlogi -p openlogi-desktop -p openlogi-overlay -p openlogi-agent
packaging/linux/install.sh --from-source

Use --prefix=/usr with --from-source only when you need a different binary prefix. On SysV init or OpenRC, replace TAG+="uaccess" in the bundled udev rule with MODE="0660", GROUP="input", add the user to input, and sign in again:

sudo usermod -aG input "$USER"

On Wayland, automatic per-application profile switching requires XWayland. In Hyprland or Omarchy, native actions require HYPRLAND_INSTANCE_SIGNATURE and XDG_RUNTIME_DIR in the systemd user-manager environment.

Windows

Each release includes signed per-user .msi installers and portable .zip archives for x86_64 and arm64. The MSI installs under the current user's local application folder and does not require elevation.

Both formats place OpenLogi.exe and openlogi-agent.exe together. Keep those files side by side when you use the portable ZIP, because the GUI connects to the background agent for device I/O.

The agent shows a notification-area icon after the main window closes. Hide it by turning off Settings → General → Show in the notification area, then restart the agent, or set show_in_menu_bar = false in [app_settings] and restart the agent.

Updating

macOS. Release app bundles use Sparkle for updates, a path added in v0.8.14. Use Settings → Updates to check, download, and install; Homebrew installations update through brew upgrade.

Linux. Update a release package with the package manager that installed it. For Flatpak, download and install the next bundle because flatpak update has no remote to query.

Windows. The MSI supports in-app updates through Settings → Updates. Choose Download & Install, then restart OpenLogi when the update is ready.

Installation source

Settings → Updates → Installation source identifies the running copy as a Homebrew cask, Linux package, Nix install, Windows MSI, portable ZIP, or macOS app bundle. It shows Not identified when OpenLogi has no ownership evidence for the running copy; the read-only result does not change update behavior.

Uninstall

For a Linux release package, remove OpenLogi through the same package manager that installed it. For a Linux source installation made with --from-source, run the removal script from the checkout; pass the same custom prefix when applicable:

packaging/linux/uninstall.sh
# Or, if the source installation used a custom prefix:
packaging/linux/uninstall.sh --prefix=/usr

Next steps

Connect a device after OpenLogi starts. If installation or access does not work as expected, see Troubleshooting.

On this page