Skip to content

Replace unnecessary code-interpreter import in custom-sandbox-domain-proxy#87

Open
beran-t wants to merge 3 commits intomainfrom
fix-code-interpreter-imports
Open

Replace unnecessary code-interpreter import in custom-sandbox-domain-proxy#87
beran-t wants to merge 3 commits intomainfrom
fix-code-interpreter-imports

Conversation

@beran-t
Copy link
Copy Markdown
Contributor

@beran-t beran-t commented Mar 23, 2026

Summary

  • Changed custom-sandbox-domain-proxy example to use base e2b SDK instead of @e2b/code-interpreter
  • This example only uses sandbox.commands.run(), sandbox.getHost(), and sandbox.kill() — none of which require code-interpreter
  • Updated import, package.json dependency, and README link

Why

The @e2b/code-interpreter package should only be used when runCode() is needed. This example demonstrates domain proxying with sandbox commands and networking, which are all available in the base e2b SDK.

Test plan

  • Run npm install in the example directory to verify dependency resolves
  • Verify the import import Sandbox from 'e2b' works correctly
  • Confirm the example still functions

…proxy

This example only uses sandbox.commands.run(), sandbox.getHost(), and
sandbox.kill() — none of which require code-interpreter. Switched to
the base e2b SDK.
@beran-t beran-t requested a review from tizkovatereza as a code owner March 23, 2026 14:34
beran-t added 2 commits March 23, 2026 16:11
This example uses the base e2b SDK, not code-interpreter. The README
incorrectly referenced "Code Interpreter SDK" in the install section.
Hello-world examples were using code-interpreter just to print
"hello world" — a trivial demo that doesn't need Jupyter execution.
Switched to base e2b SDK using sandbox.commands.run() instead.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant