Pistis
API referenceFollowing

Read where its sandbox is

GET
/sessions/{id}/sandbox

Reading it never starts, resumes or replaces a sandbox.

Authorization

bearer
headerAuthorizationBearer <token>

An API token

Path Parameters

id*string

A session id

Response Body

The sandbox's state

application/json
  1. response
generation*integer

Counts sandboxes this session had

state*unknown
Example Request
curl -X GET 'http://127.0.0.1:7777/sessions/ses_6c1f2a0b9d3e4f5a6b7c/sandbox'
Example Response
{  "generation": 0,  "state": "missing"}

List subagent sessions GET

The sessions its `subagent` steps started.

Watch the sandbox's screen GET

`multipart/x-mixed-replace; boundary=pistis-frame`, for as long as you read it. Each part is a picture (`image/jpeg`, with `X-Screen-Width` and `X-Screen-Height` when known), sent only when the screen changed, or `application/json` `{"none": "<why>"}` while there is no picture (no browser open yet, the agent isn't using the sandbox). The sandbox makes pictures only while someone watches; a slow reader gets the newest picture, never a backlog. Nothing is recorded. Whoever may read the session may watch it.