The Logitech G604 is my favorite mouse ever, so much so that before they were discontinued (RIP), I purchased two at the same time so I wouldn't have to change mice for years to come. Long story short, my original mouse is still going strong, but I finally opened up the second one to use at my company's office.
But this introduced an issue: my previous mouse was programmed using G HUB, Logitech's god-awful user configuration software. I did not want to download G HUB, cross my fingers and pray it played well with my Macbook.
So I did what we do in 2026. I asked Claude Grok to write a script to download my home mouse's memory profile so I can upload it directly to my office mouse.
What the agent actually did
G604s talk HID++ over a vendor interface on the Unifying/Lightspeed receiver (0x046d:0xc539). The agent used libhidapi, poked the Onboard Profiles feature (0x8100), and pulled device identity, profile directory, active profile, button tables, and macro sectors straight off the hardware.
What's really cool is that Grok actually just built a CLI tool, so I can run this again if (god forbid) I have to re-flash any of my mice again:
g604-onboard info
g604-onboard dump ~/.local/share/g604-profiles/home-office.json
g604-onboard apply ~/.local/share/g604-profiles/home-office.json
g604-onboard verify ~/.local/share/g604-profiles/home-office.json
I've uploaded this to a public Github gist here so you can use it if you'd like.
Why this is wild
Every day I get more AI-pilled. Your boy wouldn't have even attempted this. My time is valuable and I know just how far these rabbit holes can go. I would've cursed Logitech under my breath, and dutifully installed their malware software just to copy/paste some text over to my new mouse.
I didn't open any protocol analyzers, I didn't need to know what an HID++ draft was. Yet, with Grok, I could pose a simple question and have it:
- find the device on the bus
- decide the problem was onboard flash, not OS remaps
- implement a dump/apply against a vendor protocol
- debug a firmware validation rule that only reveals itself after reboot
- leave me a tool in
~/binand a profile JSON I can re-use
If you blinked between October 2025 and July 2026, you'll have missed that we very rapidly went from "AI that autocompletes a function" to "AI that can fix a messy hardware problem end to end."
I can't confirm (because I didn't do the work), but Grok tells me that the CRC detail is the kind of thing that used to mean an afternoon on GitHub issues and a half-working Python script you never commit. If my graveyard of Github projects is any indication, I'm inclined to agree.
Idk man, I think this new AI age is freakin' cool.