Bytebot SOP

Appearance

Test ​

Status: SANDBOX-NEEDED ​

Bytebot runs in a containerized Linux desktop environment and automates the desktop with computer vision. It cannot safely run without an isolated Docker environment that includes a virtual display.

Why this was not tested ​

Bytebot requires Docker Compose to spin up a full virtual Linux desktop with a VNC/display server. It controls the desktop via mouse and keyboard simulation. Running it against a host machine without an isolated container poses risk of unintended desktop control. The test was not executed.

What is required ​

  • Docker Desktop with Compose support
  • Sufficient RAM (the container includes a full Linux desktop runtime)
  • An AI provider API key (Anthropic or OpenAI)
  • No host display is needed; the container provides its own virtual display

Smoke test procedure (inside isolated Docker environment) ​

Step 1: Start the stack

bash
docker-compose -f docker/docker-compose.yml up -d

Step 2: Confirm containers are running

bash
docker-compose -f docker/docker-compose.yml ps

All containers must show Up status. If any show Exit or Restarting, pull logs:

bash
docker-compose -f docker/docker-compose.yml logs -f bytebot-agent

Step 3: Desktop API health check

bash
curl -X POST http://localhost:9990/computer-use \
  -H "Content-Type: application/json" \
  -d '{"action": "screenshot"}'

Expected output: A JSON response with "type": "image" and a non-empty base64 data field. Any response matching this structure confirms the virtual desktop is alive.

Step 4: Agent API health check

bash
curl http://localhost:9991/tasks

Expected output:

json
[]

A 200 OK with valid JSON confirms the agent service is up.

Step 5: Tasks UI

Open http://localhost:9992 in a browser. The Bytebot task creation interface should load with no console errors.

Do not use until ​

An isolated Docker environment with a virtual display is provisioned and no host desktop is exposed to the container.