USB, peripherals and monitors
Inspect the actual device before choosing a control method.
Reviewed 6 October 2026 · 2 min read
Import example project ↗Two named conversations, shared files, revisions and a preview.
Before you start
Storage, serial devices, MIDI and phones use different protocols. A USB-C connector does not imply unrestricted passthrough.
Screen actions must identify the display or application window. Mixed display scaling can affect coordinates.
Step by step
- Request an inventory on the intended computer.
- Select the device by identity, not list position.
- Use a supported protocol with only necessary access.
- Test a harmless action, disconnect/reconnect and revocation.
Try this
Example request
List my Windows monitors and identify the editor window. Capture only that window. Inspect the connected serial device’s identity before opening a session; do not send device commands yet.
Check the result
- Evidence identifies the correct device/window.
- Disconnecting invalidates its session clearly.
- Phone cables are not presented as generic USB tunnels.
If something goes wrong
Compatibility needs physical hardware tests. Simulated responses cannot establish it.
iOS accessories and installation depend on supported protocols, trust, entitlements and signing. Do not assume phone-to-phone signing is available.
Your screen may differ by platform and version. Check availability or get help.