Live browser view of an in-flight run (WebSocket)
Mirrors /api/authoring/:id/live but for an ORDINARY run of a published automation (not a demonstration): while a synchronous run dispatched via POST /v1/run/:flow, MCP, or the Playground is in flight, this socket relays its CDP screencast. Registered per-run and torn down when the run ends. Queue-dispatched runs execute on a separate worker process with no shared memory, so no frame is ever relayed for those. Read-only relay; same session-cookie + Origin-allowlist auth as /live.
承認
The dashboard's signed, HttpOnly session cookie (packages/service/src/auth.ts): base64url(payload).base64url(hmac-sha256), absolute 30-day lifetime, SameSite=Lax, Secure on any TLS deployment. Minted by POST /api/auth/signup or POST /api/auth/login (or, outside production, auto-provisioned by GET /api/session). Because it is HttpOnly, it cannot be read or attached by a browser-based API-reference "Try it" panel across origins — exercise these routes with a real logged-in browser session or a cookie-jar HTTP client.
パスパラメータ
The automation id.
レスポンス
Switching Protocols — the connection is now a WebSocket relaying JSON frames of screencast data.