CapabilitiesBuilt-in agents
Browser built in
A web browser (Chrome or Chromium) ready for an agent to drive.
Short answer: 8 of 16 providers offer it fully: Agent 37, Boat, InstaBox, Lizard, Runtime, Sandboxer, Tensorlake and boxd. With a catch: E2B and Morph. Checked 29 October 2026.
Who offers it
Part of Built-in agents, which explains why it matters.
Fully: Agent 37, Boat, boxd, InstaBox, Lizard, Runtime, Sandboxer and Tensorlake. With a catch: E2B and Morph. Not at all: Blaxel, Cloudflare Sandbox, Modal, Sprites and Vercel Sandbox.
- Agent 37Yes
Chromium and a browser tool ship in the Hermes template; other templates do not include a browser.
docs-confirmed “The stock `agent37-hermes` template includes a headless browser” Source
Chrome is preinstalled, with a browser-only stream and a desktop.
docs-confirmed “| `google-chrome-stable` | Chrome 151 |” Source
- boxdYes
`agent-browser` drives a Chromium build with anti-bot fingerprinting, and opens on the desktop.
docs-confirmed “the pre-installed `agent-browser`” Source
- InstaBoxYes
The default `agent-browser` template has a desktop and Chromium.
docs-confirmed “have a Linux desktop with a browser.” Source
- LizardYes
The `desktop` template has a graphical desktop; `desktop-camoufox` adds a Firefox build for scraping, in US East only.
docs-confirmed “`desktop-camoufox` is the `desktop` template plus Camoufox, a Firefox build for scraping that you drive with Playwright; it runs only in `us-east-1` for now.” Source
- RuntimeYes
One call starts Chromium and returns a CDP address for Playwright, Puppeteer or browser-use.
docs-confirmed “`sbx.browser.start()` runs Chromium in the sandbox. It returns `cdpUrl`, the address that Playwright, Puppeteer, browser-use and Stagehand connect to.” Source
- SandboxerYes
Every VM has Chrome installed, and the desktop shows it.
docs-confirmed “Every Sandboxer VM has Google Chrome installed.” Source
- TensorlakeYes
Chrome ships in the ubuntu-vnc image and is driven over CDP through a tunnel.
docs-confirmed “Run Google Chrome inside an ubuntu-vnc sandbox and drive it locally through the Chrome DevTools Protocol over a tunnel.” Source
- E2BWith a catch
The catch: A browser comes with the desktop image or through Kernel cloud browsers, not in the default sandbox image.
docs-confirmed “For **local browser automation** using a virtual desktop, see [Computer use](https://docs.e2b.dev/use-cases/computer-use.md).” Source
- MorphWith a catch
The catch: A documented example runs headless Chrome in a container, but no browser is installed for you.
docs-confirmed “runs two containerized services (a headless Chrome and an NGINX proxy)” Source
- BlaxelNo
Note: No browser is installed or offered; you would add Chrome to your own image.
Tutorials show code-server in a browser, not a browser in the sandbox.
inferred “Sandboxes are instant-launching virtual machines” Source
Note: The base images ship no browser; you install one in your own Dockerfile.
docs-confirmed “include none of them.” Source
- ModalNo
Note: No browser, desktop or computer-use API is documented; the sandbox is a headless container.
inferred “Sandboxes are useful for tasks like executing code generated by an LLM” Source
- SpritesNo
Note: No browser is installed or offered; a browser is something you run and reach through a proxy.
inferred “sprite proxy - Forward local ports through the remote server proxy” Source
Note: No browser is documented in the image or as an API; agents in the image are terminal tools.
inferred “coding agents, and common utilities.” Source
- DaytonaNot published
No browser is documented in the default image or the computer-use desktop; the docs describe the desktop, not what is installed in it.
docs-confirmed “Computer Use enables programmatic control of desktop environments within sandboxes.” Source
Related
Need several capabilities at once? Add more in the capability finder. Something wrong here? Use the report link at the bottom of the page.