The first time I hit ⌘K in Linear and got exactly what I wanted on the first try, something clicked. This isn’t a search box. It’s not a menu. It’s a third primitive, the same level of UI furniture as the URL bar and the menu bar.
Why it matters
A keyboard-driven, fuzzy-searchable, command-runnable surface collapses three different UI patterns into one:
- Navigation (where can I go?)
- Search (what is here?)
- Action (what can I do?)
When all three live in the same input, users stop context-switching between mouse and keyboard.
What “feels instant” means
Try the demo embedded in the live post (lands with chunk 1.4). The sweet spot for input → result rendering is under 100ms. Past that, you can feel the lag. Past 200ms, you start typing again.
How to build one that doesn’t suck
(…rest of post…)