AgentHost
Live View Network Requirements
The browser live view and human takeover stream video directly from your agent's VM to your browser over WebRTC. That direct connection has network requirements on the viewer's side.
What The Live View Needs
Your browser must be able to establish a WebRTC connection to the agent VM. AgentHost first attempts the most direct media path and uses authenticated TURN relay fallback when restrictive networks prevent a direct connection.
Networks That Commonly Block It
Corporate firewalls and proxies that block outbound UDP, restrictive guest Wi-Fi, some VPNs, and a few mobile carriers with strict NAT can prevent the peer connection. In those networks the live view shows a connection failure even though the session itself is healthy.
What You Can Do
Try a different network (for example a mobile hotspot or a network without a corporate proxy), disable a VPN if one is active, or ask your network administrator to allow outbound UDP for WebRTC. The failure is on the viewing network, not on your agent.
Everything Else Keeps Working
Only the live video stream is affected. API control of the session, navigation commands, screenshots, recordings, and artifacts work regardless of your network, so you can keep operating the browser session through the API while the live view is unavailable.