The number on our own homepage is 173 commands. That number is true and it is also a slightly dishonest way to describe how anyone uses this app. So I logged a week — one person, ordinary work, no attempt to use features for the sake of it.
The honest count
Eleven commands accounted for almost everything. A long tail of maybe fifteen more appeared once or twice. The remaining hundred and forty-something did not come up at all, which is roughly what you would expect and not a problem — a command you never run costs you nothing.
The interesting part is not the ratio. It is that the eleven are not the eleven I would have predicted, and that half of them are not AI at all.
The eleven
Writing: one tone, not eleven
We ship eleven rewrite tones. I used one. "Concise" ran eighteen times; "Professional" twice; the other nine never. This is not a failure of the other tones — Customer Support and Executive get heavy use from people whose jobs involve those registers. It is a reminder that the tone menu is a personal object, and the right move is to bind your one tone to a hotkey and forget the menu exists.
The mechanic that made it stick is Magic Rewrite replacing text in place. Select, hotkey, done — the paragraph changes under the cursor and I never leave the editor. When I first used a version that returned the rewrite in a panel to copy back manually, I used it maybe a third as often.
The clipboard one
Twenty-five uses, and almost none of them were the obvious "paste the thing I copied a second ago". The pattern was recovery: a URL from this morning, a snippet of config from a doc I already closed, an error message I copied before restarting.
Two features earned their place inside that. Named stacks — select several clips, join them, paste the group — turned out to be how I assemble a status update. And the image OCR, which runs locally, meant I could copy a screenshot of a stack trace and search its text later. That is the one that surprised me.
Windows: three of fifteen
SnapWheel has fifteen snap positions. I used three. Thirds and corners went untouched all week, which makes me suspect they matter enormously to people with a 34-inch ultrawide and not at all to people on a laptop.
The genuinely useful discovery was Layouts rather than snaps: saving a multi-app arrangement and restoring it. One saved layout for writing, one for reviewing code. Two commands replaced about a dozen individual snaps a day.
What I never touched
Canvas. Kanban. Emoji search. QR codes. Every social action. Nine of eleven rewrite tones. Symbol picker. Speedtest. Purge. Brew Store. None of it came up in a normal week of work, and I write parts of this app.
I am not going to pretend that means those features are filler — the Kanban board has a devoted set of users and Purge is the reason some people installed in the first place. It means the app has to be built so that features you ignore stay invisible.
So hide the rest
The practical conclusion of the log: spend twenty minutes hiding things. Any action can be hidden from the palette, favorited to the top, or renamed with an alias that matches how you actually think about it. A palette showing eleven commands you use is a much better tool than one showing 173 you might.
If you want the reasoning behind shipping 173 anyway, that is the other post. If you want to know how the three text surfaces differ, start here.