Pimp My IDE / garage dispatch
Back to garage
October 1, 2026 | interface craft / operator controls

Your agent needs a panel, not more chat chrome.

Chat is good for intent. It is a bad place to hide recurring status, authority, stop controls, and run evidence. Give those jobs fixed positions.

Keep the conversation. Pull repeated operational state out of the scroll and bolt it to a labeled backplane.

The old panels made state spatial.

Marcin Wichary photographed modular industrial dashboards in German and Polish museums. The collection includes air-traffic, rail, tram, and power-plant panels. Across the photographs, labeled modules, lamps, counters, switches, and removable plates occupy fixed positions.[1]

Wichary is careful about uncertainty. He identifies museum context and visible details, then marks guesses about how individual controls worked. That boundary matters. The photographs support a design observation without turning every lamp into a documented operating procedure.

A fixed position lets the operator look for a state instead of searching for a sentence.

Specialized keys reduced recall.

IEEE Spectrum's history of the Bloomberg Terminal describes a keyboard built for traders and analysts. Its color-coded function keys had labels that stated their use. Users did not have to remember each command. The original keyboard sent commands through a controller and dedicated network to centralized computers, which returned the result.[2]

The lesson is narrower than "make everything look like a terminal." A repeated, important command deserves a stable control with a plain label. The label should describe what happens. The result should return to a known place.

Agent chat mixes four different jobs.

A coding-agent transcript often carries intent, current state, action requests, and evidence in one vertical stream. The stream is useful history. It is weak current-state storage. A status line scrolls away. An approval can resemble ordinary prose. A stop command may sit beside suggestions that have no authority.

Keep free-form intent in chat. Promote recurring operational jobs into modules. Put live status in one slot. Put the current authority mode in another. Give Stop its own control. Keep the receipt visible after the action ends.

Keyboard state must stay visible.

The W3C explanation for WCAG 2.2 Focus Visible says each item that receives keyboard focus needs a visible indicator. It also says the indicator must remain visible while the item has focus.[3] A custom control panel cannot trade that requirement for atmosphere.

Use native controls as the source of truth. Keep the focus ring outside the control. Pair color with words such as SELECTED, OPEN, and STOPPED. Respect reduced-motion settings. A panel should reduce search cost, not create a decoding test.

Interactive makeover / control-room backplane

Set authority, fit modules, keep Stop fixed

Traditional purpose replaced: a toolbar plus a scrolling activity log. Better version: one authority selector, four optional modules, a fixed Stop control, and a receipt that keeps the latest panel state.

Configure the panel

This is a teaching demo. It does not connect to an agent or execute commands.

Authority detent
Backplane modules
Panel sequence

One decision per row

  1. Set authority. Choose whether the panel may observe, prepare, or request action.
  2. Fit modules. Keep only the readouts and controls used during the shift.
  3. Latch the layout. Save the intended panel state before connecting a live route.
  4. Test Stop. Prove the command module blocks while status and the last receipt remain visible.
Operator panel / fixed backplane

Agent control room

Observe / 3 fitted

Observe mode is selected. Three modules are fitted.

The panel can display status and a read-only command. Stop remains available. Add the receipt module to retain run evidence.

A fitted module means the panel includes that requirement. It does not mean live state, command policy, stop delivery, or run evidence has been connected or tested.

One backplane / four jobs

Do not make the transcript carry current state.

01 / STATUS

Fixed readout

Reserve one location for the task, phase, and last state change. Do not make the operator search the transcript.

02 / COMMAND

Plain label

Name the operation and current authority. Do not make icons or color carry the command alone.

03 / BRAKE

Stable stop

Keep Stop in the same location across modes. Do not bury it in a menu that changes with context.

04 / RECEIPT

Retained result

Save revision, output, and open limits after the transient activity state disappears.

Sources read

Source log and evidence boundary
  1. Marcin Wichary, "Before pixels: Modular industrial dashboards", published September 30 and read October 1, 2026. The post presents museum photographs of modular air-traffic, rail, tram, and power-plant panels. Wichary identifies visible modules and marks uncertainty about several functions.
  2. IEEE Spectrum, "A Brief History of the Bloomberg Terminal", read October 1, 2026. The article describes the early terminal keyboard, its labeled and color-coded finance keys, the controller, the dedicated network, and the request-and-result path.
  3. W3C, "Understanding SC 2.4.7 Focus Visible", read October 1, 2026. The guidance says keyboard-operable interfaces need a mode with visible focus and that the indicator must remain visible while focus is shown.
  4. Hacker News discussion for "Before pixels: Modular industrial dashboards", item 49912792, checked against the Hacker News API on October 1, 2026.

Evidence boundary: the four-module backplane is Pimp My IDE editorial guidance. It is inspired by the visible organization of the photographed panels, the documented Bloomberg keyboard, and W3C focus guidance. We did not reconstruct the museum equipment or measure this control pattern against a production coding agent.