keybind-find reads the shortcuts you actually configured, then runs the one you pick
Benjmhart’s Linux utility combines configuration readers with app-specific sheets; desktop permissions determine whether a search result can actually be executed.

The shortcut exists. Your memory of it has apparently been garbage-collected. keybind-find opens a searchable list built around the app you are using, including supported custom bindings. Benjmhart’s project makes remembering the command’s name useful even when the key combination has escaped.
The README describes reading real configurations rather than asking you to maintain a second cheat sheet. That includes several different kinds of truth: sway’s binding lines, Hyprland’s running compositor, tmux’s running server and editor maps. A printed guide can tell you the factory shortcut. It cannot know about the remap you made six months ago because two applications both wanted the same keys.
Those readers have different limitations. KDE’s saved shortcut file supplies bindings that have actually been written there; the tool does not query the running global-shortcut service for the rest. Some applications contribute built-in defaults merged with user changes. “Live” therefore depends on which program is being read, and on whether its current configuration can be reached.
The action picker doubles as a way to learn. On X11, its key-search mode narrows the list as you press the beginning of a binding. Escape changes to text filtering. You can finish a half-remembered sequence or search for the action in words, then see the shortcut you could have used. The README describes the result as a “command palette,” which is a fairly humane way to deal with a keyboard that has become a filing cabinet.
The compatibility table deserves the click before installation. KDE Plasma on Wayland can identify the focused window with kdotool but cannot send the selected keys. GNOME on Wayland cannot identify that window through the supported path, also cannot send picks, and opens its list in fzf. The README traces the sending limitation to the virtual-keyboard protocol the compositors do not offer. The list can still help, but you press the reported keys yourself.
For applications without a configuration reader, the sheets documentation provides a manual route. A sheet matches the window class; a web-app sheet can further match text in the window title. Included browser sheets cover Gmail, YouTube and GitHub. Gmail still requires keyboard shortcuts enabled in its own settings. The utility cannot make a disabled application feature accept a shortcut by writing its name on a helpful list.
The ranking documentation says sent selections accumulate in a local usage log and frequently picked bindings rise to the top. Other results alternate among providers so one window manager cannot monopolize the first screen. That gives the combined list some restraint as the supported applications multiply.
Shell discovery carries a less obvious cost: opening the list starts an interactive shell, so its startup files run again. The README gives that process three seconds and provides KEYBIND_FIND=1 for skipping slow or noisy startup work. A shortcut finder could become annoying very quickly if looking for “help” also restarted half your development environment. The next compatibility question is whether the configuration you want to discover can be read without waking everything attached to it.