Baker on a16z: "We got Claude Code. I built some stuff, did some cool stuff. Then in 3 minutes of creating Grok Bots, I had much better versions of everything I created."
Podcast summarizer. 10 seconds in Grok Bot.
Substack, X summarizer, X sentiment tracker. Hours in Claude Code. 7 to 12 seconds in Grok Bot.
"To me, Grok Bot does feel like another ChatGPT moment."
via @stark0xbt
Show your Grok Bot a task once. It handles it from then on.
Rakazo is an open source Grok Bot. Do the task on the bot's computer while it watches, and it saves the steps as a skill it can reuse.
Every bot in BotDirectory runs on it.
https://t.co/9EOSTBtk6n
Grok Bot is getting support for Apple Home and iOS Alarms.
The latest Grok Bot iOS build has the groundwork in place:
"Grok Bot can read and control your Home accessories when you ask it to."
"Grok Bot can set alarms and timers when you ask it to."
via @aaronp613
Grok Bot can also keep you safe online
Whenever you're sharing something personal on social media, Grok Bot can help protect your private info. About to share a screenshot of a flight booking on 𝕏? Just ask Grok Bot to hide all the sensitive details first.
via @XFreeze
A Grok Bot that hunts for deals.
A Rakazo user has a bot scanning eBay and other marketplaces for cheap servers and PC parts, then sending every good deal. via @michaelortnerit
Rakazo is an open source Grok Bot. Every bot in BotDirectory runs on it.
https://t.co/9EOSTBtk6n
The Grok Bot team just put its own bots in the marketplace.
Import one. Connect your tools. Done.
The 10 worth stealing, by job:
BUILD
Engineer Bot → supervises coding agents, you merge the PRs
Proto Bot → turns feature ideas into draft PRs
figma bro → turns Figma frames into build specs
Startup QA Bot → tests your product and reports bugs with steps
GROW
Distro Bot → runs campaigns, asks before posting or spending
Signal Prospector → finds buying signals and drafts outreach
Video Editor → cuts raw footage into captioned vertical clips
RUN THE BUSINESS
Stalk Bot → tracks competitors' pricing and positioning
Haggle Bot → finds wasted SaaS spend and drafts negotiations
MAKE YOUR OWN
dr eggbot → describe a job, it builds a specialist bot
via @cyrilXBT
“A lot of you said you finally get Grok vs. Grok Bot. Cursor, not so much.
So I asked Grok Bot to make a quick video explaining it. I didn't edit a thing.” — @Texas_Twins_Dad
https://t.co/m005eSTM9R
A lot of you said you finally get Grok vs. Grok Bot.
Cursor, not so much.
So I asked Grok Bot to make a quick video explaining it.
Here it is. I didn't edit a thing.
“I asked Grok Bot to install Docker in its own computer.
So I can practically run anything.” — @melvindvivas
Your Grok Bot has a whole computer of its own. Let it set up the tools it needs.
Give each Grok Bot one job.
Rakazo is open source and starts you with a bot team: Inbox Manager, Sales Outbound, Expense Manager, Coding Agent, and a Chief of Staff to run the rest. Each is a template you can tweak.
Every bot in BotDirectory runs on it.
https://t.co/9EOSTBtk6n
The more you rely on Grok Bot, the harder it would be to start from scratch.
If you lost access to your account tomorrow, could you rebuild your setup?
Here’s a prompt to create an automatic backup routine and a recovery checklist, stored outside your account, so you can get back up and running faster:
“Help me create a backup and recovery SOP for my Grok Bot setup.
1 - Map my setup.
Help me ask each Bot to document its own job, rules, memory, skills and routines. Don’t assume one Bot can see what the others have learned. Include essential files, preferences and context. Flag anything inaccessible or missing.
2 - Save a recovery pack.
Help me connect Google Drive or OneDrive first. Save a readable rebuild document in a private folder I can access without Grok Bot.
Include a connections table: each app, the account it uses, which Bots use it and what they’re allowed to do. Exclude passwords, API keys and login tokens.
3 - Write the rebuild instructions.
Use this order: reconnect apps, create Bots, restore their documented instructions and context, add skills, then recreate routines in a paused state. Configure approval rules before enabling anything.
Clearly mark where I’ll need to sign in again. Prioritise the workflows I depend on most and include a manual fallback while Grok Bot is unavailable.
4 - Test a recovery.
Walk me through rebuilding one non-critical workflow without changing the original. Keep external actions paused.
Ask the original and rebuilt Bot the same three questions about its job, rules and preferences. Compare the answers and test the workflow. Record what worked, what was missing and what still needs testing.
5 - Keep it current.
After I approve the destination and first backup, create a monthly routine to update the rebuild document. Also update it after changes to a Bot. Explain any update that requires me to trigger it manually.
Keep dated versions, verify the saved files can be read and tell me if a backup fails or is incomplete.
6 - Make restarting safe.
Check unfinished work, missed tasks and actions already completed, so restarting doesn’t send duplicate messages or repeat transactions.
Rebuilt routines start paused. Check what each one sends or changes, then ask for my approval to enable them one at a time.
Finish with a one-page ‘Start here’ checklist covering:
What’s backed up.
What needs manual rebuilding.
What to restore first.
What doesn’t come back, including past chat history and anything a Bot learned that wasn’t captured.”
You’ve put time into getting Grok Bot working the way you want.
Make sure you’ve also kept the instructions to build it again.
via @Michael_Fenech_
“I email my Grok Bot more than anyone else these days.” — @KettlebellDan
Your Grok Bot can have its own inbox. Forward it the thread, the receipt, the doc, and let it take it from there.