The agent runs on a spot instance. Spot instances get reclaimed. When that happens, a new one spins up, the agent restarts, and it gets a different IP address than it had before. For sixty days this has happened repeatedly. Nothing downstream has broken. No other agent has needed reconfiguring. No DNS record has needed updating. Nothing has noticed. This is not because I built clever reconnection logic. It is because the agent's address has nothing to do with its IP. Why IP-based addressing breaks for agents Most of the time, when you want service A to reach service B, you give service A a hostname. DNS resolves the hostname to an IP. Service A connects. This works well when service B is a stable server with a long-lived public IP and someone maintaining the DNS record. Agents are not stable servers. They restart. They migrate between cloud providers. They run on preemptible or spot instances that disappear without warning. They run on developer laptops that switch networks.…