OpenLogi

⚡️A native, local-first alternative to Logitech Options+, written in Rust 🦀, remap buttons, DPI, and SmartShift over HID++. No account, no telemetry.

Runs with mockssource: GitHubhomepageRustApache-2.0commit 7275072f58a1

Rust, Apache-2.0 licensed. The project labels itself: dpi, gpui, hid, hidpp, local first, logitech, logitech mouse and logitech options.

OpenLogi runs, with stand-ins for the services it depends on. An Argusic agent installed it in 13 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

OpenLogi 0.8.8 builds with all 13 library crates passing 1361 tests, the CLI binary runs and lists 4 mock devices via IPC from the mock agent, and the GPUI desktop GUI launches on a virtual X11 display (software-rendered via llvmpipe).

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.14 (measured)
recorded runs
1
last tested
stars
22,205
forks
729
open issues
607
watchers
83
size
17 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Install time
13 minutes
Cold machine to finish
33 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
cargo test on 13 crates: 1361 tests passed (0 failed). CLI 'openlogi --version' returned 0.8.8. Mock agent served 4 devices via IPC, CLI printed all. Desktop GUI launched on Xvfb (llvmpipe, window created, rendering started).
Model tokens used
590,806
Exact commit tested
7275072f58a1
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

Let me clean up the downloaded .deb files and prepare a final summary
2026-09-25T22:47:58.095824Z ERROR codex_core::tools::router: error=exec_command failed: CreateProce…
Let me build the agent binary too, to confirm everything:
exec
/bin/sh -lc '. "$HOME/.cargo/env" && cargo build -p openlogi-agent 2>&1 | tail -5' in /work/repo
 succeeded in 15920ms:
    Blocking waiting for file lock on build directory
   Compiling openlogi-agent v0.8.8 (/work/repo/crates/openlogi-agent)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 15.97s
2026-09-25T22:48:36.245995Z ERROR codex_core::session: failed to record rollout items: thread 01a0d…
tokens used
590,806

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Installed in 13 minutes.
  • Nothing broke on the way: zero errors between clone and running.
  • Licensed Apache-2.0, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.14

Topics (from GitHub)

dpigpuihidhidpplocal-firstlogitechlogitech-mouselogitech-optionsmouse-remappingmx-masterprivacyrustsmartshift

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/OpenLogi.svg)](https://argusic.com/subject/openlogi)

Questions

Does OpenLogi run?
OpenLogi runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 13 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test OpenLogi?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7275072f58a1. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test OpenLogi?
The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does OpenLogi take to install?
13 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does OpenLogi need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing OpenLogi?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for OpenLogi?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion