Use Cmd+K for the command palette and selected-text links

[bholmesdev]

What should change?

Move the global command palette shortcut from Cmd/Ctrl+P to Cmd/Ctrl+K.

Cmd/Ctrl+P makes Hubble feel like a code editor. Cmd/Ctrl+K better matches user expectations for a text-focused app and its command palette.

Hyperlink behavior

Cmd/Ctrl+K needs context-sensitive behavior inside the rich-text editor, matching Notion:

• With a non-empty text selection, open/focus the hyperlink UI for that selection.
• With no text selected, open the global palette.

Today, pressing Cmd/Ctrl+K with an empty editor selection starts hyperlink creation. Remove that behavior and the code/UI state used only by the empty-selection shortcut flow. Existing-link editing should continue to work.

Acceptance criteria

• Cmd/Ctrl+K opens the global palette when focus is outside the editor.
• Cmd/Ctrl+K opens the global palette when the editor selection is empty.
• Cmd/Ctrl+K opens/focuses hyperlink controls when editor text is selected, without opening the palette.
• The empty-selection Cmd/Ctrl+K hyperlink-creation behavior and shortcut-only supporting code are removed.
• Cmd/Ctrl+P no longer opens the global palette.
• Menu accelerators, shortcut hints, tests, and user-facing copy reflect the new binding.

Context

Follow-up to #208 and its implementation in #209.

[github-actions]

Triage: Needs discussion. The intent (palette on Cmd/Ctrl+K, links only with a selection) is clear, but how Cmd+K gets arbitrated — and what "remove the empty-selection flow" actually covers — conflict with how the code is wired today, so an implementer would have to guess on several load-bearing decisions.

Evidence:

• Two commands would own CmdOrCtrl+K. app.go-to-file is CmdOrCtrl+P and editor.link is already CmdOrCtrl+K (packages/editor/src/commandRegistry.ts:50, :121), and packages/editor/src/commandRegistry.test.ts:9 asserts every command owns a unique binding. Selection-sensitive dispatch also isn't expressible today: CommandContext has no selection field, editor.link dispatches via the TipTap keymap (packages/ui/src/editor/EditorCommandShortcuts.ts:38) while app.go-to-file dispatches from the window keydown loop (apps/desktop/src/App.tsx:372-385).
• The native File-menu accelerator fires regardless of focus. commandMenuItem("app.go-to-file", …) registers the accelerator in the Electron menu (apps/desktop/electron/main.ts:835, :805), and App.tsx:359 notes both paths fire and is safe only because "opening is idempotent". At Cmd+K that stops being safe: with text selected the menu accelerator would still open the palette, defeating AC 3.
• The empty-selection supporting code is not shortcut-only. LINK_CREATION_REQUESTED_EVENT → creating mode, ghost text, and wiki suggestions (packages/ui/src/editor/LinkPopover.tsx:976, LinkCreationGhostExtension.ts) are also driven by typing [[ (packages/ui/src/editor/SmartLinkExtension.ts:78-82). Only the empty-selection branch at SmartLinkExtension.ts:26-33 is specific to the command; deleting creation mode would break [[ wiki-link insertion.
• The same command backs the Format menu and selection toolbar. applyFormatCommand("link") calls toggleLinkAtSelection (packages/ui/src/editor/formatCommands.ts:109) and FormatCommandMenu.tsx:164 renders the editor.link shortcut, so removing the empty-selection branch silently changes what Cmd+/ → Link does with a collapsed caret.
• AC 2 conflicts with "existing-link editing should continue to work". A caret inside an existing link is an empty selection, and Cmd+K there currently toggles the link actions popover (LinkPopover.tsx:1218).

Open decisions before this is ready:

• How is Cmd+K arbitrated — shared registry binding with documented precedence, a contextual binding on one command, or renderer-only dispatch? Does the unique-binding invariant change, and how does that interact with Add customizable shortcuts for existing Hubble commands #189 / Add Shortcuts tab to Settings #194?
• What happens to the File-menu accelerator: dropped, registerAccelerator: false with renderer dispatch, or set dynamically?
• Caret inside an existing link with no selection: open the palette, or keep toggling link actions?
• Does [[ creation mode stay? If yes, is the removal scoped to just SmartLinkExtension.ts:26-33?
• With a collapsed caret, what should Format menu / toolbar Link do — no-op, keep the creation flow, or something else?
• Does moving the palette to Cmd+K supersede Command palette: add a command mode to the global palette #208 / Prototype: command mode for the global palette #209's ⌘⇧P command-mode plan?

---

Triaged by a Warp Factory agent.

---

Triaged by a Warp Factory agent.