Logi Options+ mini: an unofficial trimmed installer for Logitech's Options+

What the project changes, and what it explicitly does not

Logi Options+ mini provides a way to choose a customised Logi Options+, so that users can better control its features.

The scope is narrow and worth being precise about. This is not a replacement for the Logitech application, and it is not a fork of it. It is a way to install the official application with a subset of its features present. The project description says so directly, that the project customises Logi Options+ functionality through the official installer's command line options, and it references Logitech's own documentation on bulk installation and configuration of the Options+ software as the model.

That last point is the whole design. Logitech already documents a command line driven install for their own deployment tooling, and this project reuses those switches so that a home user can get a trimmed install without a device management console.

The features that can be toggled are named in the README: analytics, which shows or hides the choice for users to opt in to share app usage and diagnostics data, flow, sso for the ability for users to sign into the app, update for app updates, dfu for device firmware updates, logivoice for the Logitech voice feature, aipromptbuilder for the AI Prompt Builder feature, smartactions, actions-ring and device-recommendation, which is macOS only. The list also includes backlight, which enables or disables the keyboard backlight on supported keyboards.

Two things follow from the mechanism. The first is that the trimming happens at install time, so the choices are baked into the installed application rather than applied to a running one. The second is that the tool's behaviour is bounded by what Logitech's installer supports, which is why the menu is a list of switches rather than an arbitrary set of toggles.

The project carries a disclaimer that is worth quoting because it defines the whole posture: this project is an unofficial third-party tool with no affiliation whatsoever with Logitech, and Logi, Logitech and Options+ are trademarks of Logitech. The licence is the Apache licence, with the LICENSE file at the repository root. The primary language is Swift, the default branch is `main`, and the last push was on 2026-09-07, with recent releases v2.1.0 from 2026-09-05, v2.0.0 from 2026-08-07 and v1.9.0 from 2026-07-18.

Two native apps and two scripts, plus auto-update feeds

The repository is unusual in how it presents the same product four ways, and the table in the README makes the split explicit.

`Logi Options Plus Mini/` is the macOS native application, a SwiftUI and Xcode project that includes a GUI installer, configuration backup, permission detection and a background agent. `Logi Options Plus Mini For Windows/` is the Windows native application, built with Tauri 2, React and Rust, with the features aligned to the macOS version. Then there are the two scripts, `logi-options-plus-mini.command` for macOS and `logi-options-plus-mini.ps1` for Windows.

And then the two update feeds, `appcast.xml` as the macOS Sparkle automatic update source and `latest.json` as the Windows Tauri automatic update source. That is a detail that tells you the project is a distributed product rather than a script collection: the native apps update themselves, through the standard mechanism for each platform, and the release artefacts are the mechanism that feeds them.

The choice of technology stack for the Windows app is worth a sentence. Tauri 2 gives a native webview window rather than a bundled browser runtime, and pairing it with React and Rust means the Windows installer and the macOS app can present the same interface while the shared logic lives in Rust. The primary language recorded for the repository is Swift, which reflects the macOS app being the original implementation and the Windows one the port.

For a user, the practical difference is where the controls live. The scripts ask you a question in a terminal and then do the work silently, while the apps present a graphical selection and handle the install, the backup and the permission checks for you. The README also lists among the features that configurations are automatically preserved on uninstall and upgrade, and that an offline version of Logi Options+ can be installed.

The feature menu, and the difference between the two scripts

The script path is where the mechanism becomes visible, because the script prints the list of switches it is going to use and then asks you to choose.

On macOS the menu runs from analytics through device-recommendation, with an `all` option and a prompt to press enter for none:

Enter your choices(e.g. 2 6, default is none):

The Windows PowerShell script presents the same idea with a different order, and the difference is instructive rather than accidental. The macOS list has device-recommendation at position 8 and smartactions and actions-ring after it, while the Windows list has aipromptbuilder at position 8 and pushes device-recommendation down to position 9, and the two lists have different numbering for the same features.

The reason for aipromptbuilder appearing on one list and not the other is stated in the feature list: the AI Prompt Builder feature is no longer supported as of Logi Options+ 2.7.961922. The Windows installer still offers the switch, while the macOS one has dropped it from the menu, which suggests the two scripts track the current installer flags at different rates.

The prompt format itself is worth noting, because it explains the whole interaction model. You type the numbers of the features you want to keep, separated by spaces, for example `2 6`, and the default is none. The `all` option keeps everything, which is how you would use the tool purely as an installer.

So the semantics are: a number in your list means keep that feature, and the features you do not name are the ones that get removed. That is a reasonable default for the audience, since a user who wants to keep everything does not need the tool, and a user who wants a minimal install names the two or three things they actually use.

Running the shell and PowerShell installers

The script route is a clone and a run, and the macOS sequence in the README is explicit about the privileges involved.

git clone https://github.com/Qetesh/logi-options-plus-mini.git
cd logi-options-plus-mini

chmod u+x logi-options-plus-mini.command
./logi-options-plus-mini.command

