AGagentsky

Remote-harness relay WebSocket [write]

Changed on

WebSocket (Upgrade: websocket) served by the chat-proxy. The maker's ACP process connects with Authorization: Bearer hct_… (the per-harness connect token minted via POST /harnesses/{id}/connect-token). The relay validates the token, then opens a parallel WebSocket to the session's pod and splices both connections together, forwarding newline-delimited JSON-RPC frames in both directions. One live connection per session; a second attempt while one is open returns 409. The session must be ACTIVE and the pod RUNNING. Gated by the REMOTE_HARNESSES platform switch (off → 404).

get/sessions/{id}/harness

Request

  • Base URL
    https://api.agentsky.dev/v1
  • URL
    https://api.agentsky.dev/v1/sessions/{id}/harness
  • Auth
    HTTP bearer

Path parameters

idstring required

The session id

Response

Error — { error: { code, message, request_id } }

Changes