I built a native Logitech Options+ clone for Linux

Like many of you, I've been waiting for Logitech to bring Options+ to Linux. Got tired of waiting.

First off — massive respect to the Solaar and logiops teams. They paved the way by reverse-engineering HID++ and have been the backbone of Logitech support on Linux for years. I wouldn't have gotten anywhere without their work.

That said, after daily-driving both with my MX Master 3S, I kept running into the same frustrations:

Solaar is solid for monitoring and basic config, but there's no per-app profile switching — I couldn't get my DPI/buttons to automatically change when switching between Firefox and my terminal. The gesture button and thumb wheel modes are also pretty limited in what you can configure through the UI.

logid is powerful but runs as a system daemon that kept stepping on KDE's toes. Spent way too many hours debugging why my zoom and volume were fighting each other (spoiler: logid and Plasma were both grabbing the same button events). And editing YAML configs for every button combo gets old fast.

What I really wanted was just... Options+. On Linux. Click a button on the mouse, pick what it does, done. With profiles that switch when I alt-tab between apps.

So I built Logitune.

It's a Qt6 desktop app that talks directly to HID++ 2.0 over hidraw. No daemon sitting in the background, no config files — just a normal app with a tray icon.

The highlights: - Per-app profiles that switch automatically on window focus (KDE Plasma 6 + GNOME 42+ Wayland) - Visual config — clickable mouse render with hotspots, like Options+ - Gestures — hold + swipe for 5 actions per profile - Thumb wheel — horizontal scroll, zoom, or volume, per app - DPI, SmartShift, hi-res scroll — all the usual stuff - Bolt + Bluetooth with automatic failover between them - No daemon, no root — just a regular app

Right now it supports the MX Master 3S. The app has a modular design — each device is self-contained with its own descriptor, images, and button mappings. Adding support for a new mouse is straightforward if you have the hardware to test with. There's a step-by-step guide in the wiki if you want to contribute.

Install: - Arch: yay -S logitune - Ubuntu 24.04 / Fedora 42: OBS repo (one-liner in the README) - From source: cmake + Qt6

GitHub: https://github.com/mmaher88/logitune

Happy to answer questions — there's also a wiki with architecture docs and HID++ protocol deep-dives if you're curious how it all works under the hood.

PS: This is pretty new so expect some hiccups — please post issues on GitHub with logs attached.

Edit (April 10):

Wow I really didn't expect this to blow up!

What's new since the post: Bluetooth-direct connection bug is fixed (MX3S over BT should work now without going through a receiver). MX Master 4 support is in PR, MX Master 2S is next, both thanks to Jelcoo on GitHub who has
been doing serious work on them.

A few points I came across through the comments that I would like to clarify:

1. Why did I create this?

Honestly, other than the reasons stated in the original post, I just had some free time for the first time in years and I recently decided that I don't want to go back to Windows no matter how annoying a missing feature on Linux is, and instead I will try and fix it myself. This is just one nagging issue that I always had.

I also wanted to prove that Linux can be user friendly and target a broader audience.

2. Why did I post about it?

To attract more talented developers who happen to use Logitech peripherals and have the same frustrations I did, to come in and contribute.

3. How long will this project stay alive?

Probably for as long as I use Logitech peripherals that I want to function properly under Linux.

But more importantly, the whole point of open source is for good ideas to bring people together, and when that happens the project becomes bigger than any one person and hopefully outlives their interest. I am doing my best to make the architecture as modular as possible and for new additions and contributions to be straightforward.

4. On the use of Claude/AI:

In hindsight I should have been upfront about the AI use in the original post, that one's on me.

Now with that out of the way, to answer a question a lot of you have been asking: is this vibe coded?

Short answer: No.

Long answer: there is no amount of prompting that can make you produce something extensible and modular if you don't know what you are doing, so I guess the only proof one would need is to go through the code, judge the architecture, and maybe add something.

5. On the name:

Several of you flagged the conflict with Logitech's "Logi Tune". I'm considering a rename, suggestions welcome.