Direct answer

How do I use an iPhone as a Mac controller?

Install the Mac menu bar agent, pair the phone controller, check the route, perform one task, and end the session.

Short answer

Use an iPhone as a Mac controller by installing the Remote Comp Mac menu bar agent on the host, pairing the phone from that trusted Mac, confirming the route, testing the first task, and ending or revoking access when the session is done. Keep the Mac app in Applications so operating-system permissions and updates stay attached to a stable path, and start pairing from the host that owns the work rather than from the phone. Before you rely on the session, record whether the route is Local Network nearby or a saved Private Mesh path away from the desk, and run the exact task you plan to perform so speed is measured on that route instead of assumed. When the work is finished, close the session and confirm the host is no longer being controlled, using the account, device, and operating-system permission paths to revoke access.

Install the host agent

Keep the Mac app in Applications so OS permissions and updates stay attached to a stable path.

Pair from the trusted host

Start the pairing flow from the Mac that owns the work. Enter or scan the code on the phone controller only after the host shows the setup path.

Run a route and latency check

Before relying on the session, record route state and test the exact task you plan to perform.

What it looks like

Mac setup screen showing the Remote Comp menu bar agent installation path.
Keep the installed app path stable so permissions and updates stay attached. How to install the Mac menu bar agent
Phone controller pairing screen with local code, QR setup, and route check.
Pairing should make the host, code, and route visible before the session. How to pair the phone controller
Route diagnostics screen showing local, private mesh, and relay route states.
Route state should be visible before latency or reliability claims are made. Local Network vs Private Mesh routes
Private Mesh route card showing trusted devices connected through controlled routing.
Private Mesh is for trusted away-from-desk workflows, not every possible network state. Local Network vs Private Mesh routes