Skip to main content
Runs programs in an E2B cloud sandbox. Settings and notes: E2B.

Install

Usage

captures defaults to @external: every program Mirage does not have itself. Name @python to run Python in the sandbox too.
In a browser, import @struktoai/mirage-core/machine/e2b/handle once to register the provider (pnpm add @struktoai/mirage-core), pass apiKey, and use mountType: 'own' or leave it unset.

Connecting the workspace

Pick a mount_type. ssh, mirage and both do not work in browsers. Under ssh each file call is about 150 ms for a small file from a laptop; under mirage, files on ram and sql mounts stay cached in the sandbox once read, unless a policy judges the session’s file calls, and E2B’s base template is enough: it has fuse3 and npm, and Mirage installs mirage-fuse there the first time. With own, base the template on the machine image and run mirage workspace create /tmp/sandbox.yaml in the sandbox.

A template for ssh

Build a template with sshfs and pass its sandbox ID as sandbox_id:

In a browser

Import the E2B machine from core (pnpm add @struktoai/mirage-core), which also registers the e2b provider for machines:, and pass apiKey:
Keep account keys out of shared frontend bundles; have your backend authenticate the app. mountType ssh, mirage and both need Node, so a browser uses own or none.