Skip to main content

AsyncSandbox

E2B cloud sandbox is a secure and isolated cloud environment. The sandbox allows you to:
  • Access Linux OS
  • Create, list, and delete files and directories
  • Run commands
  • Run isolated code
  • Access the internet
Check docs here. Use the AsyncSandbox.create() to create a new sandbox. Example:

files

Module for interacting with the sandbox filesystem.

commands

Module for running commands in the sandbox.

pty

Module for interacting with the sandbox pseudo-terminal.

__init__

Use AsyncSandbox.create() to create a new sandbox instead.

is_running

Check if the sandbox is running. Arguments:
  • request_timeout: Timeout for the request in seconds
Returns: True if the sandbox is running, False otherwise Example

create

Create a new sandbox. By default, the sandbox is created from the default base sandbox template. Arguments:
  • template: Sandbox template name or ID
  • timeout: Timeout for the sandbox in seconds, default to 300 seconds. The maximum time a sandbox can be kept alive is 24 hours (86_400 seconds) for Pro users and 1 hour (3_600 seconds) for Hobby users.
  • metadata: Custom metadata for the sandbox
  • envs: Custom environment variables for the sandbox
  • secure: Envd is secured with access token and cannot be used without it, defaults to True.
  • allow_internet_access: Allow sandbox to access the internet, defaults to True.
  • mcp: MCP server to enable in the sandbox
Returns: A Sandbox instance for the new sandbox Use this method instead of using the constructor to create a new sandbox.

connect

Connect to a sandbox. If the sandbox is paused, it will be automatically resumed. Sandbox must be either running or be paused. With sandbox ID you can connect to the same sandbox from different places or environments (serverless functions, etc). Arguments:
  • timeout: Timeout for the sandbox in seconds
Returns: A running sandbox instance @example

connect

Connect to a sandbox. If the sandbox is paused, it will be automatically resumed. Sandbox must be either running or be paused. With sandbox ID you can connect to the same sandbox from different places or environments (serverless functions, etc). Arguments:
  • sandbox_id: Sandbox ID
  • timeout: Timeout for the sandbox in seconds
Returns: A running sandbox instance @example

connect

Connect to a sandbox. If the sandbox is paused, it will be automatically resumed. Sandbox must be either running or be paused. With sandbox ID you can connect to the same sandbox from different places or environments (serverless functions, etc). Arguments:
  • timeout: Timeout for the sandbox in seconds
Returns: A running sandbox instance @example

kill

Kill the sandbox. Returns: True if the sandbox was killed, False if the sandbox was not found

kill

Kill the sandbox specified by sandbox ID. Arguments:
  • sandbox_id: Sandbox ID
Returns: True if the sandbox was killed, False if the sandbox was not found

kill

Kill the sandbox specified by sandbox ID. Returns: True if the sandbox was killed, False if the sandbox was not found

set_timeout

Set the timeout of the sandbox. After the timeout expires, the sandbox will be automatically killed. This method can extend or reduce the sandbox timeout set when creating the sandbox or from the last call to .set_timeout. The maximum time a sandbox can be kept alive is 24 hours (86_400 seconds) for Pro users and 1 hour (3_600 seconds) for Hobby users. Arguments:
  • timeout: Timeout for the sandbox in seconds

set_timeout

Set the timeout of the specified sandbox. After the timeout expires, the sandbox will be automatically killed. This method can extend or reduce the sandbox timeout set when creating the sandbox or from the last call to .set_timeout. The maximum time a sandbox can be kept alive is 24 hours (86_400 seconds) for Pro users and 1 hour (3_600 seconds) for Hobby users. Arguments:
  • sandbox_id: Sandbox ID
  • timeout: Timeout for the sandbox in seconds

set_timeout

Set the timeout of the specified sandbox. After the timeout expires, the sandbox will be automatically killed. This method can extend or reduce the sandbox timeout set when creating the sandbox or from the last call to .set_timeout. The maximum time a sandbox can be kept alive is 24 hours (86_400 seconds) for Pro users and 1 hour (3_600 seconds) for Hobby users. Arguments:
  • timeout: Timeout for the sandbox in seconds

get_info

Get sandbox information like sandbox ID, template, metadata, started at/end at date. Returns: Sandbox info

get_info

Get sandbox information like sandbox ID, template, metadata, started at/end at date. Arguments:
  • sandbox_id: Sandbox ID
Returns: Sandbox info

get_info

Get sandbox information like sandbox ID, template, metadata, started at/end at date. Returns: Sandbox info

get_metrics

Get the metrics of the current sandbox. Arguments:
  • start: Start time for the metrics, defaults to the start of the sandbox
  • end: End time for the metrics, defaults to the current time
Returns: List of sandbox metrics containing CPU, memory and disk usage information

get_metrics

Get the metrics of the sandbox specified by sandbox ID. Arguments:
  • sandbox_id: Sandbox ID
  • start: Start time for the metrics, defaults to the start of the sandbox
  • end: End time for the metrics, defaults to the current time
Returns: List of sandbox metrics containing CPU, memory and disk usage information

get_metrics