The script needs `sudo` permission to uninstall the old version, and the output shows what happens: a banner with a timestamp and the message Starting install of Logi Options+, then the download of the official installer, then the uninstall of the existing version, then the feature menu. The Windows script's output is the same sequence with the same steps, Downloading Logi Options+ Installer, Download completed successfully, Uninstalling existing version of Logi Options+.

On Windows there is one extra step, and it is the kind of thing that stops a user cold. The PowerShell script needs to be run once in an administrator terminal with `Set-ExecutionPolicy -ExecutionPolicy RemoteSigned`, and the README links issue 5 for the details. After that you right-click the ps1 file and choose to run it with PowerShell.

The stated system requirements are short: macOS, Windows, and a network connection to download the official installer. That last requirement is the one that matters in a locked down environment, because the script downloads the vendor installer every time it runs.

There is one FAQ entry worth repeating, since it is the failure people hit. Some Macs cannot uninstall using the official method, and the project says you need to uninstall with a third-party tool and then run it again, having tested that uninstalling with Pearcleaner makes the subsequent install work.

The alternative to the scripts is the native apps, downloaded from GitHub Releases, with the macOS app handling the GUI install, the configuration backup and the permission detection, and the Windows app offering the same feature set.

Building from source on both platforms

The build instructions differ as much as the toolchains do, and the README keeps them separate for that reason.

On macOS you open the Xcode project `Logi Options Plus Mini/Logi Options+ mini.xcodeproj` in Xcode, set your Development Team in the Signing configuration, and build. There is no command line build described for the macOS app, which is a deliberate choice for a project whose macOS deliverable is a signed and notarised app that has to pass macOS Gatekeeper.

On Windows you change into the `Logi Options Plus Mini For Windows/` directory and run:

pnpm install && pnpm tauri dev

for development, and `pnpm tauri build` for a release build, with the README in that directory holding the details. The Tauri CLI is doing the work here, bundling the Rust backend and the React front end into a single installer.

The two build paths also tell you something about the shape of the project. The macOS side inherits Apple's model, where a signed and notarised app is distributed and updated through Sparkle, and the `appcast.xml` file is the feed that makes that work. The Windows side uses Tauri's own updater with `latest.json` as the manifest, and Windows installers are distributed the same way for both platforms, from GitHub Releases.

The contribution guide in the README is a conventional fork workflow: fork the repository, create your branch with `git checkout -b feature/AmazingFeature`, commit with `git commit -m 'Add some AmazingFeature'`, push the branch with `git push origin feature/AmazingFeature`, and open a pull request.

Where this is the wrong tool

There are three cases where Logi Options+ mini does not help, and the first is the most common.

The first is if you want to change Options+ behaviour after installing it. The mechanism is a trimmed install driven by the official installer's command line options, so the feature set is chosen at install time and baked into the installed application. If you want to toggle LogiVoice on later, or you want a feature that is not on the menu, you reinstall. There is no configuration switch in the running app.

The second is if any of the removable features are ones you use. The menu includes Flow, which is Logitech's cross-device workflow feature, Smart Actions and Actions Ring, which are the mouse gesture and ring features, and the sign-in capability. Disabling them removes functionality rather than a setting, and the tool's menu is the only place the choice is made, so the decision is a one-time installation decision rather than a preference you can revisit in the app.

The third is any platform or environment the scripts do not cover. The requirements are macOS and Windows, and a network connection to reach the vendor's installer. A Linux user with a Logitech keyboard and a preference for not running Logitech's software has no path here, and an air-gapped or heavily proxied machine cannot complete the download.

There is also a question that sits above the technical one. The project is explicit that it is unofficial and has no affiliation with Logitech, and it automates the vendor's own installer with the vendor's own documented switches. That is a narrow and defensible position, and it is different from patching the application or redistributing its code. It is still worth checking that your organisation is comfortable with a third-party tool scripting a vendor installer, particularly on a machine that handles sensitive input, since the installation replaces the existing application.

The alternative approach, and the one to weigh it against, is to install the official Options+ yourself and turn off the settings you do not want from inside the application, which covers the analytics opt-in, the sign-in and the update preferences, but not the features that only exist as installer switches. The difference in approach is that the official route leaves the vendor's full feature set installed and hides some of it, while this project removes it, and the second is what the project is for.

Editorial conclusion

Adopt Logi Options+ mini if you run Logitech Options+ on macOS or Windows and want to strip out the parts you do not use, such as analytics opt-in, Flow, LogiVoice and device recommendations, while keeping the device customisation you actually rely on, since the project drives the official installer's own switches rather than patching the application. Do not adopt it if you rely on any feature the menu offers to disable, if you are on a Linux system, or if your organisation does not permit third-party installers to fetch and reinstall vendor software. Verify three things first: that the feature you care about is on the menu, since the list differs slightly between the macOS and Windows scripts, that the installer can reach Logitech's servers, because the download is part of every run, and that your existing Options+ configuration survives, since the project claims to preserve it across upgrades but the mechanism is a reinstall rather than an in-place edit.

Frequently asked questions

Official sources

1. Issues
2. License: Apache-2.0
3. Qetesh/logi-options-plus-mini on GitHub
4. README
5. Releases