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

[New tool] docker code executor #16935

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Conversation

logan-markewich
Copy link
Collaborator

Description

Adds a new tool spec with several tools for basically being a developer.

  • execute_code
  • execute_file
  • list_files
  • write_file
  • create_directory

Still TODO:

  • does this actually work? So far have only slightly dogfooded this with a gpt-4o agent
  • is this safe? Can it be safer?
  • does the approach make sense? I might want to add async functions as well tbh
  • write tests?

New Package?

Did I fill in the tool.llamahub section in the pyproject.toml and provide a detailed README.md for my new integration or package?

  • Yes

Version Bump?

Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

  • Yes
  • No

Type of Change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Your pull-request will likely not be merged unless it is covered by some form of impactful unit testing.

  • I added new unit tests to cover this change
  • I believe this change is already covered by existing unit tests

Suggested Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added Google Colab support for the newly added notebooks.
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I ran make format; make lint to appease the lint gods

@logan-markewich
Copy link
Collaborator Author

Hmm. To be more production useful, this kind of needs to be on a server

@logan-markewich
Copy link
Collaborator Author

A more opionated version of this tool could also be a tool Registry, where an llm can build its own tools over time

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