feat: let each keyboard shortcut be unassigned in Settings > Keyboard

[silentoplayz]

Summary

Settings > Keyboard lets me move any configurable shortcut to other keys, but not remove it. The only way to stop one shortcut from firing is the Enable Keyboard Shortcuts switch, which turns off every shortcut at once. I propose an x button beside each shortcut's keys that sets it to Unassigned, a state Settings > Keyboard already shows and already honors.

Problem / Motivation

1. Open Settings > Keyboard.
2. Click the keys shown next to Regenerate Response. The row reads Press keys....
3. Try to clear it. Escape cancels the recording, and any other key press becomes the new binding. Nothing sets the shortcut to Unassigned.
4. Scroll to Toggle Controls. It already reads Unassigned, because it ships without keys.

Two shortcuts show why a per-shortcut off switch matters:

• Regenerate Response is bound to Cmd+R / Ctrl+R, the keys a browser uses to reload the page. With the message box focused, which it is most of the time in an open chat, pressing them to reload regenerates the last reply instead. People describe losing replies to it in [UX] Ctrl+R deletes messages without confirmation, this shortcut is also used in browsers to refresh the page #12179 and Cmd+R triggers Regenerate instead of browser page refresh #23731, and ask for a way to turn it off in Conflict between the browser web refresh shortcut and the 'regenerate' shortcut #18437 and Cmd+R triggers Regenerate instead of browser page refresh #23731.
• Generate Message Pair is bound to Cmd+Shift+Enter / Ctrl+Shift+Enter. Pressing it adds the draft as a message plus a placeholder reply without asking the model, and empties the message box. Someone who never uses it can lose a draft to one wrong key press.

Today there are two options. I can rebind the shortcut to keys I hope never to press, which leaves a live binding that can collide with something later. Or I can turn off keyboard shortcuts entirely and lose the ones I use every day.

Proposed Solution

Add a small x button beside the keys of every assigned shortcut. Clicking it saves the shortcut as Unassigned. Clicking Unassigned afterward records new keys the same way it does today, and Reset Defaults keeps restoring every shortcut to its original keys.

Almost everything this needs already exists:

• An empty binding is skipped when Open WebUI matches a key press, so an unassigned shortcut never fires.
• Settings > Keyboard already renders an empty binding as Unassigned, and clicking it starts recording like any other row.
• An empty binding saves and loads like any other value, which is how Toggle Controls ships.

The change covers the shortcuts that already have a rebind button. Fixed keys, such as Escape to close a modal, stay as they are.

Files Likely Affected

• src/lib/components/chat/Settings/Shortcuts.svelte, the row that shows each shortcut's keys, next to the existing Unassigned state, at

  open-webui/src/lib/components/chat/Settings/Shortcuts.svelte

  Lines 214 to 238 in 420b4a2

  	<div class="flex w-[9.5rem] shrink-0 items-center justify-end gap-1">
  	{#if configurable}
  	{#if recordingShortcut === id}
  	<span
  	class="inline-flex min-h-[1.125rem] items-center rounded-full bg-gray-100 px-[0.4375rem] py-0.5 text-[0.625rem] font-medium leading-none text-gray-500 dark:bg-white/6 dark:text-gray-400"
  	>
  	{$i18n.t('Press keys...')}
  	</span>
  	{:else if chord}
  	<button
  	class="inline-flex min-h-[1.125rem] items-center rounded-full bg-gray-100 px-[0.4375rem] py-0.5 text-center text-[0.625rem] font-medium leading-none text-gray-500 dark:bg-white/6 dark:text-gray-400"
  	title={$i18n.t('Click to rebind')}
  	on:click={() => (recordingShortcut = id)}
  	>
  	{formatChord(chord)}
  	</button>
  	{:else}
  	<button
  	class="text-[0.625rem] text-gray-500 transition hover:text-gray-400 dark:text-gray-600"
  	on:click={() => (recordingShortcut = id)}
  	>
  	{$i18n.t('Unassigned')}
  	</button>
  	{/if}

  . Saving an empty binding can go through the same save the rebind already uses, at

  open-webui/src/lib/components/chat/Settings/Shortcuts.svelte

  Lines 68 to 71 in 420b4a2

  	const setBinding = async (id: Shortcut, chord: string) => {
  	if (!isConfigurableShortcut(id)) return;
  	await saveKeybindings({ ...$keybindings, [id]: chord });
  	};

• No change should be needed in src/lib/shortcuts.ts: the key matching already skips empty bindings at

  open-webui/src/lib/shortcuts.ts

  Lines 196 to 203 in 420b4a2

  	function buildReverseLookup(bindings: KeybindingsMap): Map<string, ConfigurableShortcut> {
  	const lookup = new Map<string, ConfigurableShortcut>();
  	for (const id of CONFIGURABLE_SHORTCUTS) {
  	const chord = bindings[id];
  	if (chord) lookup.set(chord, id);
  	}
  	return lookup;
  	}

  , and Toggle Controls already defaults to an empty binding at

  open-webui/src/lib/shortcuts.ts

  Line 97 in 420b4a2

  [Shortcut.TOGGLE_CONTROLS]: '',

Alternatives Considered

• Reserving a key, such as Backspace or Delete, to clear a shortcut while it records. Any key can be part of a shortcut, so reserving one to mean "unassign" takes it away from people who want to bind it. A key press is also harder to discover than a visible button.
• An on/off switch for each shortcut. It would remember the old keys for later, at the cost of a second control on every row. Reset Defaults already brings the original keys back.
• Changing the default keys for Regenerate Response. This would fix the reload conflict for new users, but not the next shortcut that collides with a browser, an operating system, or an extension on someone's machine.

Additional Context

Related: #29998 proposes moving Enter Key Behavior into Settings > Keyboard, and would put the send key in the same list. Code references above are pinned to commit 420b4a2.

[silentoplayz]

Opened as #33185.