Created from #95 .
Currently, when starting a remote control session or deploying an agent, the public address to which it will connect is inferred from the address in the browser.
A new option (e.g. AgentConnectionUrl) could be added to the server config that will be passed to the agent to explicitly tell it which public address to use.
However, since the server is monolithic (UI, API, and hub served from a single backend), both the browser URL and AgentConnectionUrl would both still need to be routed to the same backend. Separating the two would be a large architecturally undertaking.