What happens if the agent loses its connection?

Connections drop — a flaky link, a reboot, an ISP hiccup. The agent is built to ride that out on its own: it reconnects automatically and brings your tunnels back without intervention.

Automatic reconnect with backoff

When the control connection drops, the agent waits briefly and dials the core again, retrying on a short backoff (a second or so at first, then a few seconds) with a little random jitter added. The jitter matters at scale: it stops a whole fleet of agents that lost the same uplink from reconnecting in lockstep and hammering the core at the same instant.

Tunnels come back automatically

The agent keeps its tunnel configuration across reconnect cycles, so once it is back online the tunnels reopen on their own — you don’t recreate anything. Any individual stream that was in flight when the link dropped returns an error to its TCP client, exactly as a momentary network blip would; you just reconnect that client and continue.

You see it happen, live

The panel shows the agent going offline and coming back in real time, pushed over the connection rather than polled — no refreshing to find out. That visibility is part of the design: you watch the drop and the recovery as they happen.