Field Notes

Build a Mac command palette: your commands above your apps

Pick from List now takes commands, rows of your own pinned above the list. Add a Router and a Mac command palette is eight nodes with no nesting.

The chooser, run from the canvas. Four commands sit above 127 installed apps, and the first one already holds the highlight.

A command palette is a hotkey, a search field and a list. Press the keys, type three letters, press Return. Code editors have had one for years. On a Mac the nearest thing is a launcher, which is a list of apps with a few commands of your own squeezed in beside them.

I built that launcher two months ago, and the commands were the awkward part. Each one was an extra row in the app list, so every pick left the chooser by the same wire. The flow then had to work out whether you had picked an app or a command, and which command. That took a Condition, a Template and a shell case statement.

Since v1.62.0, Pick from List has commands of its own, and a Router gives each one its own wire. This post rebuilds the launcher as a Mac command palette with both.

The flow

Fig. 1Eight nodes in two sections. The top row lists the apps and opens the one you pick. The Command wire drops to a Router, which has one outlet per command.

The top row is the launcher: a Keyboard Shortcut on cmd+shift+space, Installed Apps for the list, Pick from List to show it, and Open File to launch the app you pick. Everything new hangs off the wire labelled Command.

Commands are rows you pin above the list

A command is a name, an icon and a kind. You add them in the Pick from List inspector under Commands, and they appear above the records in the order you list them.

Fig. 2The Commands list in the inspector. Three commands are set to Wire. Morning Brief is set to Flow and names the flow it runs.

Three things follow from commands being part of the node and not part of the list.

Search filters commands and rows together

Fig. 3The chooser after typing git. One command is left, GitHub Notifications, above the four apps that match.

Type git and both groups narrow at once. A command that does not match hides until you clear the search, and the highlight moves to the first one that does. So the whole gesture for GitHub Notifications is the hotkey, git, Return.

The Prompt is Run a command or open an app…. The chooser has no title bar, so the search field's placeholder is the only place to say what the list is for.

Three ways out

YouOutletThe payload gains
Pick an appSelectedselected, the whole row, and selectedIndex
Pick a Wire commandCommandcommand.name and command.index
Press Escape, or click outsideDismissednothing

Exactly one outlet is taken and the other two are skipped in full. Open the app reads {{selected.path}} and can never run on a command. A command's branch can never run on an app. A command also clears selected and selectedIndex from the payload, so a branch that tests for a picked row gets an honest answer.

One Router where there was a staircase

One outlet carries every Wire command, so something has to split them. The only tool for that used to be a Condition, which answers Yes or No. Three commands took three of them, each hanging off the No of the one before:

Fig. 4The same palette built with Conditions. Downloads?, GitHub? and Date? step down and to the right, and Open the app is at the bottom of the stairs.

It works, and it has ten nodes to this flow's eight. The count is not the problem. The shape is.

A Router reads one field and has one outlet per case. Here Field is {{command.name}} and the cases are the three command names.

Fig. 5The Router inspector. Field is command.name, and the three cases are the three Wire commands.

Every command is now two hops from the chooser, however many there are. Adding one is a row under Commands, a case in the Router, and a wire. Three details make it hard to get wrong:

What a run looks like

Fig. 6The canvas after picking Copy Today's Date. The chooser's badge reads Command, the Router's badge reads Copy Today's Date, and the wires the run took are lit.

Each node that branches shows the outlet it took, by name. The Router's badge is the case, not a Yes or a No. Execution History says the same in text, with command: {name: Copy Today's Date, index: 2} as the input to the branch.

I ran this flow four times before publishing, once for each way out: a command, an app, Escape, and the Run a flow command below. The date reached the clipboard, Calculator opened, Escape ended the run as completed with nothing after the chooser, and Morning Brief got a run of its own.

A command that runs another flow

The fourth command, Morning Brief, has no wire and no case. Its kind is Flow. Picking it starts that flow as its own run, as if you had pressed Run on it, and Pick from List takes no outlet, so nothing else in this flow runs.

Fig. 7The top row after picking Morning Brief. The chooser's badge reads Ran Morning Brief, and neither the Selected wire nor the Command wire is lit.

Use Wire when the work belongs to this flow, or is one node. Use Flow when the work is already a flow you start some other way. A morning brief that runs on a schedule is a good example: one row in the palette runs it on demand, and the flow itself does not change.

A Flow command is subtitled with its flow's name and wears the icon of that flow's folder unless you give it one of its own. A command you listed still shows when its flow is turned off. It cannot run the flow it lives in.

Offer shared flows fills the list for you. Turn it on and every flow that is switched on and exposed to AI agents appears as a Flow command after the ones you listed, in name order.

How it behaves

Variations

Paste into the Flow Builder

On a keyboard shortcut, show my installed apps in a chooser with three commands on top: Open Downloads, GitHub Notifications and Copy Today's Date. Open the app I pick. Send the command I pick through a Router so each command has its own branch: open my Downloads folder, open https://github.com/notifications, or copy today's date to the clipboard.

What's in this flow

One trigger. Nodes are listed in the order a run reaches them; the canvas above shows where it branches.

Download this flow
  1. Keyboard ShortcutCmd-Shift-Space
  2. AppleInstalled Apps
  3. ActionPick from List
  4. Open FileOpen the app
  5. ConditionRouter
  6. Open FileOpen Downloads
  7. Open URLGitHub Notifications
  8. Run ScriptCopy Today's Date

Run this one yourself

Download the flow, double-click it, and Watchflows opens it on the canvas. Everything in this note is on the 14-day free trial.