@mattyp@poteto Grok Bot treats skills and scripts inconsistently. Skills require a fixed location (/home/box/agent-data/workflows/) that does not survive a box rebuild. Scripts have no platform location at all. Please treat them consistently: make skills durable across rebuilds, and give scripts a supported location.
Grok Bot is completely back for me. Brain, usage. Everything. Magic restored.
OpenBot deleted. Dope idea, good design, but way too buggy and feature-limited to be worth it after using it for a few days. Glad I checked it out, but Grok Bot is still way better than anything else when healthy.
I’ll test 4.8 if you want lmk
@mattyp@poteto@bot Also, in no particular order, here’s some of the feature requests my bits have sent in for me:
Thanks @mattyp and @poteto for listening!
I love GrokBot… I’m running 20 of them. My principal request is better advance communication from SpaceXSI when you have to make a potentially unfavorable change, like changing models, usage limits, or redirecting computer resources to train the next version of Grok so that users can plan their usage expectations accordingly.