Remote debugging without proximity: your device and your AI tool each make their own outbound connection, so they can sit on different networks, in different cities, or on different continents.
Most device debugging assumes you are standing next to the device: same Wi-Fi, a USB cable, or a manually forwarded port. OmniDebugLink removes that assumption. Your app and your AI coding tool each connect to a global edge network from wherever they are, and traffic between them is relayed over the internet. The device can be in another office, another city, or another time zone — what you see is what is on screen, wherever the screen is.
Nothing listens on the device. The SDK inside your app opens one outbound WebSocket and keeps it alive; your AI tool talks to the MCP endpoint after an account sign-in. Because both ends dial out, no shared LAN, USB tethering, port forwarding, or public address is ever needed — the link works wherever ordinary outbound internet access is allowed.
device → wss://api.omnidebuglink.dev/ws?token=<clientToken> (outbound WebSocket) AI tool → https://api.omnidebuglink.dev/mcp (account sign-in, no token to copy)
The link is built to survive real-world networks. The SDK sends a heartbeat roughly every 55 seconds; if the service stays silent for 180 seconds, a watchdog drops the connection and the SDK reconnects automatically with exponential backoff (1 s doubling up to a 30 s cap), then re-announces its capabilities. Brief outages heal themselves instead of ending the session.
When you create a token pair in the console you pick the region closest to your device, and relays run across 11 global regions, so the round trip stays short no matter where you and the device are. One token pair belongs to exactly one device — if a second instance connects with the same token, it replaces the first, so give each device its own token pair.
The wire protocol defines built-in connectivity tasks every client implements, so you can verify a remote link in seconds — echo proves the round trip, ping measures it:
echo {"text":"hi"} → {"echo":"hi"}
ping {"sentAt":<ms>} → round-trip time computed by the service
The outbound connection, heartbeat, and reconnect logic are built into all 7 official SDKs — the same one-line start(clientToken) call on Unity, Android, iOS / macOS, Flutter, React Native, Godot, and Web (JavaScript).