When to use E2B
Use E2B when:- task work should run outside the Roomote host
- you want hosted sandboxes with snapshot support
- you can provide an E2B API key
- your deployment can reach E2B and E2B task sandboxes can reach Roomote
Configuration
Add E2B from Settings > Sandboxes with your API key, or provide the values as deployment env vars:DOCKER_WORKER_IMAGE or release derivation). You can also pin the
template as an env var:
E2B_DOMAIN only for self-hosted or custom E2B clusters. The default E2B
domain is enough for standard hosted E2B.
Worker template expectations
The E2B template should contain the Roomote worker runtime: system packages, browser tooling, language tools, command helpers, and the worker bootstrap used to connect back to Roomote. Settings and setup only collect the API key — not a template ID field. Roomote builds the template from the worker image during setup when needed. For production, keep the worker image or template version pinned so task startup is predictable.Verify setup
- save
E2B_API_KEY(and let Roomote provision the template, or setE2B_TEMPLATE_IDin the deployment env) - select E2B as the default sandbox provider
- start a small task from an environment
- confirm the task starts, streams logs, and can run project commands
- verify preview links if the task starts a web app
Common issues
- E2B reports a missing template. Confirm auto-provisioning finished, or
that
E2B_TEMPLATE_IDmatches a template available to the configured API key. - Tasks start with missing tools. Rebuild or refresh the worker template from the current Roomote worker image.
- Preview links fail. Confirm the deployment URL and preview proxy are reachable from hosted sandboxes.