feat: add E2B code interpreter

[jamesmurdza]

This is a plug-and-play alternative of the Docker code interpreter that uses E2B cloud sandboxes.

The inputs and outputs are slightly different compared to the default code interpreter:

Input: Dependencies are specified in the code via "!pip install"
Output: Output is a JSON structure separating standard output, errors, and rich data.

However these don't necessarily affect the end user as they are specified for the agent in the schema.

It also requires an E2B API key.

[jamesmurdza]

Example agent: https://gist.github.com/jamesmurdza/956021e18c9576560c01b25f3e9d5b6b

[jamesmurdza]

Hi @lorenzejay, I've just improved the text and added comments to the README to explain why we have a close() function. I also added arguments to the tool, including timeout.

[lorenzejay]

Hi @lorenzejay, I've just improved the text and added comments to the README to explain why we have a close() function. I also added arguments to the tool, including timeout.

Awesome. Again, should it just automatically use the close method once it finishes the response? Don't need to keep the process running when its done right. Instead of having users set close manually. not saying remove the method just include that or even include that as a flag users can set ie: close_when_finished: bool

[jamesmurdza]

Hi @lorenzejay, I've just improved the text and added comments to the README to explain why we have a close() function. I also added arguments to the tool, including timeout.

Awesome. Again, should it just automatically use the close method once it finishes the response? Don't need to keep the process running when its done right. Instead of having users set close manually. not saying remove the method just include that or even include that as a flag users can set ie: close_when_finished: bool

@lorenzejay If I understand correctly that would close the sandbox after the first time the tool is called. Since we don't know how many times the tool will be called (and it's frequently used more than once) that would cause workflows to break.

[lorenzejay]

@jamesmurdza getting close
tools/init.py:
add from .e2b_code_interpreter_tool.code_interpreter_tool import E2BCodeInterpreterTool

then on root init.py:
E2BCodeInterpreterTool in init.py to properly import it from crew_tools

[lorenzejay]

@jamesmurdza when running the tool on my crew i get this:

File ".../pypoetry/virtualenvs/crewai-Nmm_nbE4-py3.11/lib/python3.11/site-packages/e2b_code_interpreter/main.py", line 40, in init
super().init(
TypeError: Sandbox.init() got an unexpected keyword argument 'envs'