Understand this story
Pydantic AI integrates E2B as a native sandbox provider. According to the official Pydantic AI article, after adding E2BSandbox() to the agent capability list, all shell commands and file operations execute in an isolated E2B microVM, and environment variables and SSH keys do not enter the sandbox. The sandbox can be paused after a run ends and resumed on the next run, with the filesystem and memory remaining unchanged, and it can be reused across processes via a credential-free reference identifier. The article gives two examples: one is a two-round run that pauses after diagnosis and then repairs; the other is, in a Temporal workflow, after the worker is killed, a new worker continues and completes the repair in the same sandbox. This capability is currently provided as a native option.
AI-generated from public reports
Latest development · Report
Pydantic AI integrates E2B sandbox as a native capabilityDevelopments
1 confirmed developments
- Source:English text is being prepared.
Reports and discussion timeline
Browse reports and discussion by time. Their evidence levels remain distinct.
Oct 22
Pydantic AI official articleFirst-partySelected
Pydantic AI integrates E2B sandbox as a native capability
Pydantic AI integrates E2B as a native sandbox provider. After adding E2BSandbox() to the agent's capability list, all shell commands and file operations are executed in an isolated E2B microVM, and environment variables and SSH keys do not enter the sandbox. The sandbox can be paused after a run ends and resumed on the next run, with the filesystem and memory remaining unchanged, and can be reused across processes via a credential-free reference identifier. The article gives two examples: one is a two-round run of diagnose, pause, then fix; the other is killing a worker in a Temporal workflow and having a new worker continue and complete the fix in the same sandbox.