A Stream Deck for Claude Code: What Actually Goes on the Keys

The KM16 Macropad is sixteen keys on an anodised aluminium body, with one large knob and two small ones, and it is $119. If you searched for a stream deck for Claude Code, this is the plain version of that idea: a grid of programmable keys beside your keyboard that sends whatever you assign to it, with no screens under the caps and no host application needed while you work.

What would I actually put on the keys?

Claude Code is the same few decisions on a loop. Accept an edit, reject it, interrupt a run that has clearly gone the wrong way, clear the context, resume the last session, move between terminal panes. That is five keys, and it is most of what anyone uses. The rest of the grid fills with things that are not Claude Code at all: run the tests, open the diff, go back to the branch you were on an hour ago.

Keys can send text as well as keystrokes, which is the part people underrate. A standing instruction you retype several times a week can live on one key and arrive complete every time. The knob is the other quiet win: scrolling back through a long transcript with a knob beats holding a page key down.

Is a grid with screens better than plain keys?

For flexibility, yes, and we would rather say so than pretend otherwise. A key with a small display under it can relabel itself, so one key can mean one thing in a terminal and something else in a call, and you can read what it currently means instead of remembering. That category also has a software layer running on the computer, which is where other people's integrations live, so some things work without you writing any glue at all.

What plain keys give you instead is feel and independence. A mechanical switch under a real cap tells your finger it fired, so you press it without looking down, and the pad keeps sending what it was told to send whether or not anything on the host is awake. We have not run the two kinds side by side on one desk, so take this as a comparison of mechanisms rather than a review.

Can it show me how much Claude Code usage I have left?

Not by itself, and that is worth knowing before you spend anything. A device only shows a number if something on your machine reads that number and pushes it out. A key with a display at least has somewhere to put it once you have done that work. A plain mechanical key has nowhere to put it at all, which is a genuine limitation of what we sell.

If a readout is the real requirement, the honest answer here is the Desk Terminal at $79, a small colour screen that sits off to one side and shows one thing permanently, or the Status Light at $45 when what you are watching is a state rather than a number. Both want a short script from you. Neither arrives knowing anything about Claude Code.

When is a key grid the wrong purchase?

When the thing breaking your concentration is not pressing keys, it is checking whether the run has finished yet. A grid cannot fix that, because a grid faces you at desk level and you are not looking at it while you work on something else. A lamp you can see from the other side of the room can. And if your list of repeated actions is honestly two items long, sixteen keys is more pad than you need: Slam Buttons at $29 is two full-size arcade buttons that cover accept and reject and make a satisfying noise doing it.

If you are still deciding whether any of this earns its desk space, read what a macropad is actually for in programming first.