Mish Ushakov
7296b2c55d
`Sandbox.connect` was attaching the data-plane envd headers
(`E2b-Sandbox-Id`, `E2b-Sandbox-Port`) to the control-plane `POST
/sandboxes/{id}/connect` call in both the sync and async SDKs. These
headers belong only on data-plane (filesystem/commands/pty) requests, so
this aligns the Python SDK with the JS SDK, which never sends them on
the connect call.
## Usage
No API change — `Sandbox.connect(sandbox_id)` (and the async equivalent)
behaves the same, just without the spurious headers on the control-plane
request.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
401 B
401 B
@e2b/python-sdk
| @e2b/python-sdk |
|---|
| patch |
fix(python-sdk): stop sending E2b-Sandbox-Id/E2b-Sandbox-Port headers on the control-plane connect request
Sandbox.connect was attaching the envd data-plane headers (E2b-Sandbox-Id, E2b-Sandbox-Port) to the POST /sandboxes/{id}/connect API call. These headers belong only on data-plane (filesystem/commands/pty) requests, matching the JS SDK behavior.