Command Palette

Press ⌘K (Ctrl+K) anywhere on this page, or the button — a palette only a hotkey can reach is invisible to anyone who has not been told the hotkey. Open with nothing typed and you get recents and the groups, never a blank box; recents vanish the moment you type, because a recent row plus its own group row is one command listed twice. Groups sit in the order the array declares them, not alphabetically. Type inv to reach Billing through a keyword that is not in its label, zzz for a no-results message that names what you typed. Focus a field first and ⌘K does nothing: the keystroke belongs to whoever is typing. This is the only preview on the page with the hotkey bound.

run is awaited. Press “Rebuild search index”: the row spins, everything else recedes, the palette refuses to close, and it dismisses only once the work settles. Press “Deploy to production”: the rejection renders on its own row with the reason and turns it into a retry — icon, label and colour all change, so it never depends on red alone. A palette that closes optimistically and swallows that error is worse than no palette.

“Change status →” pushes its own list. One level, capped in the type rather than left to a recursion the row height cannot carry. Escape goes up before it closes the palette, Backspace on an empty query does the same, and the breadcrumb’s back button is there for the pointer — with focus handed back to the input, so the arrow keys keep working.

The search hook is for rows a client fetches. It is debounced, runs only with a query, and lands **below** the local groups so late arrivals never shove the list out from under the cursor. Three distinct outcomes, all pressable: type sa for results, zz for “no matches”, and fail for the service error — loading, failed and nothing-matched are three messages, never one.

A command the current user cannot run stays in the list, disabled, with the reason as its second line rather than a tooltip — hover-only text is unreachable for a keyboard, and a palette is a keyboard surface. Arrow keys skip them, so the block is real and not just visual.

The fourth message: no commands at all is not the same as nothing matched, not the same as still loading, and not the same as a failed fetch. commands={[]} says so instead of showing an empty frame.