Get the metrics of the current sandbox. Arguments:
  • start: Start time for the metrics, defaults to the start of the sandbox
  • end: End time for the metrics, defaults to the current time
Returns: List of sandbox metrics containing CPU, memory and disk usage information

beta_create

[BETA] This feature is in beta and may change in the future. Create a new sandbox. By default, the sandbox is created from the default base sandbox template. Arguments:
  • template: Sandbox template name or ID
  • timeout: Timeout for the sandbox in seconds, default to 300 seconds. The maximum time a sandbox can be kept alive is 24 hours (86_400 seconds) for Pro users and 1 hour (3_600 seconds) for Hobby users.
  • auto_pause: Automatically pause the sandbox after the timeout expires. Defaults to False.
  • metadata: Custom metadata for the sandbox
  • envs: Custom environment variables for the sandbox
  • secure: Envd is secured with access token and cannot be used without it, defaults to True.
  • allow_internet_access: Allow sandbox to access the internet, defaults to True.
  • mcp: MCP server to enable in the sandbox
Returns: A Sandbox instance for the new sandbox Use this method instead of using the constructor to create a new sandbox.

beta_pause

[BETA] This feature is in beta and may change in the future. Pause the sandbox. Returns: Sandbox ID that can be used to resume the sandbox

beta_pause

[BETA] This feature is in beta and may change in the future. Pause the sandbox specified by sandbox ID. Arguments:
  • sandbox_id: Sandbox ID
Returns: Sandbox ID that can be used to resume the sandbox

beta_pause

[BETA] This feature is in beta and may change in the future. Pause the sandbox. Returns: Sandbox ID that can be used to resume the sandbox

get_mcp_token

Get the MCP token for the sandbox. Returns: MCP token for the sandbox, or None if MCP is not enabled.

AsyncSandboxPaginator

Paginator for listing sandboxes. Example:

next_items

Returns the next page of sandboxes. Call this method only if has_next is True, otherwise it will raise an exception. Returns: List of sandboxes

AsyncWatchHandle

Handle for watching a directory in the sandbox filesystem. Use .stop() to stop watching the directory.

stop

Stop watching the directory.

Filesystem

Module for interacting with the filesystem in the sandbox.

read

Read file content as a str. Arguments:
  • path: Path to the file
  • user: Run the operation as this user
  • format: Format of the file content—text by default
  • request_timeout: Timeout for the request in seconds
Returns: File content as a str

read

Read file content as a bytearray. Arguments:
  • path: Path to the file
  • user: Run the operation as this user
  • format: Format of the file content—bytes
  • request_timeout: Timeout for the request in seconds
Returns: File content as a bytearray

read

Read file content as a AsyncIterator[bytes]. Arguments:
  • path: Path to the file
  • user: Run the operation as this user
  • format: Format of the file content—stream
  • request_timeout: Timeout for the request in seconds
Returns: File content as an AsyncIterator[bytes]

write

Write content to a file on the path. Writing to a file that doesn’t exist creates the file. Writing to a file that already exists overwrites the file. Writing to a file at path that doesn’t exist creates the necessary directories. Arguments:
  • path: Path to the file
  • data: Data to write to the file, can be a str, bytes, or IO.
  • user: Run the operation as this user
  • request_timeout: Timeout for the request in seconds
Returns: Information about the written file

write_files

Writes multiple files. Writes a list of files to the filesystem. When writing to a file that doesn’t exist, the file will get created. When writing to a file that already exists, the file will get overwritten. When writing to a file that’s in a directory that doesn’t exist, you’ll get an error. Arguments:
  • files: list of files to write as WriteEntry objects, each containing path and data
  • user: Run the operation as this user
  • request_timeout: Timeout for the request
Returns: Information about the written files

list

List entries in a directory. Arguments:
  • path: Path to the directory
  • depth: Depth of the directory to list
  • user: Run the operation as this user
  • request_timeout: Timeout for the request in seconds
Returns: List of entries in the directory

exists

Check if a file or a directory exists. Arguments:
  • path: Path to a file or a directory
  • user: Run the operation as this user
  • request_timeout: Timeout for the request in seconds
Returns: True if the file or directory exists, False otherwise

get_info

Get information about a file or directory. Arguments:
  • path: Path to a file or a directory
  • user: Run the operation as this user
  • request_timeout: Timeout for the request in seconds
Returns: Information about the file or directory like name, type, and path

remove

Remove a file or a directory. Arguments:
  • path: Path to a file or a directory
  • user: Run the operation as this user
  • request_timeout: Timeout for the request in seconds

rename

Rename a file or directory. Arguments:
  • old_path: Path to the file or directory to rename
  • new_path: New path to the file or directory
  • user: Run the operation as this user
  • request_timeout: Timeout for the request in seconds
Returns: Information about the renamed file or directory

make_dir

Create a new directory and all directories along the way if needed on the specified path. Arguments:
  • path: Path to a new directory. For example ‘/dirA/dirB’ when creating ‘dirB’.
  • user: Run the operation as this user
  • request_timeout: Timeout for the request in seconds
Returns: True if the directory was created, False if the directory already exists

