Command palette

mod+k (⌘K on macOS, Ctrl+K elsewhere) opens one keyboard-first entry point for the whole app: run any command, jump to an issue or project, find a teammate's issues, and act on the issue you are looking at — without touching the mouse. / opens it in search mode, ? opens the read-only shortcut reference instead.

Guides, in the order you'd actually need them

1. Add a global commandCommand paletteAdd a global commandWorked example: a "Go to my Issues" command (a page used purely to demonstrate the shape) that is reachable from the palette and from the keyboard as g i,… — a command that exists on every page (navigation, preferences, account), or one a single component registers while it is mounted, with an optional keyboard shortcut.
2. Add a contextual command with nested stepsCommand paletteAdd a contextual command with nested stepsWorked example: the issue page's Change status…. It depends on the current issue, opens a second list ("a step") of the statuses the workflow allows, hides… — the pattern behind the issue page's "Change status…", "Labels…" and "Assign to…": commands that depend on the current page, open a step, and only appear when the user may perform them.
3. Add a search sourceCommand paletteAdd a search sourceWorked example: how people (@ann) were added next to issues and projects. The same steps add any new kind of result. Everything goes through one internal e… — a new kind of result (like issues, projects or people) found through the internal GET /command-palette/search endpoint.

The architecture in one paragraph

A command is not a shortcut: every action the palette can run is a Command (resources/js/types/Commands.ts) and a keybinding is just an optional shortcut attribute of it. CommandProvider (resources/js/context/CommandContext.tsx) holds the registry, the open state and a stack of nested steps; components register commands for as long as they are mounted with useCommands() (same lifecycle as useShortcuts()), and the app-wide ones live in useGlobalCommands. While a command is registered, its shortcut is handed to the shortcut engine (see ../shortcuts/Keyboard shortcutsEvery keyboard shortcut in Orbit — ? for help, mod+k, alt+p, a page-scoped p for "create project" — goes through one system: ShortcutContext. There's no pe…), so the palette row, its shortcut chip and the help view all come from one definition. The CommandPalette organism renders the registry: local commands are fuzzy-ranked on the client and appear instantly; issues, projects and people come from the server (usePaletteSearch, debounced 150ms, stale responses cancelled) and stream in below them. The first character can scope the search: > commands only, # issues only (#42 is the project-scoped number users see), @ people only.

Where things live

Rules that keep it correct

• Never offer what the user cannot do. Hide a command with when() on the same ability the controller enforces; hidden, not disabled.
• Mutations reuse the existing routes (router.patch(route('issues.update', id), ...)), so validation, workflow transitions, activity logs and notifications stay in one place.
• Server search is scoped to the user's project memberships in the repository query itself, and every source needs a test with a non-member.
• Memoize what you register. useCommands(commands) re-registers whenever the array identity changes, which re-renders its consumers; an unstable array (a fresh [] default prop) loops.
• Theme variables only, and AA contrast. Use --text-gray-color, not --text-muted-color, for palette text: the muted token fails 4.5:1 on both themes. paletteContrast.test.ts checks every pair the palette uses against global.css.