feat(python-sdk): add logger option for request/debug logging

[mishushakov]

Adds a logger option (a standard library logging.Logger) to Sandbox.create/AsyncSandbox.create and the static Sandbox.connect(sandbox_id, ...), wired into the API client, the envd client, the volume content client, and the RPC (ConnectRPC) path. The logger is stored on the sandbox and propagates to all of its later operations — including control-plane calls like kill/pause/set_timeout/get_info (via get_api_params) — so logging keeps working after construction; mirroring the JS SDK, logger is a construction-time option and not a public per-request parameter those methods accept from the caller, and nothing is logged unless a logger is supplied. The stdlib logging.Logger is used directly as the adapter (no ported JS Logger interface), and log levels match JS: requests at INFO, successful API and unary RPC responses at INFO, streamed RPC messages at DEBUG, failed API responses (status >= 400) at ERROR. The always-on module-level (e2b.*) request logging at the transport layer was removed in favor of this opt-in client-layer logging, and volume content operations continue to accept logger per call via VolumeApiParams to match the JS Volume API. Includes a changeset and unit tests in tests/test_logging_option.py.

Usage

import logging
from e2b import Sandbox

logging.basicConfig(level=logging.DEBUG)
logger = logging.getLogger("my-app.e2b")

sbx = Sandbox.create(logger=logger)
sbx.commands.run("echo hello")   # RPC logged via `logger`
sbx.set_timeout(60)              # control-plane call also logged via `logger`

🤖 Generated with Claude Code

[changeset-bot]

🦋 Changeset detected

Latest commit: ed5e520

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@e2b/python-sdk	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[cursor]

PR Summary

Medium Risk
Touches all sandbox HTTP and RPC client wiring and changes default logging from always-on module logs to opt-in only, which may surprise operators who relied on implicit SDK noise.

Overview
Adds an optional logger (logging.Logger) on Sandbox.create, AsyncSandbox.create, and static Sandbox.connect(sandbox_id, …). The logger is held on ConnectionConfig and flows through get_api_params so later control-plane calls (kill, pause, set_timeout, get_info, etc.) keep using the same logger—matching the JS SDK’s construction-time-only model (not a public per-request ApiParams field).

HTTP logging moves to shared make_logging_event_hooks / make_async_logging_event_hooks on the API client, envd httpx clients, and volume clients. ConnectRPC logging is added on e2b_connect.Client. Levels align with JS: requests and successful unary responses at INFO, streamed RPC messages at DEBUG, HTTP status ≥ 400 at ERROR. With no logger, no request/response logs are emitted.

Breaking observability change: always-on e2b.* transport-level request logging is removed in favor of this opt-in path. Volume content calls can still pass logger per request via VolumeApiParams.

Also guards envd_access_token with Unset when building sandbox headers. Includes a changeset and tests/test_logging_option.py.

^{Reviewed by Cursor Bugbot for commit ed5e520. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

Package Artifacts

Built from 288f9d7. Download artifacts from this workflow run.

JS SDK (e2b@2.30.7-mishushakov-python-logger-connection-option.0):

npm install ./e2b-2.30.7-mishushakov-python-logger-connection-option.0.tgz

CLI (@e2b/cli@2.13.1-mishushakov-python-logger-connection-option.0):

npm install ./e2b-cli-2.13.1-mishushakov-python-logger-connection-option.0.tgz

Python SDK (e2b==2.29.6+mishushakov-python-logger-connection-option):

pip install ./e2b-2.29.6+mishushakov.python.logger.connection.option-py3-none-any.whl

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 25416ed3cc

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 96c1322. Configure here.}

[mishushakov]

@matthewlouisbrockman was the two commits added on purpose? if it's not related to the PR, i'd move that

[matthewlouisbrockman]

apparently that's what happens when u click the copilot link next to review at top of github ui, lemme figure out how to undo those lol

[matthewlouisbrockman]

should we sanitize these? used to be

    def handle_request(self, request):
        url = f"{request.url.scheme}://{request.url.host}{request.url.path}"
        logger.info(f"Request: {request.method} {url}")
        response = super().handle_request(request)

        # data = connect.GzipCompressor.decompress(response.read()).decode()
        logger.info(f"Response: {response.status_code} {url}")

        return response

now it's the raw url

[mishushakov]

I will merge this one and then implement the sanitization in both SDKs, as JS also appears to be lacking.