Agent InfrastructureAutomated release watch

@e2b/python-sdk@2.52.0

E2B released Python SDK v2.52.0, capping client-side sandbox fork counts to 20, aligning file ignore behaviors with Docker conventions, introducing HTTP version pinning, and improving HTTP/2 connection pooling and retry logic.

Human read

Why this signal matters

E2B has released version 2.52.0 of its Python SDK with several key updates across template building, network transport, and sandbox management: - Sandbox Forking : Client-side validation now restricts the count parameter in Sandbox.fork (and the CLI/JS equivalents) strictly to a range of 1–20 before issuing an API call. - Ignore Pattern Consistency : Template file copying now strictly aligns with Docker rules. Patterns matching directories exclude all sub-contents, leading slashes are ignored, ! re-includes paths, and brace expansion (e.g., {a,b} ) is no longer supported (must be declared separately). In Python, symlinks to directories are copied as links rather than recursively. Files hashes have been updated to omit directory sizes, triggering a one-time rebuild on subsequent runs for affected copy() steps. - Protocol Configuration : Introduces an http version client/connection option and E2B HTTP VERSION environment variable allowing users to force HTTP/1.1 over the default HTTP/2. - Resilience and Retries : Control-plane requests now automatically retry on 502, 503, and written network dropouts (excluding non-idempotent POST operations like creation/forking). Exponential backoff with jitter (0.1s to 10s) and Retry-After headers are respected. - HTTP/2 Connection Management : Replaces static shard-based connection pools with dynamic load balancing based on the fewest in-flight streams. Removed internal shard configurations ( E2B ENVD POOL SHARDS ).

Agent parse

Actionable summary

E2B Python SDK 2.52.0 enforces a client-side cap (1–20) on Sandbox.fork(count=...) , updates template copy ignore behavior to strictly match Docker (including .dockerignore precedence, directory exclusions, and removal of brace expansion), introduces HTTP/1.1 vs HTTP/2 pinning via http version / E2B HTTP VERSION , adds 502/503 retry handling, and balances sandbox HTTP/2 traffic based on in-flight stream counts…

Agent usefulness
77/100
Confidence
96%
Canonical data
JSON + Markdown
Next actions

What builders should check

  • Verify that any Sandbox.fork(count=...) invocations do not exceed 20.
  • Update any fileIgnorePatterns relying on brace expansion (e.g., .{env,pem} ) to specify each pattern separately.
  • Expect a one-time template rebuild for copy steps on the next build due to updated files hash calculations.
  • Remove any usage of deprecated internal shard settings ( E2B ENVD POOL SHARDS or transport shard arguments).
Classification

Tags and routing

sandboxcode-executionagents
Related signals

Continue the thread