Today I'm going to talk about what everybody else is talking about these days. Grockbot. Yes, I did an episode lovingly entitled Grock Grock Grock where I gave you my highle overview of Grockbot, the new Grock models and origin cursor's new GitHub replacement. But today I'm going to talk specifically about Grockbot. After several weeks of working with Grockbot, I have to tell you the truth. I have killed all my open claws and moved almost entirely to Grockbot. In this episode, I'm just going to show you a couple very practical use cases of Grockbot, why I think it's better right now than some of the open claws I was running, what is still missing, and what I can't wait for you to try. This is going to be a totally hands-on mini episode with bot ideas you can steal. We will put the bot links and the bot templates in the show notes. And I hope this is a really specific way to get you up and running in your life a little bit better with Grockbot.

This episode is brought to you by work OS. AI has already changed how we work. Tools are helping teams write better code, analyze customer data, and even handle support tickets automatically. But there's a catch. These tools only work well when they have deep access to company systems. Your co-pilot needs to see your entire codebase. Your chatbot needs to search across internal docs. And for enterprise buyers, that raises serious security concerns. That's why these apps face intense IT scrutiny from day one. To pass, they need secure authentication, access controls, audit logs, the whole suite of enterprise features. Building all that from scratch, it's a massive lift. That's where Work OS comes in. Work OS gives you drop-in APIs for enterprise features so your app can become enterprise ready and scale up market faster. Think of it like Stripe for enterprise features. OpenAI, Perplexity, and Cursor are already using work OS to move faster and meet enterprise demands. Join them and hundreds of other industry leaders at workos.com. Start building today.

Okay, quickly before we get into use cases, let's just remind you of exactly what Grockbot is. Grockbot is the new multi-agent platform from xAI. It allows you to build autonomous co-worker agents, give them tools, connect them to your systems, and have them collaborate on complex tasks. Now, what do I have to say having gone through this? UX matters. It just does. And I think OpenClaw set the standard for what an autonomous teammate personal agent can do. Multiplayer was genius. Use cases were awesome, but at the end of the day, I struggled so much to maintain my open claw. And I am a very technical person. I have Tailscale running, I'm SSHed into my Mac Mini, I have a lifeguard claw, I have all this stuff, and it was just too hard. And so I think the xAI team really nailing a simple everything works out of the box 90% co-worker agent has really just solved a lot of my problems and I have let these agents rip.

Let's dive into the first use case, which is one of my favorites for content creation and distribution: the Publishing Assistant. If you produce a podcast, a video show, or write regularly, you know that creating the core asset is only 30% of the work. The rest is distribution: writing social posts, creating transcripts, building show notes, drafting newsletters, and updating community channels.

I built the Publishing Assistant bot in Grok Bot to completely take over post-production distribution for How I AI. Every hour, it runs a scheduled cron job to check our podcast host, Transistor, for new published episodes. When it detects a new episode, it grabs the audio metadata and the raw transcript. From there, it follows our detailed show style guide to generate platform-specific assets: formatted YouTube show notes with timestamps, a complete email newsletter draft, an X thread draft, and a LinkedIn post.

Instead of stopping at generating text in a chat window, it uses its browser and API integrations to push these directly to our tools. It creates draft threads in Typefully and drops the newsletter draft directly into our publishing queue, then sends me a consolidated Slack notification with links to review and approve everything with a single click. What used to take two hours of tedious post-production work after every single episode is now completely automated.

The second bot in my daily roster is the Competitor & Market Intelligence Agent. In fast-moving spaces like AI and SaaS, missing a competitor's feature launch, pricing pivot, or technical breakthrough can put you weeks behind. But manually checking dozens of changelogs, GitHub releases, blogs, and Twitter feeds every day is impossible to sustain.

I set up this bot to monitor a curated list of direct competitors and key open-source repositories. It runs daily sweeps across changelog pages, documentation updates, product launch announcements, and community discussions. What makes it powerful inside Grok Bot is its ability to synthesize signal from noise. It doesn't just give me a firehose of RSS feeds; it filters out trivial bug fixes and PR marketing fluff, extracting actual architectural changes, feature rollouts, and pricing modifications.

Every Monday morning, it compiles a structured competitive briefing covering what launched, how it compares to our own feature set, and potential strategic implications. It pushes this briefing directly into our Notion workspace and alerts our team channel. Having an autonomous research assistant doing continuous market surveillance ensures we are never caught off guard by industry shifts.

Another critical agent for us is our SOC 2 control bot, which we named Lockdown. We have our SOC 2 controls managed in a central dashboard, and every day as a small team, we have to go through and make sure that all of our monitors are green, that any monitors alerting are not outside SLA, that we're closing vulnerabilities, all that kind of stuff.

So I built Lockdown, the SOC 2 control bot. What this bot does is it actually logs into that dashboard we use to manage our SOC 2 controls, looks through all the controls, and makes sure that none of them need human attention. If there are code controls that we need to address—for example, a newly identified vulnerability—it triages that vulnerability, issues a PR, and then asks me to review and approve it.