watch_dir

Watch directory for filesystem events. Arguments:
  • path: Path to a directory to watch
  • on_event: Callback to call on each event in the directory
  • on_exit: Callback to call when the watching ends
  • user: Run the operation as this user
  • request_timeout: Timeout for the request in seconds
  • timeout: Timeout for the watch operation in seconds. Using 0 will not limit the watch time
  • recursive: Watch directory recursively
Returns: AsyncWatchHandle object for stopping watching directory

Commands

Module for executing commands in the sandbox.

list

Lists all running commands and PTY sessions. Arguments:
  • request_timeout: Timeout for the request in seconds
Returns: List of running commands and PTY sessions

kill

Kill a running command specified by its process ID. It uses SIGKILL signal to kill the command. Arguments:
  • pid: Process ID of the command. You can get the list of processes using sandbox.commands.list()
  • request_timeout: Timeout for the request in seconds
Returns: True if the command was killed, False if the command was not found

send_stdin

Send data to command stdin. :param pid Process ID of the command. You can get the list of processes using sandbox.commands.list(). :param data: Data to send to the command :param request_timeout: Timeout for the request in seconds

run

Start a new command and wait until it finishes executing. Arguments:
  • cmd: Command to execute
  • background: False if the command should be executed in the foreground, True if the command should be executed in the background
  • envs: Environment variables used for the command
  • user: User to run the command as
  • cwd: Working directory to run the command
  • on_stdout: Callback for command stdout output
  • on_stderr: Callback for command stderr output
  • stdin: If True, the command will have a stdin stream that you can send data to using sandbox.commands.send_stdin()
  • timeout: Timeout for the command connection in seconds. Using 0 will not limit the command connection time
  • request_timeout: Timeout for the request in seconds
Returns: CommandResult result of the command execution

run

Start a new command and return a handle to interact with it. Arguments:
  • cmd: Command to execute
  • background: False if the command should be executed in the foreground, True if the command should be executed in the background
  • envs: Environment variables used for the command
  • user: User to run the command as
  • cwd: Working directory to run the command
  • on_stdout: Callback for command stdout output
  • on_stderr: Callback for command stderr output
  • stdin: If True, the command will have a stdin stream that you can send data to using sandbox.commands.send_stdin()
  • timeout: Timeout for the command connection in seconds. Using 0 will not limit the command connection time
  • request_timeout: Timeout for the request in seconds
Returns: AsyncCommandHandle handle to interact with the running command

connect

Connects to a running command. You can use AsyncCommandHandle.wait() to wait for the command to finish and get execution results. Arguments:
  • pid: Process ID of the command to connect to. You can get the list of processes using sandbox.commands.list()
  • request_timeout: Request timeout in seconds
  • timeout: Timeout for the command connection in seconds. Using 0 will not limit the command connection time
  • on_stdout: Callback for command stdout output
  • on_stderr: Callback for command stderr output
Returns: AsyncCommandHandle handle to interact with the running command

Pty

Module for interacting with PTYs (pseudo-terminals) in the sandbox.

kill

Kill PTY. Arguments:
  • pid: Process ID of the PTY
  • request_timeout: Timeout for the request in seconds
Returns: true if the PTY was killed, false if the PTY was not found

send_stdin

Send input to a PTY. Arguments:
  • pid: Process ID of the PTY
  • data: Input data to send
  • request_timeout: Timeout for the request in seconds

create

Start a new PTY (pseudo-terminal). Arguments:
  • size: Size of the PTY
  • on_data: Callback to handle PTY data
  • user: User to use for the PTY
  • cwd: Working directory for the PTY
  • envs: Environment variables for the PTY
  • timeout: Timeout for the PTY in seconds
  • request_timeout: Timeout for the request in seconds
Returns: Handle to interact with the PTY

resize

Resize PTY. Call this when the terminal window is resized and the number of columns and rows has changed. Arguments:
  • pid: Process ID of the PTY
  • size: New size of the PTY
  • request_timeout: Timeout for the request in seconds

AsyncCommandHandle

Command execution handle. It provides methods for waiting for the command to finish, retrieving stdout/stderr, and killing the command.

pid

Command process ID.

stdout

Command stdout output.

stderr

Command stderr output.

error

Command execution error message.

exit_code

Command execution exit code. 0 if the command finished successfully. It is None if the command is still running.

disconnect

Disconnects from the command. The command is not killed, but SDK stops receiving events from the command. You can reconnect to the command using sandbox.commands.connect method.

wait

Wait for the command to finish and return the result. If the command exits with a non-zero exit code, it throws a CommandExitException. Returns: CommandResult result of command execution

kill

Kills the command. It uses SIGKILL signal to kill the command Returns: True if the command was killed successfully, False if the command was not found

SandboxApi

list

List all running sandboxes. Arguments:
  • query: Filter the list of sandboxes by metadata or state, e.g. SandboxListQuery(metadata={"key": "value"}) or SandboxListQuery(state=[SandboxState.RUNNING])
  • limit: Maximum number of sandboxes to return per page
  • next_token: Token for pagination
Returns: List of running sandboxes