Unsigned prereleases

Two archives. Take the first one

Every release publishes a user bundle and a devtools bundle per platform, plus a SHA256SUMS file. Unless you are diagnosing hardware or measuring resource usage, you want the user bundle and nothing else.

Version 0.1.0 · All releases and changelogs

Windows

Windows 10 or 11, x86_64

macOS

Apple Silicon only - Intel is unsupported

User bundle

gflick-0.1.0-windows-x86_64.zip
gflick-0.1.0-macos-aarch64.tar.gz

gflick-setup, the installer and maintenance tool
gflick-agent, the device owner and IPC server
gflick-tray, the status client
gflick, the scriptable IPC CLI

This is the one to download. It never opens HID directly except through the agent.

Development and hardware diagnosis

Devtools bundle

gflick-devtools-0.1.0-windows-x86_64.zip
gflick-devtools-0.1.0-macos-aarch64.tar.gz

gflick-probe, the direct-HID diagnostic CLI
gflick-bench, the resource-usage recorder

Probe talks to HID directly and must not run while the agent is running - they compete for the same interface.

Platform requirements

Intel macOS is outside the support and test matrix, so the installer refuses it rather than installing something that would fail later.

Supported platforms
Platform	Target	Status
Windows	Windows 10 or 11, x86-64	Supported
macOS	Apple Silicon (aarch64)	Supported
macOS	Intel (x86-64)	Rejected by the installer
Linux	Any	Not built

Or build it yourself

Building from source avoids the unsigned-binary warnings entirely. It needs Rust stable - the workspace declares 1.85 as its minimum - plus Visual Studio Build Tools with Desktop development with C++ and a Windows SDK, or the Xcode Command Line Tools on macOS.

Clone

git clone https://github.com/R4ULtv/gflick

Build

cargo build --release --workspace

Run the agent

cargo run -p gflick-agent

Verify before you extract

Nothing published here is code-signed or notarised, so Windows SmartScreen and macOS Gatekeeper will both warn about an unidentified developer. That warning is expected, which is exactly why the hash check matters: download SHA256SUMS alongside the archive and compare the two before extracting anything.

The per-platform verification command is on the card for your platform above, and the step-by-step install flow is on the setup page.

What you get after installing

The default install registers the agent and the tray. The agent discovers devices, keeps each mouse session owned by one thread, refreshes battery state, persists your preferences, and serves protocol version 1 over an OS-local socket. The tray subscribes to those events and sleeps between changes rather than polling.

A graphical settings application is the intended primary interface and is not shipping yet. Until it does, control happens through the gflick CLI. Component selection, installed paths, and uninstall behaviour are covered in the setup README .