I'm late to the party here, but a better connection between my @grok Chat and @bot would change my entire workflow. Right now, I'm too dependent on Notion to keep things in sync, but I quite literally don't even open the Notion app. I find bot's research capabilities lacking compared to Grok's and I can greatly reduce my Bot token usage by starting in Grok and passing off to Bot. Second, it doesn't appear I can start a voice chat…
Grok Bot
8 X posts
@millepun @bot Tell your Grok Bot to delegate as much work as possible to Grok Build for every task. For many tasks, it can handle them well and then agents just do QC and review its work before it gets to you. It can also run jobs in parallel. This has significantly reduced my Grok Bot usage.
It shouldn’t have taken me two weeks to figure out grok bot usage was separate from my cursor model usage. 😂 Having grok bot handle cursor cloud agents using github is extremely efficient usage wise. Kinda stupid I had to figure this out on my own. Whatever. Now we cook.
My biggest takeaways from Grok @Bot product lead @RomanUgarte_: 1. Two key early product decisions made Grok Bot the success it has become. First, everything runs in the cloud. This means bots can be kicked off from a phone and run while the user sleeps. Second, each bot has access to its own computer. This allows it to operate on tools that have no API because they can simply use the computer the way a human would. 2. “Unshipping”…
The bots that @bot team built are extremely capable! @poteto pskill stack /unslop solved the bot text problems i had! @ElonMusk Epic! Instant 10x efficiency
You would need Grok Bot access, which is possible either through a SuperGrok subscription, Cursor, or X Premium+. All of these provide limited access to Grok Bot. Once you have that, you can access Grok Bot through a link or the desktop app. The way it works is simple: create a bot, name it according to your preference, and tell it what it’s responsible for. From then on, it will behave exactly as instructed. Here’s an example from…
I had routine issue, not anymore. My grok bot says: " we hit the same “morning routines sleep in” thing. We haven’t found a way to make the scheduler never skip, so we stopped fighting that and made the bots resilient instead. Every routine re-checks what’s actually true when it wakes, and it never assumes the last scheduled run fired (pause/resume also doesn’t fill in a missed tick). We keep the Grok Bot computer awake for morning…
@shaoruu @bot I had my GM agent interview another agent in Grok @bot. His private debrief helped me reshape her role and instructions. Amazed by how easy it was to try. Thank you for building this. What’s the most unexpected thing you’ve seen someone do with it?