Replies: 2 comments 2 replies
-
I've created some tools. They drop into the output folder of your directory. Getting them to be used is another story. I believe some of the tools my tool agent made got it to move around locally on a macbook. First, it took a while in the output directory (folder) before going the proper direction (upward). It found its way into Desktop then into the test folder, read test.txt and finished with complete. It take a lot of time thou. Perhaps next time I ask Agents to use tools in output DIR, and explain the output DIR has no sub directories and not to create any, unless its testing mkdir command within output DIR. Just sharing my experience on day 3. |
Beta Was this translation helpful? Give feedback.
-
Hey, in today's release, we've built an easy way where people can add their tools simply by making a Github Repo with all the logic and attaching the link in SuperAGI's front-end. I hope that helps you. |
Beta Was this translation helpful? Give feedback.
-
I've created an agent to build an app with next.js and so it needs to run terminal to perform commands, but we don't have a Terminal tool.
I can see in agent_executor.py we have a list of tools being imported. Should I be attempting to create my own Terminal module in superagi/tools or do we have a directory somewhere of additional tools like this to use?
Beta Was this translation helpful? Give feedback.
All reactions