Privacy
MouseHerdr has no telemetry. Remapping, window inspection and settings stay on your Mac.
The one thing it asks the network for is its own updates: a signed release checks GitHub for a new release daily and downloads it in the background, sends no profile of your Mac with the check, and stops when you turn automatic updates off in Settings. Source and ad-hoc builds do not auto-update.
With agent features enabled, it reads agent status, titles, questions and terminal text through the locally installed Herdr tools, and sends answers through those tools when you choose to reply. Herdr and your coding agents have their own network behavior.
To recognise a mouse, MouseHerdr reads what each connected pointing device reports about itself: its vendor and product ids, its name, how it is connected and how many buttons it declares. It opens none of them and sends nothing anywhere.
MouseHerdr does not read the keyboard, with one exception: while the agent wheel is showing, key presses pass through it so that it can tell when Escape is pressed and put the wheel away. It acts on no other key, keeps and logs none, and stops the moment the wheel closes.
Logs can contain application names, agent workspace/tab names, button events, local paths and the names of connected mice; a Bluetooth mouse’s name can include its owner’s. Typed answers are logged by character count, not their contents.
Settings are in ~/Library/Application Support/MouseHerdr: config.json holds the MX Master 4’s buttons, mice/ has a file for each other mouse, and mice.json remembers which mice have been met and what you picked for them. The log is at ~/Library/Logs/MouseHerdr.log.