Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for built-in code_interpreter tool #3

Open
transitive-bullshit opened this issue Nov 15, 2023 · 1 comment
Open

Add support for built-in code_interpreter tool #3

transitive-bullshit opened this issue Nov 15, 2023 · 1 comment
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@transitive-bullshit
Copy link
Owner

This is for the built-in code_interpreter tool.

Currently, the built-in code_interpreter tool is hard-coded to throw a 501 unsupported error (source).

At a minimum, we should support an integration with open-interpreter.

I believe that e2b also has some interpreter functionality.

@transitive-bullshit transitive-bullshit added enhancement New feature or request help wanted Extra attention is needed labels Nov 15, 2023
@transitive-bullshit transitive-bullshit changed the title Add support for different code_interpreter implementations Add support for built-in code_interpreter tool Nov 15, 2023
@transitive-bullshit
Copy link
Owner Author

transitive-bullshit commented Nov 16, 2023

For code_interpreter sandboxing, also considering:

We could certainly use Docker like open-interpreter does; just want to keep our options open for keeping things as lightweight as possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant