Quick Launch Modal (part 3)
The third part of the Quick Launch page, for readers working in the codebase: how the floating window is managed, how its global and per-tab hotkeys register, how each tab maps to a component, the voice-suppression seam that keeps main-window voice commands dormant, and the design decisions behind the modal.
On this page
What it is
This is part 3 of the Quick Launch Modal page. The main page covers what Quick Launch is, how to open it, how to compose and send, and its settings; part 2 covers every other tab and the mobile sheet. This half is the implementation view: how the window, the hotkeys and the tabs are built, and why they are built that way.
Where to find it
There is no separate UI surface here — this half is for someone working in the codebase. Everything it describes is reached at runtime through the same floating window and the same Settings → Quick Launch page the other two pages cover.
How it behaves
What a reader can observe of the choices below: the modal pops up over whatever is on screen but never covers an exclusive-fullscreen game or video player, it hides rather than closes so an unsent draft survives, and its window is frameless and cannot be moved or resized.
Related
part 2 is the tab surfaces these components render, and the main page is the user-facing half. The contracts named above hold the invariants behind each piece, and keyboard-shortcuts.md is the global shortcut catalog Quick Launch registers into.
Last verified 2026-09-26