Tunnel Client Disconnect

The Mac client reports WHY its tunnel dropped — the server only ever sees a generic 1006 on the socket, which can't distinguish a NAT/TCP drop from the client's own watchdog force-reconnect (ping_failed) or a graceful redeploy. Logged to infra_events so /admin/relay-health can break churn down by the real client-side cause (LMCA cloud-relay churn investigation, 2026-06-05).

post/tunnel/client-disconnect

Request

  • Base URL: https://api.local-mcp.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.local-mcp.com/tunnel/client-disconnect
  • Auth: none declared

Request body

machine_idstring
reasonstring
detailstring
session_secondsnumber

Response

Successful Response

unknown required

Changes

No recorded changes to this operation across all 1 revision of this API.