fix(sdk): disable timeout on background commands by default

[mishushakov]

Summary

Background commands (commands.run(..., background=True) in Python / { background: true } in JS) were killed once the default 60s command timeout elapsed. They now default to no timeout, while foreground commands keep the 60s default, and an explicit timeout/timeoutMs still takes precedence.

The "disable" value differs per transport: Python's e2b_connect treats 0 as no-limit, while @connectrpc/connect treats timeoutMs <= 0 as an immediate abort and only undefined as no-limit — so the JS side resolves to undefined and the Python side to 0. Both SDKs use their natural "not set" marker (undefined / None) to decide the default, and the changeset bumps e2b and @e2b/python-sdk as patches.

Usage

# Python — runs indefinitely now (previously killed after 60s)
handle = sandbox.commands.run("python -m http.server", background=True)
# explicit timeout still honored
sandbox.commands.run("sleep 10", background=True, timeout=2)  # TimeoutException

// JS/TS — no timeout by default for background commands
const handle = await sandbox.commands.run('python -m http.server', { background: true })
await sandbox.commands.run('sleep 10', { background: true, timeoutMs: 2000 }) // still times out

Tests

Integration tests (sync + async Python, JS) against live sandboxes assert that a background sleep 20 is capped when given timeout=10 (raises TimeoutException in under 20s) and completes successfully when no timeout is set.

🤖 Generated with Claude Code

[changeset-bot]

🦋 Changeset detected

Latest commit: 12850f4

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

This PR includes changesets to release 2 packages

Name	Type
@e2b/python-sdk	Patch
e2b	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
Default timeout behavior changes for background commands, which may affect callers that implicitly relied on the old 60s kill.

Overview
Background commands.run no longer applies the 60s default command timeout when background is true, so long-running background processes are not killed at 60s unless you pass timeout / timeoutMs. Foreground runs still default to 60s; explicit timeouts still apply.

In JS, background starts pass undefined for timeoutMs instead of the default connection timeout. In Python (sync and async), omitted timeout resolves to no limit for background and 60s for foreground via an _Unset sentinel; timeout=None is treated as no limit. Patch bumps and integration tests cover capped background runs, uncapped background runs past 70s, and Python timeout=None on foreground.

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

[github-actions]

Package Artifacts

Built from 7a0477a. Download artifacts from this workflow run.

JS SDK (e2b@2.27.2-mishushakov-disable-background-cmd-timeout.0):

npm install ./e2b-2.27.2-mishushakov-disable-background-cmd-timeout.0.tgz

CLI (@e2b/cli@2.10.4-mishushakov-disable-background-cmd-timeout.0):

npm install ./e2b-cli-2.10.4-mishushakov-disable-background-cmd-timeout.0.tgz

Python SDK (e2b==2.25.1+mishushakov-disable-background-cmd-timeout):

pip install ./e2b-2.25.1+mishushakov.disable.background.cmd.timeout-py3-none-any.whl

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6647fb6cab

ℹ️ 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".