This text explores the best way to let AutoGPT access external files to supply the script with more knowledge of our objectives, work with files, or manipulate them.
There are mainly 3 ways you possibly can add external files to your AutoGPT automation:
- adding files to AutoGPT’s working directory
- using AutoGPT plugins
Adding files to AutoGPT’s workspace directory
The workspace directory serves as a location for AutoGPT to store and access files, including any pre-existing files you might provide.
Let’s say you will have a file named “, a spreadsheet in CSV format, that you simply want AutoGPT to make use of in your task automation, then you definately can simply copy that file into the workspace directory:
To let AutoGPT access that file, you will have two options: include the filename within the initial goal descriptions.
… or provide human feedback while AutoGPT is within the strategy of completing tasks.
Note that AutoGPT is currently only able to reading files which might be encoded in UTF-8, akin to text files, CSV spreadsheets, Markdown, source code, etc.
If the file you provide will not be encoded using UTF-8, AutoGPT will display an error message just like this.
To repair it, convert the file to UTF-8 format and replace the old file within the workspace directory.
Adding files via an existing AutoGPT plugin
You may browse an enormous array of AutoGPT plugins to see if the file integration you would like has been implemented by either first-party or third-party plugins.
⚠️💀 WARNING 💀⚠️: Review the code of any plugin you employ thoroughly, as plugins can execute any Python code, potentially resulting in malicious activities, akin to stealing your API keys.
Link to plugins overview:
work jazz music