Control surface
A layer of buttons over the agent harness, so moving between agent threads takes one press. It works like a broadcast switcher, where the director calls a camera and someone presses its button.
Jesse of not-replaced-yet puts it at step seven of a ladder: prompt engineering, context engineering, tool calling, agents, swarms and loops, the harness, then the control surface. Jesse's is an Elgato Stream Deck XL. Each client gets a folder of keys, one per work stream, and each key opens its own Claude Code thread. Nick calls it an abstraction layer: a lot sits under one press, and the person has to decide what they want before Claude Code sets it up.
Jesse reports that laying out the keys forces a decision on how work time is divided, and that with less friction more threads run at once, so token use goes up. Related: thread-rehydration, malleable-computer, and the software-side answer in agent-orchestrating-multiplexer.
Source: report