E2B

E2BRuntime connects to a live E2B sandbox by id. Create it with E2B’s CLI or SDK from a template carrying Mirage and fuse3, then provision the workspace inside it. Mirage only connects and executes; it never creates, starts, stops, or deletes the sandbox. See the Sandbox overview for the shared image and matching mount-prefix setup. The in-sandbox mount is served by the Python Mirage build for both SDKs.

Install

pnpm add e2b

Configure

runtimes:
  - name: e2b
    captures: ["python3", "pip"]
    config:
      sandboxId: ${E2B_SANDBOX_ID}
      apiKey: ${E2B_API_KEY}
  - vfs

apiKey is optional when E2B_API_KEY is set. The runtime connects on the first captured line and reuses the sandbox client until the workspace closes. Closing the workspace releases the client and leaves the sandbox running. The same configuration in application code is:

import { E2BRuntime } from '@struktoai/mirage-node'

const runtime = new E2BRuntime({
  captures: ['python3', 'pip'],
  config: { sandboxId: 'sandbox-id' },
})

Templates, CPU and memory sizing, networking, and lifecycle controls remain E2B settings.

Mirage timeouts stop waiting rather than terminating the remote process. E2B also applies its SDK command timeout, currently 60 seconds by default, to both runaway and legitimate long-running commands. See Resource limits.

Getting Started

Agents

Resources

CLIs

Watch

Runtimes

Install

Configure

​Install

​Configure

Install

Configure