Hi! I own two UHK v2 keyboards, one at home and one at the office, and would like to keep their keymaps and layers consistent.
When I change a keymap or layer at home, I would like to have that change available on my office keyboard without manually exporting and importing the configuration each time.
Desired behavior
An opt-in way to share a configuration between two UHKs through Agent. Ideally, Agent would detect changes made on the other computer and offer to apply them to the connected keyboard. A confirmation step would be perfectly fine for my use case; fully automatic application is not essential.
Possible approach
One option might be to let users choose a shared configuration file or folder, synced between computers using a service of their choice. Agent could export changes there and offer to import updates when needed.
This is only a suggestion, and I’m open to other approaches. Conflicting changes and accidental overwrites would need to be handled carefully.
Related discussion
I found #1851 , which discusses configuration backups to Google Drive. My main use case is keeping two keyboards consistent, rather than backing up configurations.
Is there an existing recommended workflow or a plan for this use case? If not, would you be open to considering a feature along these lines?
I’d be happy to work on an implementation and submit a PR if we can agree on the general direction and scope first.
Thanks for your work on UHK and Agent!
Hi! I own two UHK v2 keyboards, one at home and one at the office, and would like to keep their keymaps and layers consistent.
When I change a keymap or layer at home, I would like to have that change available on my office keyboard without manually exporting and importing the configuration each time.
Desired behavior
An opt-in way to share a configuration between two UHKs through Agent. Ideally, Agent would detect changes made on the other computer and offer to apply them to the connected keyboard. A confirmation step would be perfectly fine for my use case; fully automatic application is not essential.
Possible approach
One option might be to let users choose a shared configuration file or folder, synced between computers using a service of their choice. Agent could export changes there and offer to import updates when needed.
This is only a suggestion, and I’m open to other approaches. Conflicting changes and accidental overwrites would need to be handled carefully.
Related discussion
I found #1851 , which discusses configuration backups to Google Drive. My main use case is keeping two keyboards consistent, rather than backing up configurations.
Is there an existing recommended workflow or a plan for this use case? If not, would you be open to considering a feature along these lines?
I’d be happy to work on an implementation and submit a PR if we can agree on the general direction and scope first.
Thanks for your work on UHK and Agent!