The Stream Deck Nobody Asked For

How a bedtime phone session turned into a GitHub repo by morning

I was lying in bed, half asleep, scrolling my phone the way you’re not supposed to.

But instead of doom-scrolling, I was talking to Claude. I had this idea rattling around—a dumb, specific, delightful idea—and I wanted to see if it had legs.

I own a Stream Deck. If you haven’t encountered one, it’s a little desktop peripheral with 15 customizable LCD buttons. Each one can be programmed to do whatever you want—launch apps, trigger shortcuts, run scripts, send keystrokes. It was designed for Twitch streamers who need to switch scenes and trigger sound effects on the fly.

But it escaped the streaming world a while back. Podcast producers use them to manage live recordings. Music producers map them to DAW controls. Productivity nerds—my people—turned them into macro pads for everything from Zoom controls to Photoshop workflows. There’s a whole cottage industry of people sharing their custom setups.

I’d been using mine off and on for years. Honestly, it spent more time gathering dust than earning its keep. But I’d recently been spending a lot of time in Claude Code—the terminal-based coding tool that’s become my daily driver—and the repetitive keystrokes were piling up.

Start a session. Resume a session. Accept a change. Clear the screen. Switch models. Check costs.

The same commands, dozens of times a day.

That’s when it clicked: Stream Deck was *built* for this.

The Bedtime Brainstorm

So there I am, winding down for the night, and I pull up Claude on my phone. Not Claude Code—just the conversational Claude app. The way you’d text a friend about an idea.

“Hey, I want to set up my Stream Deck for Claude Code. Here’s what I’m thinking...”

And of course Claude didn’t just affirm the idea. It started building. Within a few minutes I had a full layout designed—a 5x3 grid mapping the commands I use most. Session launchers across the top row. Slash commands in the middle. Controls on the bottom.

Then it generated a set of pixel-art icons. Minimal, monochrome, retro-looking. Actually good.

I fell asleep with a fully designed Stream Deck profile on my phone and a grin on my face.

.

The Vibe-Bro Mandate

The next morning I started setting it up. Opened the Stream Deck software, began dragging buttons around, configuring hotkeys one by one.

About three buttons in, I stopped.

What kind of vibe-bro, worth his salt, would do things manually if he doesn’t have to?

I pulled the work into Claude Code and asked a simple question: “Can you configure my Stream Deck directly?”

Of course it could. And it did.

In a matter of minutes, Claude Code generated the configuration files, set up the button mappings, and wired everything together. I tested it, tweaked a few things, and asked it to create variants—one for Ghostty terminal, one for Apple Terminal, and a generic version for whatever setup someone else might use.

Then I had it push the whole project to GitHub.

From bedtime idea to published open-source repo, by lunch. 15 custom icons, three terminal variants, auto-setup scripts, documentation.

If you want to use this, just point Claude to the repo and say go. Literally.

The Pattern

This isn’t really a post about Stream Deck. If you’re one of the rare productivity geeks who owns one, grab my repo and remix it. You’re welcome.

But the thing that keeps hitting me—the thing I keep coming back to in this newsletter—is what just happened in that sequence.

I had an idea. A small one. The kind of thing that in a previous life would have gone on a sticky note, maybe a “someday” list, and slowly faded into the background noise of good intentions.

Instead, I explored it on my phone while half asleep. Refined it the next morning. Implemented it, tested it, packaged it, and shared it—all before my afternoon coffee.

The technical hurdles that would have stopped me two years ago—learning the Stream Deck SDK, writing configuration scripts, generating icons, setting up a GitHub repo with proper documentation—just... dissolved.

I wrote previously about the collision between analog wisdom and digital acceleration. About navigating this exponential rate of change while holding on to what’s essential.

Here’s what I’m finding: when the tools get out of the way, the doing gets more human, not less.

I wasn’t wrestling with code. I was designing an experience. I was solving a problem I actually had. I was making something and sharing it—the whole creative loop, idea to artifact, in less than a single day.

Just Do Things

There’s a phrase bouncing around the AI-native crowd: “just do things.” It sounds flip. It’s not.

For most of my career, the distance between “I have an idea” and “here’s the finished thing” was measured in weeks, months and years. Learning curves. Documentation rabbit holes. Stack Overflow threads. The friction was enormous, and most ideas died in that gap.

That gap is closing. Fast.

I built a whole landscaping project last summer using YouTube as my teacher. But this is different. YouTube showed me how. AI removes the how entirely and lets me stay in the what and the why.

What do I want this to do? Why does it matter? The machine handles the rest.

That’s not laziness. That’s leverage. The same way a power drill isn’t laziness compared to a hand drill—it just lets you build more, faster, with your energy focused on design instead of repetition.

The Catch

I’m still a GenX skeptic at heart. I know what I don’t know. And I know that every tool that gives you superpowers also gives you new ways to screw up at superhuman speed.

But I’ll tell you this: that Stream Deck project was pure fun. The kind of fun I used to have building things as a kid—before I knew about scope creep and technical debt and stakeholder alignment.

An idea. A tool. A result.

That loop is getting tighter. And I’m starting to think the people who thrive in whatever’s coming next won’t be the ones with the most technical skills. They’ll be the ones with the most ideas and the willingness to just... try them.

The Stream Deck sits on my desk now, glowing with its little pixel icons, saving me a few keystrokes every session. It’s a small thing.

But it used to be just an idea I had in bed.

~capshaw

My desk. My StreamDeck with this implemented.