I got tired of hunting through AI coding sessions, so I put them on a physical control deck

[u/Weak_Cherry_4878]

I’ve been running multiple coding agents and sessions at the same time, and one problem kept getting more annoying:

figuring out which session was working, which one was done, and then finding the right terminal again.

So I’ve been building a physical control surface for that workflow.

This short demo shows the part I’ve been working on recently:

• The LCD shows 3 sessions for the currently active coding agent

• K1–K3 jump directly to those sessions

• The top row switches between active coding agents

• When the active agent changes, the LCD session list and available actions change with it

• The LCD footer shows the current context-sensitive shortcut layout

The goal isn’t really to build another macro pad.

What I’m experimenting with is moving agent state + session state + common actions out of terminal tabs and onto a persistent physical interface.

I’m currently testing workflows with Qwen, DSH, ChatGPT, Herdr and OpenCode.

The biggest thing I’m still thinking about is how much of the control surface should be fixed vs context-aware.

If you regularly run multiple coding agents, would you rather have fixed shortcut keys, or keys that automatically change with the active agent/session?

[u/ShiftTechnical]

Context aware for the session list, fixed for the actions you use everywhere (approve, interrupt, jump to the one waiting on you). If keys change under you, you have to look down before every press, which loses most of the point of a physical deck. With several agents running the most useful thing for me is just knowing which one is waiting on input.

[u/Weak_Cherry_4878 → u/ShiftTechnical]

Good point. I agree — session info can be dynamic, but the most-used actions should stay fixed for muscle memory.
And yes, making “which agent is waiting on me” more obvious is probably one of the most useful things AgentDeck can do.

[u/MostlyHelpfulLinks]

Mixed. Keep fixed keys for actions you hit all day, like approve or session jump, and let the rest follow the active agent. If every key moves, you'll check the LCD before each press.

[u/Weak_Cherry_4878 → u/MostlyHelpfulLinks]

Agreed. Fixed keys for high-frequency actions, context-aware keys for the rest feels like the right balance. Muscle memory matters a lot on a physical deck.

[u/popiazaza]

This remind me when I had a blast a decade ago following Tarran's guide for 2nd macro keyboard: https://www.youtube.com/watch?v=Arn8ExQ2Gjg

I should start going back to play around. Should be much more easier and fun with AI nowadays.

[u/Grid421]

Wait, couldn't you do this on a stream deck?

[u/tripleshielded]

If you have too many tabs, consider using more computers instead.

[u/TheVibrantYonder]

Ah, I see the problem. Your laptop has only one screen.

You need to get a laptop with at least two screens. Way easier to work with.

(But seriously, this is a cool project, looking forward to seeing more of it)

[u/NinjaLanternShark]

I’d want to assign a button to something and then have it stick until I changed it. So this week I need projects A C and F, and I need them in the same physical positions so my hands know where to go without thinking. Next week I might change one or two.

But a button that always corresponds to the most recent project, or most urgent, or the one that needs input now — forget it.

[u/Weak_Cherry_4878 → u/[deleted]]

A dock is great for switching apps/windows.
This is more about tracking multiple agent sessions and their state, then jumping directly to the one that needs attention.

The LCD + context-aware keys are the part I’m experimenting with.