A Desk Setup for Pairing with an AI Agent

In cream-and-grey eighties console styling, Retro Board is an 87-key tenkeyless mechanical keyboard. It covers ordinary typing and review navigation without a number pad, but the catalogue does not confirm switch type, programmability or ergonomics for a particular user.

How is pairing with an agent different from working alone?

The work alternates between describing intent, reading proposed changes, checking evidence and correcting course. The agent can produce code faster than a person can review it, so the desk should optimize comprehension rather than submission speed. Keep task, worktree and branch visible at every prompt.

Write acceptance criteria before the agent edits. A separate test command and review checklist prevent conversation confidence from replacing verification.

How should the screen split between your code and theirs?

Give the diff enough width to read complete lines and keep the agent terminal adjacent or one direct switch away. Use another region for tests or application output only when it belongs to the same task. Independent agents deserve separate full-width windows rather than crowded panes.

Place the active file and diff on the main visual axis. Chat history can move aside after its current request and response have been understood.

What does the typing half of the desk need?

It needs a keyboard position that keeps wrists and shoulders comfortable, an accurate pointer and shortcuts whose meaning remains stable. Exact comfort depends on body, desk height and key feel, so trial matters more than a product description. Keep Enter and approvals on the normal keyboard.

A tenkeyless layout leaves more pointer space but omits the number pad. Anyone who relies on numeric entry should treat that as a real tradeoff.

What does the reviewing half need?

Use readable text, strong diff colours with non-colour markers, a clean Git status and access to the complete command output. Review generated tests as carefully as production code. Run checks from the same worktree and inspect changes against the intended base.

The Retro Board supplies a conventional 87-key form for deliberate input, not automated authority. Judge it by confirmed layout and styling, then arrange the display so every press follows visible evidence rather than agent momentum. Keep a paper or local text note for open assumptions and unresolved review items. Before each new prompt, mark what was verified and what remains speculative. Use a direct focus shortcut for the agent terminal, but make submission a separate key. Take ordinary breaks from both typing and reading; an agent's availability does not make continuous review sustainable. Reassess screen height, font size and keyboard position after any desk or chair change.

Back to blog