In 2014, GitHub shipped Atom with Cmd+Shift+P. In 2015, VS Code lifted it. In 2018, Linear made Cmd+K a brand. In 2020, Notion, Figma, Slack, Superhuman, and Linear had all converged.
In 2026, if your tool does not have a command palette, it feels like a tool from 2010. The command palette is the single most important UI primitive of the last decade.
We will talk about why it matters in email specifically.
What a command palette does
A command palette is a single keystroke (usually Cmd+K) that opens a fuzzy search box. You type a few characters of any action, label, contact, or destination. It surfaces matches. You hit enter. The action happens.
It is one shortcut that replaces, on a typical day, 50 menu items, 30 toolbar buttons, and an account switcher.
Sounds modest. It is anything but.
Why menus lose to palettes
Three reasons.
One: menus require you to know where the action lives. “Is ‘Mark as VIP’ under Edit, View, or some context menu?” A palette does not care. You type “vip” and the action surfaces.
Two: menus require mouse precision. Pull down the File menu. Find the right item. Click. Cost: 2 seconds plus attention. A palette is one keystroke and three letters of typing.
Three: menus require chunking. You have to organize related actions under a parent. The palette has no parents. Every action is a sibling, ranked by your usage.
What this looks like in email
In Apple Mail, applying a label requires: click the message, click the “flags” dropdown, scroll to the right color, click. About 4 seconds.
In a palette client, applying a label is: Cmd+K, type “flag red,” enter. About 0.8 seconds.
The savings are real but not the main point. The main point is that the palette removes the menu-finding cognitive cost. You stop looking for the action. You just name it.
What we put in STAMP's palette
The full list of actions accessible by Cmd+K in STAMP:
- Switch to any connected account, including aliases.
- Apply or remove any tag (urgent, VIP, reply needed, frustrated, etc.).
- Snooze with natural-language times (“snooze tomorrow 9”).
- Send to any contact (“email john ackerley about quote”).
- Search the entire archive (“contracts june 2024”).
- Jump to any view (urgent queue, reading queue, snoozed).
- Create a saved search.
- Toggle settings.
- Trigger any keyboard shortcut by name (“archive”).
Every one of those is also accessible by a dedicated shortcut. The palette is the unified way in. New users learn the palette first and pick up dedicated shortcuts as they get faster.
The palette is also the help system
A subtle benefit: the palette doubles as a discoverable help system. New users open Cmd+K, see the list of actions, and learn what the app can do.
A menu does the same job, badly. Menus are organized by hierarchy. Palettes are organized by use frequency. The palette is the fastest tutorial you never wrote.
The palette is what onboarding wished it could be.
Why “just learn 30 shortcuts” is the wrong answer
Some power users will tell you to just memorize the shortcut for every action.
This is fine for the 10 high-frequency actions. For the long tail (apply a specific tag, send a saved snippet, jump to a saved search), memorization breaks down. Nobody remembers the shortcut for “apply tag ‘follow up Q3’.”
The palette covers the long tail at the same speed as a learned shortcut, with zero memorization cost.
Anti-patterns to avoid
If you are designing or evaluating a palette, watch for these:
Slow opening. A palette that takes 200 ms to render is dead on arrival. Open in under 50 ms or do not bother.
Bad fuzzy matching. “Mark as VIP” should surface for “vip,” “mark vip,” “v.i.p.,” “important.” If the matcher is too literal, users abandon.
No usage ranking. A palette should learn what you do most and surface those first. STAMP's palette ranks by your last 200 actions.
Hidden behind a different shortcut. If your palette is Cmd+P or Cmd+J or anything else, you are losing convention. Use Cmd+K.
A confession
We did not always have a palette. STAMP's 2024 alpha had only dedicated shortcuts. Users hit a wall around action 25, where memorizing more shortcuts had diminishing returns.
We added the palette in beta. Usage of every other shortcut went up, not down. The palette did not replace the shortcuts. It made the shortcuts more learnable, because users discovered them through the palette and graduated to typing them directly.
How to introduce the palette to your team
If you switch to a palette-driven client, the team learning curve is one day.
- Pin Cmd+K to a sticky note on every monitor for a week.
- Stop teaching the menu locations of actions. Teach the action name.
- Have one shared lunch where everyone watches the most experienced user run their inbox.
After that week, the menus become vestigial. People stop opening them. The palette is the new default.
Where to go from here
For the broader keyboard argument, how to never touch the mouse for email again. For the shortcut grammar, keyboard shortcuts every email power user should know.
Cmd+K to fly anywhere. hello@stamp.email