Not sure yet how it handles apps that render their menus non-natively - Electron apps with custom menu implementations being the usual case. That's where most "read the system menu" tools quietly show an empty panel instead of the real shortcuts. Would be good to see that called out explicitly on the product page, either as supported or as a known gap, rather than finding out by trial and error per app.
I love that it shows conflicting shortcuts too! Does it work across most common apps?
@ryanwrites
Thanks! Yes — conflicts are checked against each app's actual menus plus your own remaps, so it works across any Mac app, common or obscure.
@charlie_titherley
Exactly right, good guess! Keymap reads shortcuts live from each app's own menu bar via macOS's Accessibility API — there's no hand-built database, and no per-app support was added. That's why it works out of the box with anything: Safari, VS Code, Figma, or a random app you downloaded today. Nice side effect: when an app updates its menus, Keymap always reflects the current shortcuts. (The flip side of that platform approach: shortcuts apps don't expose in their menus — like global hotkeys or IME bindings — aren't visible to any app, so those stay out of scope.)