@e2b/python-sdk@2.51.0
E2B Python SDK 2.51.0 delegates default configurations to the API, migrates sandbox operations to v2 endpoints, and deprecates the secure option.
Why this signal matters
E2B released @e2b/python-sdk@2.51.0. The release stops sending SDK-side default parameters in API payloads, allowing the backend API to govern omitted options. This affects sandbox create, fork, connect (previously defaulting to 5-minute timeout), fork (count: 1), create (allow internet access), pause (keep memory), and template builds (CPU/memory presets); explicitly passed values remain unaffected. Sandbox creation and connection now target v2 endpoints (POST /v2/sandboxes and POST /v2/sandboxes/{id}/connect), which automatically secure envd access and default timeouts to 5 minutes. As a result, the secure option in Sandbox.create is deprecated and ignored. Additionally, client-side validation for the fork count argument has been removed in favor of API-side validation.
Actionable summary
E2B Python SDK 2.51.0 updates Sandbox.create and connect to use v2 API endpoints, removes client-side request defaults, removes client-side fork count validation, and deprecates the secure flag.
- Agent usefulness
- 94/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- Remove usage of the deprecated secure parameter in Sandbox.create calls.
- Verify whether any workflows relied on client-side default values for sandbox create, fork, connect, pause, or template build configurations.