Skip to content

Commit 253aeba

Browse files
authored
Update README.md
1 parent 37f650d commit 253aeba

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

README.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -180,7 +180,12 @@ await sandbox.notebook.execCell(code, {
180180
await sandbox.close()
181181
```
182182

183-
## How it works
183+
## Custom E2B sandbox with Code Interpreter SDK
184+
185+
The template requires custom setup. If you want to build your own custom template and use Code Interpreter, look at [README.md](./template/README.md) in the template folder.
186+
187+
188+
## How the SDK works
184189
The code generated by LLMs is often split into code blocks, where each subsequent block references the previous one. This is a common pattern in Jupyter notebooks, where each cell can reference the variables and definitions from the previous cells. In the classical sandbox each code execution is independent and does not share the context with the previous executions.
185190

186191
This is suboptimal for a lot of Python use cases with LLMs. Especially GPT-3.5 and 4 expects it runs in a Jupyter Notebook environment. Even when ones tries to convince it otherwise. In practice, LLMs will generate code blocks which have references to previous code blocks. This becomes an issue if a user wants to execute each code block separately which often is the use case.
@@ -192,6 +197,3 @@ Additionally, this new template also partly implements the [Jupyter Kernel messa
192197

193198
The full and always up-to-date list can be found in the [`requirements.txt`](https://github.com/e2b-dev/E2B/blob/stateful-code-interpreter/sandboxes/code-interpreter-stateful/requirements.txt) file.
194199

195-
## Custom E2B sandbox with Code Interpreter SDK
196-
197-
The template requires custom setup. If you want to build your own custom template and use Code Interpreter, look at [README.md](./template/README.md) in the template folder.

0 commit comments

Comments
 (0)