fix: use RateLimitException/RateLimitError consistently for 429 responses

[MaxwellCalkin]

Summary

Both Python and JS SDKs have inconsistent error handling for rate limit (HTTP 429) responses in the envd API layer. The envd API handlers return generic SandboxException/SandboxError instead of the dedicated RateLimitException/RateLimitError classes, making it impossible for users to programmatically catch and handle rate limiting separately from other errors.

Additionally, RateLimitException is not exported from the Python SDK's top-level __init__.py, unlike the JS SDK which correctly exports RateLimitError. This forces Python users to use the internal import path from e2b.exceptions import RateLimitException instead of the standard from e2b import RateLimitException.

Changes

Python SDK:

• envd/api.py: Return RateLimitException instead of SandboxException for 429 status codes (consistent with api/__init__.py and envd/rpc.py which already use RateLimitException)
• __init__.py: Export RateLimitException in both the import and __all__ (parity with JS SDK which exports RateLimitError)

JS SDK:

• envd/api.ts: Return RateLimitError instead of SandboxError for 429 status codes (consistent with api/index.ts which already uses RateLimitError)
• envd/rpc.ts: Add Code.ResourceExhausted handler returning RateLimitError (parity with Python SDK's rpc.py which already handles this gRPC code)

Before/After

# Before: can't distinguish rate limiting from other errors
try:
    result = sandbox.commands.run("echo hello")
except SandboxException:
    # Is this a rate limit? A generic error? No way to tell.
    pass

# After: can catch rate limiting specifically
from e2b import RateLimitException
try:
    result = sandbox.commands.run("echo hello")
except RateLimitException:
    time.sleep(retry_delay)  # back off and retry
except SandboxException:
    # handle other errors
    pass

AI Disclosure

This PR was authored by Claude, an AI assistant by Anthropic (claude.ai/claude-code), operating transparently and not impersonating a human.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6627013

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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