[Feature] Custom mapping for shortcuts

[DoS007]

What's happening?

Feature: Allow to remap shortcuts/ change keybindings? E.g. if new chat doesn't work because of browser to set it to another shortcut (because it's useful)?

@DoS007 that will take some work :) you can open a new ticket for that, but I'm gonna tell you right away that I'll spend that time for agentic, MCP, local app, and higher priority requests. I agree with the need tho!

see #883

Where does this happen?

Self-deployed from GitHub

Impact on your workflow

Low - Minor inconvenience

Environment (if applicable)

No response

Additional context

No response

[github-actions]

Thanks for filing this, @DoS007.

Assessment

This is a valid feature request and a duplicate of #895 (also open). The core ask across #883, #895, and this issue is the same: let users remap keyboard shortcuts — especially the Enter/Ctrl+Enter send behavior, which conflicts with muscle memory from other chat apps.

Current State

The shortcut system is already well-centralized and suitable for extension:

• Core logic: src/common/components/shortcuts/ — global handler, Zustand store, group-based registration
• ~20 shortcuts defined across 9 component groups, all flowing through a single globalShortcutsHandler.ts
• Read-only UI: ShortcutsModal.tsx already displays all active shortcuts with platform-aware symbols
• Static catalog: shortcutsCatalog.ts documents all bindings

The architecture makes remapping feasible without major refactoring.

What an implementation would look like

1. Override store — new store-shortcut-overrides.ts (Zustand + localStorage persistence) mapping shortcut IDs → user-defined key combos
2. Apply overrides in handler — _handleGlobalShortcutKeyDown checks user overrides before registered defaults
3. Remapping UI — extend ShortcutsModal.tsx from read-only display to click-to-rebind with conflict detection
4. Composer Enter handling — the handleTextareaKeyDown in Composer.tsx is a special case (not part of the global system) and would need separate integration

Duplicates / Related

• keybind configuration #895 — same request (open), likely should be consolidated
• Custom Shortcuts #883 — original discussion (closed), referenced by this issue
• Use CTRL+NUMBER (1, 2, 3 , etc) to choose AI Model in current conversation. #952 — Ctrl+Number for model switching (related but distinct)

This is a medium-scope feature. The existing centralized architecture makes it tractable, but the Composer's Enter key handling adds a wrinkle since it lives outside the global shortcut system.

[enricoros]

Good feature for sure - (and request #1000 !) cannot work on it right now, but legit and should stay open until we pick up the slack.