This spans across both code controls and personnel/operational controls, like verifying whether we have completed our periodic account audits. It's very nice to have an agent monitoring this company process for us and making it really easy to interact with the responsibilities that we have to our clients. I sometimes say this: we can put AI to work, or we can have AI put us to work in a more effective way. Having AI put me to work against our SOC 2 controls and our compliance and security posture is really nice. It's just like having an intern who taps me on the shoulder and says, "Don't forget tomorrow is account review day," or "Don't forget to offboard contractor B because they're no longer with the company." We still drive these controls, but having this bot manage them is invaluable.

Finally, on the work side, something that has been really impressive from a quality perspective is migrating Holly Helpdesk, our customer support agent at Chat Purity, over to Grok Bot. This used to be an OpenClaw bot, which was pretty good after I spent a lot of time giving it tools, access, and controls. But now it runs through Grok Bot. In the last week since running Holly Helpdesk, I have gotten multiple people asking to leave reviews about our support being so good, which has never happened before.

What she does is every hour she sweeps our Intercom and email inboxes. She uses our support playbook and tools, and manages refunds and technical support fixes. If there is a bug, she is empowered to fix it using Cursor cloud agents. She is also empowered to request refunds from me. I really love this request tool use approval flow: every time a refund needs to be processed, it gives me a button asking, "Should I refund or not?" For instance, if Reuben needs a $19 refund, I approve it, which pushes a Stripe request. That Stripe request allows me to explicitly approve that action for the agent to execute on my behalf in Stripe, the refund is issued, and Holly emails back.

Holly also does a weekly retrospective looking back seven days to see if there are items we need to add to our support playbook or public docs to make more issues self-service. Lastly, she manages our Chat Purity community Slack, answering questions in support channels and prompting community engagement, which saves me from the blank page problem and keeps our community active.

Finally, I want to end with a couple of really fun personal use cases that have been quite delightful. One is Penny Pincher. Penny Pincher does exactly what you think: she goes into my email, looks through receipts, and finds subscriptions to cancel or renegotiate.

Using Penny Pincher in Grok Bot, it found things I should cancel right away, like an old Apple game subscription I had been paying for since my kids were little. It also found upcoming renewals to optimize: our home insurance policy renews in a couple of months, so it went out, gathered market rates against our current coverage, and prepared negotiation points to take to our agent. It noted an Apple Creator Studio trial ending in November and set a reminder. It also noticed I hadn't been redeeming my Audible credits despite paying monthly, so I paused that for 90 days, and it set a reminder for when the pause ends.

Another thing I had Penny Pincher do—which isn't strictly penny-pinching but very fun—was searching for a birth-year Rolex watch with a non-standard case size. It went into the marketplace, found specific vintage options released in the exact year I was born, calculated what the fair market price should be based on comparable listings, identified sellers open to offers, and actually initiated price negotiations for me.

Separate from Penny Pincher, I created a Shopzilla bot that handles complex shopping tasks. For example, I was trying to find a bookcase for a specific corner of my house that had to be exactly 30 inches wide and 15 inches deep. Shopzilla went out with its browser, searched across multiple retailers, filtered through specs, and returned a curated list of options matching those exact dimensions—a tedious manual task it handled effortlessly.

And then my favorite personal bot: Sylvie Style, an agent that helps manage my wardrobe. Having recently had a baby, nursing, and hosting video podcasts where I only need great clothes from the waist up, I wanted to revamp my style without spending hours browsing. I gave Sylvie Style access to my public Pinterest inspiration board. She combed through the images, extracted a visual style language, and researched professional styling frameworks from Reddit stylist communities.

From there, Sylvie Style built a comprehensive wardrobe plan covering essential basics, school drop-off casuals, leveled-up podcast workwear, and statement accessories. The cherry on top is the Monday Wardrobe Shop: every Monday at 8:00 a.m., she scans top retailer sales, filters for pieces that fit my exact style profile and color palette, and sends me a message with direct shopping links for items on deep discount.

I'm going to leave you with a final tip on how to migrate your existing OpenClaw agents over to Grok Bot. When running OpenClaw, I had a rescue bot called the Lifeguard whose only job was managing and monitoring the other bots.

I instructed the Lifeguard: "Pull a secrets-free package of my entire agent setup—crons, agent identities, rules, prompts, and connectors." It generated a clean zip file containing all the configuration files and agent identities without exposing credentials. I was able to upload those subfolders directly into Grok Bot, effectively performing a "brain transplant" that preserved their personalities, instructions, and integration logic.

Once the new Grok Bot agents were verified and running, I told the Lifeguard to safely terminate the legacy instances (e.g., "kill Sam"). It pulled down all active cron schedules, severed gateway configurations, and gracefully decommissioned the local instances. Moving from high-maintenance self-hosted agents to Grok Bot has dramatically simplified my workflow while running over 30 autonomous agents every single day.