Blog

What is a command bar, and why put AI in one?

Command bars went from a developer curiosity to a standard interface pattern. Here is what they are, how they differ from a search box, and what changes when AI can see your screen.

Press Ctrl + K in most software built after about 2020 and something appears: a box, a list of actions, a fuzzy search. Slack has one. Linear, Notion, GitHub and Figma have one. Your browser's address bar has quietly been one for years.

That pattern has a name, and it escaped the browser a long time ago.

A search box finds content. A command bar runs actions.

The distinction matters. When you type "invoice" into a search box, you get documents containing the word invoice. When you type it into a command bar, you might get an app, a folder, a template to create, and a saved workflow — things you can do, not just things that exist.

The three properties that define one:

  • It is keyboard-first. It opens on a hotkey and closes when you are done. Reaching for the mouse defeats the purpose.
  • It is fuzzy. Typing wrd should find Word. You should not have to remember exact names.
  • It ranks by behaviour. The thing you opened yesterday should outrank the thing you have never opened.

Why it escaped the app

For a while, every app had its own command bar and its own hotkey. Useful inside that app, useless the moment you left it.

System-wide launchers fixed that. Alfred did it on macOS more than a decade ago, Raycast modernised it, and on Windows the job fell to PowerToys Run, Flow Launcher, Wox and others. One hotkey, anywhere in the operating system, for anything you might want to do.

Once that habit forms, the bar becomes the place your hands go by default. Which is exactly why it turned out to be the right place to put AI.

What AI actually adds

The lazy version is a chat box behind a hotkey. That is a worse ChatGPT with extra steps, and plenty of tools shipped it.

The version that earns its place knows where you are. A command bar sits above everything you do, so it already has access to the things that make a question answerable:

  • The app you are in
  • What is on screen
  • Your clipboard
  • The file, page or video in front of you

That turns "summarise this" into a complete question rather than a prompt you have to paste context into. The difference in practice is large. You stop assembling context and start asking.

It also makes actions possible in the other direction. If the bar can already open apps and manage windows, an assistant sitting in it can too. "Open the two apps I need for this" is a reasonable request when the thing you asked is also the thing that launches apps.

The tradeoff

Everything above requires the launcher to see quite a lot of your machine. That is a real cost, and it should be your first question about any tool in this category — including ours. Look for software that asks before it reads, scopes access to folders you nominate, and tells you what leaves the device.

A command bar is a small interface with a large amount of reach. That is what makes it useful, and it is why the trust question is not optional.

Pivit is a command bar for Windows with AI that reads the app in front of you. Download it free, or see how it compares to other launchers.