Finding signal on Twitter is more difficult than it used to be. We curate the best tweets on topics like AI, startups, and product development every weekday so you can focus on what matters.
Grok Bot: What People Are Actually Using It For... | Tech Twitter
Grok Bot: What People Are Actually Using It For (/last30days of X, Reddit, and YouTube)
Matt Van Horn@mvanhorn · August 13, 2026 · 10 min read
Originally published by @mvanhorn on X. Tech Twitter preserves the original source alongside this readable edition.
Before you dive in
• Grok Bot demonstrates that AI agents reach mainstream adoption when they prioritize demonstration-based teaching over prompt engineering, operate as narrow single-purpose bots with human approval gates, and eliminate setup friction—shifting the bottleneck from technical specification to practical task design and trust boundaries
• Builders should recognize that the real differentiator isn't agent capability but interface simplicity, credential scoping, and the willingness to document failure modes (like a plumbing company firing its first bot), because every scaled workflow in this launch follows the same pattern: teach once by screen recording, route through a chief-of-staff bot, and keep money or sends behind human confirmation.
Best for builders who want practical takeaways. 10 min read.
Yesterday Allie K. Miller called last30days “chef's kiss” on Greg Isenberg's podcast, and I wanted the clip. So from my phone I sent Grok Bot the 48-minute YouTube link and said “cut the part for me that says last30days.” One prompt, one shot, almost perfect.
I pointed /last30days at Grok Bot twice today, one sweep on use cases and one on best practices, pulled the highest-engagement posts live, and read the Cursor team's hundred-item use-case catalog end to end. Grok Bot is 48 hours old in public beta, which means nobody has a mature playbook yet. What exists is early adopters showing their receipts, and the receipts sort into eight jobs people keep hiring it for.
Here is what people are actually using it for, ranked, with the engagement numbers and the prompts worth stealing.
1. 🔧 The office manager
The highest-signal business receipt of the launch is not from a developer. It is from a plumbing company owner:
Twenty-four hours from download to automated dispatch and office chores, in a business with zero engineers. His follow-up thread is even better because it includes the failure:
Dana Dispatcher - the first bot I ever fired (my fault). Slow, very slow, and would make mistakes.
@HouseHackerJon, X
Hiring bots, firing bots, and taking the blame for a bad job description. That is the actual texture of running these things, and nobody else in the corpus was honest enough to publish it. Steal the shape: pick one repetitive office chore, hand it over end to end, and expect to fire your first attempt.
2. 🎩 The chief of staff
The power-user convergence point. You do not talk to five bots. You talk to one, and it routes.
Debbie O'Brien runs the audit variant: she asked one bot to review her whole fleet and propose how to manage the team (112 likes, 119 bookmarks). And the sharpest framing of why this clicks for non-engineers:
Grok Bot nailed the personal context graph. Minimalist interface enough for “normies” while keeping the bar for day to day EA / Chief of Staff / COO like tasks.
@JayaGup10, X, 127 likes
We doomscroll, you upskill
Get the 10 tweets shaping how builders think today.
Newsletter
We doomscroll, you upskill
Get the 10 tweets shaping how builders think today.
you can name your @bot whatever you want, assign them any task, and text them like your friends
@hareemmannan, X, 26 likes
Steal it: make your second bot a chief of staff, then stop opening the other chats.
3. 📅 Life admin: calendars, reservations, tickets
The demo that went furthest was not a work task. It was dinner:
Calendars read, best time found, reservation booked, negotiated in mixed Chinese and English, 937 likes, and Elon's “Try out Grok @Bot” quote boost put it in front of 4.6M people.
The origin story of the whole product is the same category. Before it was Grok Bot, it was a bot named Benny that an engineer built for himself:
I built this bot called Benny. I'm a fairly lazy person... fix them all... while I sleep.
@MTSlive quoting @poteto, X, 497 likes, 65K views
Poteto's current roster (623 likes): calendar management, shipping code, sniping tickets to The Odyssey in IMAX 70mm, ordering lunch daily, and finding dank emojis for Slack. Users copied the ticket-sniping trick within a day, and the most-requested missing feature is multiplayer: groceries and social plans shared with a partner (55 likes).
4. 🎬 Teach it by doing the task once
The technique the whole community converged on in 48 hours: do not write a prompt describing the workflow. Record yourself doing it.
hit + in the chat and record yourself doing it in the browser. the bot watches, then it can do it again.
@ericzakariasson, Cursor, X, 72 likes
A teacher ran exactly that play:
gave Grok Bot access to my syllabus, digital textbook and Google Classroom... posted homework... do that every week... teacher's assistant trained in one hour.
@sethjlevy, X, 90 likes
The mental model that keeps beginners from stalling, per xAI's own docs: a skill is the how, a routine is the when. Teach the skill by demonstration, then attach a schedule. Matt Berman's walkthrough (599 likes, 236.2K views) explains why this lands with people who bounced off agent CLIs: “Grok Bot brings coding agents to a mainstream audience without being intimidating. THERE'S NO MODEL SELECTOR!” The early-access YouTube reviews agree:
This could be the thing that finally gets regular people to start using AI agents. Because it's not only really good, but also very intuitive.
Paul J Lipsky, YouTube, 26,488 views, 754 likes
And the highest-engagement setup guide of the launch is Alex Finn's five-step brain-dump playbook:
Brain-dump your goals into the first agent, then paste this, his step two verbatim:
Then let it design the fleet, propose the routines, and implement them. 2,734 likes, 3,385 bookmarks, 287K views at pull time.
5. 📬 Inbox, Slack, and the morning brief
The quietly universal starter job, same as it was for every agent before it, except now it takes about a minute to set up (63 likes). The variants people actually run:
bot scanning my messages... bot updating my accomplishments and two-week look ahead doc
@KettlebellDan, X, 63 likes
already making my days better by synthesizing the flood of information I receive... little Grok guys look cute as they toil away summarizing slack
@BurnhamDC, X, 95 likes
The Cursor catalog's versions are worth stealing verbatim: a morning digest across Slack, Gmail, calendar, and Granola managed from a DM (item 53), email triage twice a day (item 55), and my favorite, item 63: “turn a daily slack digest into a ~3-minute morning podcast you can play on mobile.”
I find it funny when @bot 👍my replies :D like dude!
@naoufal_elh, X, 146 likes
6. 💼 Sales ops and the CRM rebuild
The deepest well of concrete workflows is Eric Zakariasson's hundred-item catalog (1,918 likes, 2,928 bookmarks, 399K views), and the sales entries read like a job description: a sales play that took 90 minutes now ~95% automated (item 2), most of a custom CRM rebuilt by a small bot crew in about a day and a half (item 5), ~200 recruiting applications reviewed into strong / mid / reject in one pass (item 9), and a Salesforce end-of-quarter question answered from a phone in ~10 seconds (item 13).
Someone outside the vendor ran the same play on their own stack:
ler todos os meus emails e criar um CRM... utilizando o mcp da attio... fez bizarramente bem (read all my emails and build a CRM using the Attio MCP... it did it bizarrely well)
@daniellimae, X, 75 likes
Note the operating mode in every credible sales demo: draft and queue, never send. The screenshot everyone passed around had 36 LinkedIn drafts queued and zero sent, waiting on approval. That is the current trust boundary, and the users who like the product like it because the boundary is there.
7. ⏰ The watchers and snipers
The always-on cloud computer earns its keep on jobs where the whole value is checking constantly:
checks Google Flights deals and pings me on Slack 4x a day... Pure computer use via it's private virtual environment
@Daniel_Farinax, X, 103 likes
The catalog's sniper section is the most bookmarkable list in it, verbatim: monitor recreation.gov and ReserveCalifornia for campsites and book after a quick chat confirm (item 75), watch an AMC ticket drop and buy when seats open (item 76), snipe always-booked gym pool spots (item 77). On the work side, item 30: watch a competitor's pricing page and get a Slack ping when it changes.
Reddit got to the second-order problem within a day of launch:
I wonder what happens when 2 bots hack into the gym to sign me up and revoke someone else's membership. Like would they kick 2 ppl out or would they battle it winner gets to kick someone?
makz242, r/singularity, launch thread at 43 upvotes, 69 comments
If you can describe the refresh-and-pounce loop you do by hand, a bot will run it every few minutes forever. That is a genuinely new household capability, and also exactly the shape that turns forty polite suppliers into forty thousand, so point it at inventory instead of people.
8. 🎨 The content pipeline
The section my own use case lives in. Debbie O'Brien chained the furthest:
tested if Grok @bot could actually be my travel agent and book my flights... editing... done by a Grok bot... whole youtube video was uploaded by the youtube bot
@debs_obrien, X, 57 likes
Her aside in the same post is the tell that the muscle memory is forming: “Damn why am I writing this post instead of just asking the bot to do it.”
The heavier variant, 74 game assets generated, cleaned, cropped, and integrated in about 2 hours, where the bot created its own skill along the way, comes with the best one-line mental model of the launch: “Setting up Grok Bot is closer to hiring someone and giving them your laptop... if a person can click through it, Grok Bot probably can too.” And connect a posting MCP and the same pipeline distributes to every social channel.
My podcast-clip cut is this same job: media in, judgment call, finished asset out, no timeline scrubbing. It is the first Grok Bot result that made me close Claude Code and just ask the bot instead.
🧵 What ties all eight together
Three properties show up in every workflow on this list.
Taught, not prompted. The winners recorded themselves doing the task once and corrected the second run. Nobody wrote a 500-word system prompt.
A fleet of narrow bots. One job per bot, handoffs between them, usually routed through a chief of staff. The single do-everything bot is the beginner mistake the follow-up threads keep correcting.
Draft-and-approve by default. Queued emails, chat confirms before booking, approval before spending. Every workflow that people trust enough to keep running has a human gate at the money-or-send step.
And one fact almost every hype video omits: your bots all share a single cloud computer, with one filesystem and one set of logins. xAI's own documentation says plainly: do not use separate Bots as a security boundary. Connect Gmail once and every bot on the account can reach it. So scope by what you connect, not by which bot you are talking to, and keep the beta away from payments, production, and customer data. Reddit called the failure mode within hours of the announcement:
Incoming a lot of stories like bot send all my money to someone.
Aldarund, r/singularity, launch thread
The boundary between human and bot is already porous enough to be a joke:
🔑 KEY PATTERNS from the research
Teach by screen-recording a real run, then correct on the second run. Do not try to specify the workflow up front.
Keep skills and routines separate in your head: skill = the how, routine = the when.
Narrow, single-purpose bots that hand off beat one generalist bot.
Scope risk at the connection level, never by splitting bots. They share one VM and one credential pool.
Keep beta bots off payments, production, and customer data until permission granularity and audit records are documented.
Decide the lock-in question before you sink weeks of teaching into it: Grok Bot is the zero-setup path, OpenClaw and Hermes are the portable ones.
📊 All agents reported back
Reddit 31 threads / 6,440 upvotes / 3,054 comments; X 61 posts / 14,884 likes / 1,914 reposts; YouTube 11 videos / 229,523 views; TikTok 48 videos / 204,168 views; Instagram 20 reels / 994,396 views; Hacker News 25 stories / 2,536 points / 2,229 comments; LinkedIn 10 posts / 1,096 likes; GitHub 33 items; Digg 32 clusters / 715 posts; Techmeme 7 headlines. Compiled from two /last30days runs on 2026-08-13, a live X engagement pull, and the Cursor team's hundred-item catalog read in full.
/last7days of Fable 5 and GPT-5.6: What Thousands of Upvotes Say Actually Works
