[BUG] Cloudflare get_tunnel / list_tunnels always return connections: null since 2026-10-05 #8616

Describe the bug
Cloudflare removed the connections array from Cloudflare Tunnel list and get responses on October 5, 2026. From the Cloudflare changelog, July 9, 2026 (source):

Starting the same day, the connections array is removed from list and get responses for Cloudflare Tunnel and Cloudflare Mesh nodes (the cfd_tunnel and warp_connector API resources). Query the dedicated connections endpoint instead of reading the field off the tunnel or node object.

The same entry is on the API deprecations page with End of life date October 5, 2026. The requests keep succeeding, the field is just absent, so nothing errors.

Two tools read it off those responses:

• apps/sim/tools/cloudflare/get_tunnel.ts:81: connections: tunnel?.connections ?? null, (request is GET /accounts/{id}/cfd_tunnel/{tunnelId})
• apps/sim/tools/cloudflare/list_tunnels.ts:158: connections: tunnel.connections ?? null, (request is GET /accounts/{id}/cfd_tunnel)

Both tool descriptions still promise "active connector connections", so a workflow or agent will now get connections: null for every tunnel, including healthy ones.

To Reproduce

1. Run the cloudflare_get_tunnel tool against any tunnel that has a running connector.
2. status is healthy, but connections is null.

Expected behavior
connections contains the tunnel's active connections, as described in the tool output schema.

Additional context
The replacement is GET /accounts/{account_id}/cfd_tunnel/{tunnel_id}/connections. It returns a list of connectors (cloudflared instances), each with its own conns array (colo_name, origin_ip, opened_at, ...), so the old flat list is result.flatMap(c => c.conns ?? []).

Possible fixes:

• get_tunnel: make a second request to /cfd_tunnel/{tunnelId}/connections (or add a separate cloudflare_list_tunnel_connections tool) and fill connections from it.
• list_tunnels: one extra call per tunnel is probably not worth it; dropping the field or marking it as no longer populated (and pointing to status / the connections tool) keeps the output honest.

Checked against main at 36f060b.

I found this with a small scanner I'm building that checks public repos against upcoming platform deadlines (https://otisz.hu/api-sunset/). No sales pitch: if you'd prefer a PR instead of an issue, say so and I'll open one.

Ottó Misák