dsh-hotkeys-platform

In the DSH plugin ecosystem, each plugin tends to intercept keyboard events on its own and maintain a separate set of hotkey settings, leaving users with a scattered, hard-to-overview configuration landscape. dsh-hotkeys-platform consolidates this into a single registry service, ctx.hotkeys: a plugin simply calls registerAction to declare its action, default key, and trigger scope, while the platform handles unified persistence of user overrides and exposes a centralized settings page (DSH Settings > Hotkeys) or the /hotkeys command.

Five built-in trigger scopes-global, input, question-card, command-palette, and custom-cover everything from global shortcuts to keypresses inside specific components. Two configuration paths are provided: a visual combo-key editor and keyboard recording. Keys follow a three-state model: untouched (falls back to the declared default), recorded (uses the user's binding), or disabled (suppressed entirely). When two actions claim the same combo, the settings page highlights the conflict in red and the earlier-registered action wins.

Whether you are building a DSH plugin that needs key bindings or a DSH user who wants to see and manage every plugin shortcut in one place, this platform is the unified infrastructure you get by adding 'hotkeys' to your inject array.