Remote browser setup

Remote browser support lets the agent run headless browser tests in the same pod as the agent runtime. The browser server is exposed on localhost:3000, and the agent uses Docker/Docker Compose (via DinD) to run your test commands. Using the browser sidecar is recommended when possible because it lets you set dedicated pod resource limits for the browser container via AgentRuntime. This avoids running heavy browsers inside DinD and gives you predictable memory/CPU isolation for test workloads.

How it works

• The agent runtime pod includes a DinD container and a browser sidecar container.
• The agent runs Docker or Docker Compose inside DinD to build and run your app and test containers.
• Test containers connect to the sidecar on localhost:3000 using the appropriate protocol.

AgentRuntime browser configuration

Enable DinD and the browser sidecar in AgentRuntime:

spec:
  dind: true
  browser:
    enabled: true
    browser: chrome

Supported browser values include:

• chrome, chromium, firefox
• selenium-chrome, selenium-chromium, selenium-firefox, selenium-edge
• puppeteer
• custom

If you need a custom image, set browser: custom and supply a container that binds to port 3000:

spec:
  browser:
    enabled: true
    browser: custom
    container:
      name: browser
      image: selenium/standalone-chrome:144.0
      env:
      - name: SE_OPTS
        value: "--port 3000"