AI Agent News/stories/e2b-releases-version-2-57-0-with-a-tls-option-for-egress-proxies.md

Infrastructure

E2B releases version 2.57.0 with a TLS option for egress proxies

E2B has released e2b@2.57.0, which adds a TLS setting to egress proxy options. The release also includes a protobuf dependency bump and several internal refactors.

Source: github.com/e2b-dev/E2B/releases/tag/e2b%402.57.0

E2B has released e2b@2.57.0. The minor change adds a tls option to the egress proxy settings, which accepts either true or an object with optional serverName and caCert fields. In Python, these are exposed as server_name and ca_cert.

The getInfo and get_info calls now report the TLS setting, but they do not return the CA certificate.

Patch-level changes bump @bufbuild/protobuf to ^2.16.0 and share the process kill implementation between commands and PTY. The CLI's --language option parser is now shared between template init and template migrate, and unused internal exports were removed.

Why it matters if you build agents

If your agents send outbound traffic through an egress proxy that needs a custom CA or a server name, you can now set that in the E2B options instead of working around it.

Call getInfo or get_info to confirm the TLS setting is applied, keeping in mind that the CA certificate is not returned.

The other changes are internal refactors and a dependency update, so they are unlikely to need action in your code.

Get stories like this every weekday

One short email with the day's agent tooling news.

Subscribe