BoltKVM
Local network path

Use Thunderbolt Bridge for a two-Mac KVM connection.

BoltKVM can carry its authenticated input, clipboard, and file sessions over a Thunderbolt Bridge exposed by macOS. The same app-level trust and encryption apply whether the local path is Thunderbolt Bridge, Ethernet, or Wi-Fi.

See Automatic modeTroubleshoot discovery
First choice
Thunderbolt Bridge
Second
Ethernet
Third
Wi-Fi
Security
Authenticated each time

Automatic mode looks for the best available local path.

When Network Path is set to Automatic, BoltKVM prefers Thunderbolt Bridge, then Ethernet, then Wi-Fi. Nearby-device discovery identifies a candidate route; the saved device identity and public key still decide whether the peer is trusted.

Discovery is not authentication

Bonjour announcements and IP addresses are routing hints. They cannot turn an unknown Mac into a trusted peer. A session proceeds only after it proves the identity approved during pairing.

A path change starts a fresh session

If the active network path changes materially, BoltKVM releases current remote ownership, disconnects the old session, refreshes discovery, and reconnects through a newly authenticated path. It does not silently carry stale control across interfaces.

Choose a fixed path when predictability matters.

Automatic is the simplest default. You can instead select Thunderbolt Bridge, Ethernet, or Wi-Fi to constrain the local interface used for input sessions, or use Manual IP when discovery is unavailable.

A

Automatic

Uses the priority order and can recover after an address or interface change by discovering and authenticating the selected peer again.

T

Thunderbolt Bridge

Requires macOS to expose an available Thunderbolt Bridge interface on the path between the two Macs. BoltKVM does not create the macOS network service itself.

E/W

Ethernet or Wi-Fi

Useful when those interfaces match the desk network. Selecting a fixed path makes an unavailable interface visible instead of quietly choosing a different one.

IP

Manual address

Targets a peer address when Bonjour discovery is blocked. The peer must still authenticate as the trusted device; an address alone grants no control.

Build the rest of the desk workflow.

Input sharing
Share one keyboard and mouse in either direction
See the workflow →
Display topology
Arrange multiple screens around both Macs
See layouts →
Privacy
Understand local pairing, encryption, and data boundaries
Read the policy →

Thunderbolt network KVM FAQ.

Does Thunderbolt Bridge remove the need for pairing?
No. The transport and the trust model are separate. Both Macs still approve pairing, and every later session authenticates the saved peer identity.
Does BoltKVM require internet access?
No internet relay is required for product communication. The two Macs communicate over a local IP path.
Will Automatic mode always use Thunderbolt Bridge?
It prefers Thunderbolt Bridge when macOS exposes an available route. Otherwise it considers Ethernet, Wi-Fi, and other valid discovery results.
What if device discovery is blocked?
Check Local Network permission and the router or interface first. Manual IP can target the peer directly, but the connection still has to authenticate as the trusted Mac.

Keep the connection local and explicit.

Use Automatic for the shortest setup, or choose a fixed interface when the desk requires one.

Check requirementsOpen network support