pypi / e2b-code-interpreter
e2b-code-interpreter
What changed in e2b-code-interpreter 1 to 2, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-19.
7 breaking4 new APIs and options3 behavior and defaults1 tooling
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli inite2b-code-interpreter 213 changes
Breaking changes 5
The synchronous Python SDK now creates sandboxes with the class method Sandbox.create() instead of instantiating Sandbox().
Python single-file writes now use sandbox.files.write() instead of sandbox.write().
Python multiple-file writes now use sandbox.files.write_files() instead of the overloaded write() method.
Sandbox listing now uses pagination; callers obtain a paginator and fetch items through it.
Sandboxes are secure by default, so accessing the sandbox controller URL requires an authentication header; the SDK handles the header automatically.
New APIs and options 4
Parses an existing Dockerfile and builds a template from it; only a limited set of Dockerfile instructions is supported.
Uses an already-built Docker image as the base for a template.
Parses an existing Dockerfile and builds a template from it; only a limited set of Dockerfile instructions is supported.
Uses an already-built Docker image as the base for a template.
Behavior and default changes 3
The default template user is user, with the working directory set to that user's home directory, unlike Docker defaults.
Docker images used with fromImage must be built for the linux/amd64 platform.
Set secure to false during sandbox creation to temporarily disable secure communication.
Tooling 1
Migrates an existing template definition to the new format and generates SDK template and development and production build files.
e2b-code-interpreter 12 changes
Breaking changes 2
The V1 build command is a deprecation stub that exits immediately; migrate to the V2 build system.
This is the current V2 build command and authenticates with E2B_API_KEY instead of the access token.