I learned last night that GrokBot has been building it’s own tools to complete tasks I have given it, mostly in python or JavaScript.
However, I did not know it was rebuilding the same tools repeatedly to complete the tasks I was giving it upon every request I made.
To lower the usage of users, or at least for power users. A feature that holds all the tools/scripts the bots build to complete a task in the Bot client programs settings.
This could drastically lower the usage across the user base and the computer needed if the bots saved their tools for future use cases.
To add on to this, a import/export feature for this would also be good or possibly a connector to GitHub in order to store/call upon/inspect/edit the tools made by the bots.
I already have them logging all future token/usage compared to prior of this finding and will be having them log their token/usage after this finding so that way I will be able to share how much the difference between this actually is on my end, will share what is produced by recording this if the team needs it.
You can do most of this today. When the bot builds a tool that works, ask it to save it as a skill, for example: “Save the script you just wrote as a skill called invoice-export, and keep the script on your computer so you reuse it next time.” Your bot’s computer is persistent, so saved scripts stay put between chats, and the skill tells the bot where the tool is and when to use it.
Your saved skills show up under Plugins > Yours (in the Private section), and typing / in the composer lists the skills a bot can use. You can open, edit, or remove them from there, or just ask the bot to update one.
Importing tools straight from a GitHub repo isn’t supported today, and the bot doesn’t save tools on its own yet unless you ask.
Yes, the things you mentioned are currently available. However, the flow process would be
Ask for task
Grokbot does task
Grokbot out puts results
User has to ask to verify if new skills/tools/scripts were made in process or ask to save new sets of skills
Grokbot saves the sets
Which is a 5 step process, in what I described originally
User asks for task
Grokbot checks a file for existing tools then does task
Grokbot outputs results and saves all skills/tools built in process
The user would no longer have to ask for the save or building of the skills/tools because there would already be a location to check. Unless I’m misunderstanding, or not untilizing the current features fully. What I do know is I had not known one of the bots was repeatedly rebuilding a set of scripts to run some tasks until I had another bot analyze that bots work flows and it suggested to save all scripts/tools/skills it was using/rebuilding upon every request of the repeated task and then have the full team of bots reference that tool box area when any given task needed to build a tool to complete a task and then to bundle said tools into suites for larger tasks.
I’ve only been using these agents for about a week, so excuse me if I am lacking in my understanding or describing something that is currently available and just misunderstanding the mechanisms behind it or not untilizing. I’m fully allowing the Bots and Cursor agents to “steer the boat”, I just point at things and I have them tell me what they need from me in order to complete everything I point at them to do. It was the bots suggestions I put this feature request on the forums, and even the bots whom told me of this forums.