-
Notifications
You must be signed in to change notification settings - Fork 44.5k
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 plugins/commands for common I/O operations and train GPT with n-shots to use them #3686
Comments
Note that as far as I've seen the command system is in the process of being overhauled (centralized) apparently, and so is the plugin system. Implementing commands on top of plugins does sound logical though! There also is the ongoing work on allowing commands to be individually enabled/disabled - if commands are based on plugins, that's something that would be implicitly supported The other point worth making is that while these commands may come in handy, they would be cluttering up the context window / prompt quite a bit. In other words, you would want to offer categories of commands and/or lazy (dynamic) command suggestions to prevent that. Also, keep in mind the combinatorial explosion once these commands are offered - aka the enormous solution space |
Without those plugins, which are basic I/O functions, Auto-GPT would be maimed. |
Why does this have to be in any other language than Python ? Wouldn't it just increase the complexity? Almost all of the above tasks are possible in Python and Python is supported on all platforms, so basic I/O in Python should be enough right ? In any case Auto-GPT would be able to write and debug code in any other language if its prompted to do so, so why develop a bunch of plugins in 10 different languages to achieve the same thing which would be achieved by a plugin in only one language on any machine ? Also, Python is just the middle layer between data and the Actual AI Agent like chatGPT. How and in what language we read that data from disk/web and pass on to the AI Agent, and back from AI Agent to disk/web is inconsequential to the task being performed. |
Also see #56 |
After having thought about it a little, here's a proposal (draft really, feedback welcome!) to provide a generic and extensible framework to allow people to set up all sorts of workflows in the form of custom wizards (JSON based) right inside Auto-GPT so that these can be shared/reused and extended as needed (including by the agent itself): #3911 Feel free to add your own 2c |
This issue has automatically been marked as stale because it has not had any activity in the last 50 days. You can unstale it by commenting or removing the label. Otherwise, this issue will be closed in 10 days. |
This issue was closed automatically because it has been stale for 10 days with no activity. |
Duplicates
Summary 💡
GPT-3 or 4 often tries to code Python scripts to do basic I/O operations, because it has no choice. We didn't provide it with the basic and most common commands to handle I/O operations on documents. So it can only resort to writing the functions by itself in Python.
The proposed solution is the following:
We also need to create some specific n-shot training files (chatML, jsonl) for each of the above to let GPT learn how to use them correctly (like for GPT-4 plugins).
Examples 🌈
See also issue #3445
Motivation 🔦
GPT-3 or 4 often tries to code Python scripts to do basic I/O operations, because it has no choice. We didn't provide it with the basic and most common commands to handle I/O operations on documents. So it can only resort to writing the functions by itself in Python. What we need to do is to give Auto-GPT a set of plugins/commands (it would be better if those were converted to plugins) to solve these simple but common I/O tasks.
The text was updated successfully, but these errors were encountered: