Two Computers, One Desk: Where Agent Inputs Go

The aluminium EM Mini Pad places a knurled rotary control beside five keys and supports either USB-C or Bluetooth. Dual mode does not establish that it can stay paired to two computers, switch between them instantly or use one mapping on both.

Which inputs should be per-machine and which shared?

Keep the main keyboard and approval actions clearly associated with the computer in front of you. Navigation controls may be shared when their destination is visible, such as focusing a terminal or moving between windows. Credentials, deployment shortcuts and destructive commands should remain machine-specific.

Label displays and terminals with host, project and branch. A pointer or keyboard that can roam between systems makes visible identity more important, not less.

How can one pad serve two computers?

The documented wired and Bluetooth connections provide two transport choices. Confirm in the actual manual or configurator whether the pad remembers more than one wireless host, how it changes mode and whether mappings are stored on the device. Do not assume a cable to one machine and Bluetooth to another creates a supported toggle.

A USB switch or KVM is another route, but it adds enumeration and focus behavior that must be tested. The simplest reliable layout may dedicate the pad to the computer that needs it most.

How do you avoid typing into the wrong machine?

Make switching a visible state change and require one action to switch, then another to issue a command. Never combine host selection with a terminal command or Enter in one macro. Test what happens when one computer sleeps, disconnects or rejects Bluetooth.

Use different desktop backgrounds, prompt colours or physical labels, while keeping accessibility and colour vision in mind. Read the hostname before any privileged action.

What does the minimal two-computer layout look like?

Give each computer a display region, ordinary keyboard route and separate task ledger. Share the pointer only if its current host is obvious. Use remote access instead of duplicated peripherals when one machine can safely act as a server and the other as its reviewed client.

The EM Mini Pad can provide a small set of reversible controls after its host behavior is verified. Start wired to one computer, map navigation only and add wireless use after testing reconnects, sleep and mode changes without live agent prompts. Keep per-host mappings in a written table and use the same physical key only when its action is safe on both systems. Different operating systems can interpret the same key code differently. Test from a key viewer on each host before binding apps, and remove access from a personal machine when company policy forbids shared peripherals or remote sessions.