Command palette v2 — fuzzy actions, per-context ranking and a plugin API

Context

The command palette is the most-used surface of the library — 41% of sessions open it at least once — and the current implementation has hit its ceiling: flat action list, no context awareness, and every consumer app forking it to inject custom actions. v2 makes the palette a platform.

Three pillars: a proper fuzzy matcher (typo-tolerant, weighted by recency), per-context ranking (the palette knows whether you are in a table, a form or an editor), and a typed plugin API so apps stop patching internals.

Plugin API sketch

import { definePaletteSource } from '@lndev-ui/palette';

export const deploySource = definePaletteSource({
   id: 'deploys',
   // Ranked only when the current route matches.
   context: (ctx) => ctx.route.startsWith('/deploys'),
   actions: async (query) => {
      const environments = await fetchEnvironments(query);
      return environments.map((env) => ({
         id: `deploy-${env.id}`,
         label: `Deploy to ${env.name}`,
         icon: RocketIcon,
         shortcut: env.isProd ? undefined : ['d', env.key],
         run: () => deploy(env),
      }));
   },
});

Scope

• Fuzzy matcher with per-character scoring, typo tolerance of 1, and recency boost (half-life: 7 days)
• Context providers: table, form, editor, navigation — extensible through the plugin API
• Plugin API: typed sources, async actions, loading states, error boundaries per source
• Full keyboard model: nested pages, back with Backspace, peek with Tab
• Latency budget: 8ms per keystroke at 5,000 registered actions

Acceptance criteria

Every app we surveyed rebuilt ranking on top of the palette. If the library ranked by context, we could delete about 400 lines each.— ecosystem scan, July 2026