Custom Sandbox Templates

Operator builds a custom sandbox template (e2b.Dockerfile / e2b.toml) that pre-installs the workload's dependencies so fresh sandboxes start ready.

Bake stable dependencies and setup into a custom template so each sandbox starts pre-provisioned instead of installing at runtime. Pin versions in the template for reproducibility. Reference the template by its name/id when creating sandboxes. [REQUIRES-VERIFICATION] for the exact template config f…

A template defines a start command that boots a service. The agent creates a sandbox and immediately connects to the service before it is up.

If the template launches a service at startup, wait for an explicit readiness signal (health check / port-listening poll) before sending traffic — sandbox creation completing does not guarantee the in-VM service is accepting connections. Encode readiness as a check, not a fixed sleep. [REQUIRES-VER…

Operator wants the template to have an API token available, so they ADD it as a literal value in the template Dockerfile / build args.

Never bake secrets into the template image — image layers and build history can leak them and the same image is reused across many sandboxes. Inject secrets at sandbox runtime (env vars at create, or a mounted file) so they are not part of the shared, persisted template. Keep only non-sensitive set…