clientGetWebSocketURL

Seen 1 time(s) in 1 run(s).

What it sent and what came back (the newest 1 from our runs)

Read from each run's own recording (rule 73), secrets and signed link tokens taken out. Kept in ~/.logCli/rea/clientFacts.json, so it stays after the run is pruned.

runs/inspect/20261103T065639_mattSlack, step 4: goto /client: 200, 556 ms

Sent:

{
  "query": {
    "_x_id": "noversion-1793689064.879",
    "_x_gantry": "true",
    "_x_desktop_ia": "4",
    "_x_version_ts": "1793684253",
    "_x_frontend_build_type": "current",
    "fp": "6f",
    "_x_num_retries": "0"
  },
  "body": {
    "------WebKitFormBoundary7CeHsXHg0E6AeAEi\r\nContent-Disposition: form-data; name": "\"token\"\r\n\r\nxoxc-12165421006739-12156263517591-12492529441700-5bffe6e6a317b9bbab53d938a4526d20e882de6ab372cd46f9f90868bb0322a0\r\n------WebKitFormBoundary7CeHsXHg0E6AeAEi\r\nContent-Disposition: form-data; name=\"_x_app_name\"\r\n\r\nclient\r\n------WebKitFormBoundary7CeHsXHg0E6AeAEi\r\nContent-Disposition: form-data; name=\"_x_sonic\"\r\n\r\ntrue\r\n------WebKitFormBoundary7CeHsXHg0E6AeAEi--\r\n"
  }
}

Answered:

{
  "ok": true,
  "primary_websocket_url": "wss://wss-primary.slack.com/",
  "fallback_websocket_url": "wss://wss-backup.slack.com/",
  "ttl_seconds": 604800,
  "routing_context": "T0C4VCD06MR-4"
}

What it does

Asks where to open the realtime socket: it answered primary_websocket_url: wss://wss-primary.slack.com/, fallback_websocket_url: wss://wss-backup.slack.com/, ttl_seconds: 604800 and routing_context: T0C4VCD06MR-4. Fired 7.1 s into step 4 (goto /client), 556 ms, 200.

What our machine does with it

Not called, but its answer matches what the watch action opens: gabriel builds the socket address itself from the fixed ws_base (wss://wss-primary.slack.com/) plus query parameters (vendor/gabrielSlack/gabriel/core/ws.py, core/metadata.py) and follows the reconnect_url frames Slack sends, so the engine never asks this endpoint (python/slackApi/engine.py, watch).

What can go wrong

If Slack moved the primary host, the fixed base would stop connecting and the watch would fail on the socket rather than on this call; ok: false here would carry an error such as not_authed. The recorded answer was 200 with ok: true.