E2B: agent building features and setup

Overview

E2B suits agents that need to run code, browse, or use tools in an isolated environment rather than on an employee’s computer. Each run can be assigned a short-lived machine with limited permissions. This lets you test a script or retrieve a webpage without opening the internal network. Before connecting it to production, define which commands are allowed, how long the machine runs, and what is retained after the agent finishes.

Features

• An isolated machine for each agent run
• Run code and browse within the environment
• Connect tools without running them on an employee’s computer

Business uses

• An agent that runs a test script on a file uploaded by a user
• Retrieving data from a public website without accessing the organizational network

Getting started

• Run an official example in a test machine without organizational secrets.
• Restrict network access, runtime, and permitted commands.
• Check a failed run and what remains on the machine after shutdown.

What to check

• Machine isolation depends on the permissions granted to the agent’s code.
• Do not pass production keys into the environment without a secrets management mechanism.