Skip to content

Discontinuing GitHub Integration

Nick Coutsos edited this page Oct 29, 2026 · 1 revision

TL;DR

You may have noticed that I've stopped making feature updates to the Keymap Editor and I haven't been as responsive to feature requests on the GitHub repo.

I don't want to keep maintaining this.

More Details

I'm going to try to keep my personal feelings to a minimum but broadly speaking the software industry has changed a hell of a lot over the last few years and even where that hasn't placed constraints on my available time it has impacted the enjoyment I get out of building this.

The project stagnating for so long means it hasn't been keeping up with any of the other alternatives (I must admit, I haven't been following the ZMK comunity and don't know what all of those alternatives would be). I imagine that when ZMK Studio made runtime keymap updates possible a lot of users will have made the switch.

I've been fine with leaving things be and was reluctant to post "It's over" or some other kind of finality, but its past due.

The main thing is the security of managing the GitHub integration and the overhead of hosting the API server. I want to wind these down and let the static app continue indefinitely as long as its useful.

The Plan

I don't have a firm timeline, but maybe I'll shut down the server at the end of this year.

Your ability to edit keymaps

As mentioned before, the app itself will still work using the Clipboard source integration and copying changes out of the app and into your git repo if you still want to build using GitHub actions. (Chromium users can use the FileSystem source integration to read/write keymap files directly to your system).


I may add some more detail here later to guide people through adding their current keymaps via the Clipboard source, and copying changes back.

Clone this wiki locally