August 11–September 19, 2026 · 83 catalog entries
A source-linked catalog from the collected rai feed, using the Jev Atlas format. Grouped by the job people gave their bots. Reposts and follow-ups are merged; distinct jobs in one post can become separate entries. Counts represent use cases, not unique products or creators.
The clearest recurring pattern is a persistent bot that owns a narrow job: school messages become calendar actions; merged code becomes updated help articles; saved bookmarks become tested demos. Other examples use Grok Bot to supervise Cursor or Codex, or to connect services. Those are combined workflows, not evidence that one Grok model performs every step.
- Family, household & personal admin (17)
- Inbox, calendars & business operations (13)
- Content, marketing & audience research (12)
- Software, design & product delivery (15)
- Research, learning & information monitoring (8)
- Bot management, computer upkeep & connected devices (8)
- Templates and integrations — availability claims (6)
- Financial experiments and failures — unverified outcomes (4)
Searched saved X events and tips from August 11, 00:00 UTC through the newest matching post, 2026-09-19T02:04:02.148000+00:00. The expanded search includes Grok Bot, Grokbot, Grok @bot, plural forms and @bot mentions. It found 265 unique saved candidate posts. The older classification export added none. The model-I/O cross-check found no additional concrete use-case account with a missing source ID; three unmatched texts were a bundle promotion, a login-feature announcement and a parody.
Public FxEmbed metadata succeeded for 262 of 269 requested IDs (saved candidates plus explicitly linked posts). Embedded quotes brought the source-text pool to 323, including unrelated quote context. Seven requested IDs could not be fetched. The saved text is retained when metadata is unavailable. Eighteen saved author labels differed from public metadata; the catalog uses the metadata attribution. This is a saved-feed study, not an exhaustive search of X or an export of the browser’s complete durable log.
Each entry labels its evidence. “Author-reported use” means the author says they used it, not that we reproduced the workflow. Secondary demos, templates, integrations and financial claims remain distinguishable. Tweet text and metadata were inspected; videos, apps, transaction histories, code and linked articles were not independently audited. A source link is not a guarantee that a post will remain available.
The catalog contains 73 reported workflows, 6 template/integration entries, and 4 financial experiments or failure anecdotes.
- G001 · School emails → family calendar and action list — Read school and activity messages, surface forms and RSVPs, and add dates to the calendar. Multiple parents describe using this. Author-reported use. @MatthewBerman · @MatthewBerman · @MatthewBerman · @petergyang · @startupstella · @lennysan
- G002 · Daily printed math worksheets — Generate age-specific problems and a shared answer key, print at 6am, and adjust difficulty from prior performance. Reported by @Teslaconomics. Author-reported use. @Teslaconomics
- G003 · A printed morning newspaper — Turn calendar and email information into a paper briefing that prints overnight; the creator also offered the setup to others. Author-reported use. @karenxcheng
- G004 · Book appointments with a final human confirmation — Find appointment options, propose times, book after confirmation, and add reminders. One account describes a physical exam, hair appointment and massage. This is scheduling, not medical advice. Author-reported use. @startupstella · @MatthewBerman
- G005 · Order groceries — An early tester reports grocery ordering. The captured post does not specify the retailer or approval steps. Author-reported use. @agrimsingh
- G006 · Handle online returns — Authors report starting and completing clothing or Amazon return processes. This does not establish that the bot performs physical drop-offs. Author-reported use. @AlexFinn · @MatthewBerman
- G007 · Sell unused household items — Create Facebook Marketplace listings from photos or old listings and manage the sale conversation. One detailed account had a listing live but the sale still underway. Author-reported use. @MatthewBerman · @startupstella
- G008 · Recover unused gift cards and credits — Search old messages for forgotten balances. One parent reports finding three gift cards; another user lists airline credits as part of an ongoing audit. Author-reported use. @startupstella · @toddsaunders
- G009 · Audit subscriptions and obtain retention discounts — Find recurring charges and identify cancellations. @KatieMiller reports using cancellation screens to obtain lower rates and saving $1,600 annually; savings are not independently verified. Author-reported use. @KatieMiller · @toddsaunders · @petergyang
- G010 · Find a human service to remove an annoying errand — A “Billionairebot” suggests ways to outsource tasks. The example is finding a mobile notary for paperwork, rather than attending in person. Author-reported use. @ChrisJBakke
- G011 · Search for award travel — Search airline accounts for suitable redemption tickets. The author reports finding three first-class Japan tickets and deliberately stopping before booking because dates were undecided. Author-reported use. @congressdj
- G012 · Buy cinema tickets — Lenny Rachitsky reports using the bot to obtain IMAX Odyssey tickets. Seat selection, price and purchasing steps are not described. Author-reported use. @lennysan
- G013 · Complete online purchases overnight — A comparative tester reports both Grok Bot and Instinct buying items overnight. The password-reset anecdote in the same post belongs to Instinct, not Grok Bot. Author-reported use. @illscience
- G014 · Prepare an overlooked school photo order — A parent describes the bot ordering a kindergarten photo through Walgreens. The source is an account of the action, not a receipt audit. Author-reported use. @startupstella
- G015 · Plan a date — An author credits Grok Bot with arranging a date. The short post does not establish reservations or other completed logistics. Brief author report. @agrimsingh
- G016 · Find neglected personal commitments — An ongoing audit covers forgotten follow-ups, expiring return windows, overdue appointments, rising bills and unfinished commitments across email, calendar and files. Author reports work in progress. @toddsaunders
- G017 · Suggest changes to improve personal wellbeing — Review email, calendar and Slack to suggest ways to make life happier. Reported as a favorite use case, without measured outcomes. Author-reported use. @lennysan
- G018 · Triage an inbox and unsubscribe from marketing — Organize messages, identify what needs attention, and remove unwanted marketing. Several authors report inbox cleanup; “inbox zero” remains a self-report. Author-reported use. @MatthewBerman · @toddsaunders · @congressdj
- G019 · Coordinate personal and work calendars — Search for conflicts, mirror personal events as work-calendar holds, and allocate time for tasks and deep work. Author-reported use. @MatthewBerman · @mattyp · @ryancarson
- G020 · Find information across accounts — Search multiple Gmail, Slack and workspace connections for scattered information such as an event invitation. Author-reported use. @mattyp
- G021 · Meeting summaries and action items — Convert meetings into concise notes and follow-up tasks. The saved source lists the use case without detailing the recording pipeline. Author-reported use. @MatthewBerman
- G022 · Triage customer-support emails — Sort support requests as part of a recurring workflow. Lenny reports hours saved; the captured post does not establish autonomous resolution of every ticket. Author-reported use. @lennysan
- G023 · Keep an outbound CRM coordinated with a chief of staff — Ryan Carson describes a dedicated CRM bot managing his outbound funnel and coordinating with the bot handling email, calendars and tasks. Author-reported use. @ryancarson
- G024 · Negotiate sponsorships from inbound email — Research rates and negotiate brand deals. Alex Finn reports a $10,000 deal and later two deals; these are related updates, not independently confirmed revenue. Author-reported use. @AlexFinn · @AlexFinn
- G025 · Prepare contract redlines — An author reports two contract reviews and returned redlines. Legal correctness and acceptance of the changes were not assessed. Author-reported use. @AlexFinn
- G026 · Fulfill flower-shop orders through local florists — A creator reports building a Whop flower shop whose orders are fulfilled using Grok Bot. Volume and successful deliveries are not stated. Author-reported use. @stevenzhang
- G027 · Accounting assistance — An author says Grok Bot completed accounting work. The short post gives no scope, reconciliation checks or accountant review. Brief author report. @SherryYanJiang
- G028 · Gather documents and prepare taxes — A user reports finding tax documents in a large email archive and preparing taxes. No filing confirmation or accuracy review is provided. Author-reported use. @congressdj
- G029 · Qualify prospects and prepare outreach drafts — A promotional first-person account describes prospect research, approval-gated outreach drafts and nightly reporting. Reported weekly output is unaudited. Promotional author report. @ridark_eth
- G030 · Run newsletter operations with a bot team — Greg Isenberg describes Billy Howell using bots in his newsletter business. Counted as a reported operating setup, not proof of the income predictions around it. Secondary account of a user workflow. @gregisenberg
- G031 · Republish X posts to other social channels — Detect new X posts and cross-post to LinkedIn, Threads, Facebook and Bluesky, according to the creator. Author-reported use. @jackfriks
- G032 · Turn a large travel-media folder into an aftermovie — Reconstruct a Japan trip from nearly 600 photos and videos and produce a finished video. Metadata identifies @agrimsingh as the author. Author-reported use. @agrimsingh
- G033 · Edit audio across a large video collection — An early tester supplied a Dropbox link to 30GB of videos and reports having the audio edited. Author-reported use. @agrimsingh
- G034 · Clip a podcast and prepare the accompanying post — Cut a requested YouTube time range, then pass the clip to research and writing bots for quotes and captions. @KanekoaTheGreat is the source author. Author-reported use. @KanekoaTheGreat · @kloss_xyz
- G035 · Draft podcast takeaways and promotional ideas — Make a first pass at key takeaways and promotion after recording a podcast. Author-reported use. @lennysan
- G036 · Research gaps and sources for articles — Use Grok Bot alongside Perplexity to find questions, research and conflicting explanations before the author develops the argument. Article reach is not a measured bot effect. Author-reported use. @Av1dlive
- G037 · Find outlier YouTube videos and notable X posts — A tutorial creator describes separate YouTube-research and X-scout bots and later reports continuing to use both. Author-reported use. @petergyang · @petergyang
- G038 · Produce a daily AI-news feed for a community — Collect AI news and post it to the author’s community. Author-reported use. @AlexFinn
- G039 · Rank a thousand posts with Jev, then surface five tips — Retrieve 1,000 agent posts with the X API, rank them through Jev pairwise comparisons, and have Grok Bot return five. Jev supplies the ranking component. Author-reported use. @daniel_mac8
- G040 · Operate a content team with a publishing gate — A creator describes seven roles spanning research, writing, visuals, analytics, scheduling and publishing. The post explicitly retains human approval for publication. Promotional author report. @1920web1080
- G041 · Audit products, build landing pages and run campaigns — A SpaceXAI marketer describes these as existing team workflows while announcing a demonstration. Campaign results are not supplied. Team-reported workflow; demonstration announced. @joshkim
- G042 · Research emerging AI products into a structured brief — A user reports a 24-hour run searching X and the web, comparing sources and filtering promotional noise. Output quality was not independently checked. Author-reported use. @Lummox_eth
- G043 · Merged pull request → updated Intercom help article — Check whether a merged change affects a workflow, update or create the relevant article, and capture screenshots from a test account. Author-reported use. @damonchen
- G044 · Bookmarks → a working demo every morning — Review X bookmarks, dispatch a Cursor agent, check screenshots or video, and send a Cloudflare preview link. A repost is merged with the original workflow. Author-reported use. @mattyp · @RoundtableSpace
- G045 · App feedback → a bug-fix pull request — Monitor Creator Buddy bug feedback, ask Cursor cloud agents to fix issues, and push pull requests. Author-reported use. @AlexFinn
- G046 · Migrate a personal site from Super to Astro and Netlify — Move nearly 100 essays away from a paid Notion-backed site. The author reports a five-minute migration and links the resulting website. Author-reported use. @thisiskp_
- G047 · Navigate App Store submission and review — The app was built with Grok 4.6; Grok Bot handled browser-based submission forms and review questions. Its claimed bath-temperature sensing was not validated. Author-reported use. @luismbat
- G048 · Product plan → Cursor Cloud implementation → live walkthrough — An author describes directing the plan while bots divide the work, implement it, and click through the live product in a recurring check. Author-reported use. @fr321x
- G049 · Coordinate Codex for UI design — A user reports Grok Bot orchestrating a UI-design workflow with Codex. This is a combined setup, not a Grok-only result. Public metadata retrieval failed; this entry relies on the saved text. Saved author report; metadata unavailable. @TheAlexYao
- G050 · Reddit problem → micro-SaaS prototype — An author reports finding a Reddit pain point and building a corresponding application. Customers and revenue are not established. Author-reported use. @AlexFinn
- G051 · Build a visual office for a bot team — Create a 3D display of the author’s bots for a second monitor. Author-reported use. @AlexFinn
- G052 · Create a journaling shortcut and improve desktop notifications — Build an Omarchy journaling TUI and add a missing notification close button. The posts conflict on which tool led the OS installation, so that claim is omitted. Author-reported use. @AlexFinn
- G053 · Port Doom to an ESP32-S device — An author reports porting Doom to the device. Performance and the repost’s ten-minute claim were not independently tested. Author-reported use. @yunta_tsai · @elonmusk
- G054 · Keep a personalized homepage current — A podcast host describes a designer’s bot-maintained personal homepage shown in the episode. Secondary description of a demo. @clairevo
- G055 · Figma production and voice memo → code — The same episode describes “Figma Bro” handling design production and voice memos becoming code. These are presented as a workflow suite. Secondary description of a demo. @clairevo
- G056 · Supervise cloud coding agents and request missing evidence — A livestream viewer describes a supervising bot reading worker transcripts and asking for screenshots or performance results before returning work. Secondary livestream account. @dedene
- G057 · Correct a product-funnel diagnosis before building — A livestream account describes a data bot correcting the funnel stage at fault before handing the task to a product bot. Secondary livestream account. @dedene
- G058 · Take live-stream notes with screenshots — An author describes the bot following the Galaxy broadcast and extracting relevant moments and screenshots. Metadata identifies @XFreeze as the author. Author-reported use. @XFreeze
- G059 · Lecture URL → a mathematical study-sheet PDF — A creator offers a template producing compact lecture notes with Typst math, diagrams and SymPy formula checks. Template quality was not independently tested. Creator-reported template. @tetsuoai
- G060 · Watch for model-release announcements — Check X every five minutes for new releases, according to the author. Author-reported use. @AlexFinn
- G061 · Produce topic-specific political briefings — A user describes an hourly update bot tailored to the topics needed at work. Accuracy and source balance were not evaluated. Author-reported use. @congressdj
- G062 · Summarize podcasts, newsletters and X; track topic sentiment — An interview account describes Gavin Baker setting up summarizers and sentiment monitors. Timing claims refer to setup, not proven ongoing execution speed. Secondary interview account. @a16z
- G063 · Access space-industry research through an MCP connection — A research provider describes using Grok Bot as a preferred client for its research connector. Aggregate engagement numbers are not Grok-specific. Author-reported use. @aaronburnett
- G064 · Explain fluid dynamics with a simulation — A creator describes using Grok with Bot for a Navier–Stokes and airfoil simulation. The exact split between model and harness is not established. Author-reported use. @yunta_tsai
- G065 · Test installing and playing classic games — A tutorial author tested a gaming bot with Doom, Red Alert and Commander Keen. The post does not establish that all games ran successfully. Author-reported test. @petergyang
- G066 · Run a daily executive standup — Have specialist bots report progress, weekly goals and next actions, with a chief of staff coordinating the routine. Author-reported use. @AlexFinn
- G067 · Have a chief of staff define and brief its team — A user describes asking the manager bot to propose roles, install its instructions and create specialists after an overcomplicated setup failed. Author-reported use. @coreyganim · @AleiahLock
- G068 · Maintain a bot registry and back up the workspace — “Overwatch” tracks bots, pushes the workspace to Git hourly on workdays, cleans folders and archives temporary files. Author-reported use. @scheemunai
- G069 · Coordinate an Obsidian knowledge graph — A user describes twenty note-processing bots plus a coordinator, with source requirements and human approval for irreversible actions. The scale is self-reported. Promotional author report. @0xtoriin
- G070 · Turn a screen demonstration into a reusable skill — An early tester reports recording a workflow and testing the resulting skill on Taobao. Shopping success is still described as an experiment. Author-reported experiment. @agrimsingh
- G071 · Clean a computer’s stale files — An author lists computer cleanup as an active use case; another describes screenshot cleanup as work in progress. Author-reported use. @MatthewBerman · @toddsaunders
- G072 · Command a robot mower remotely — A user reports starting and docking a mower fifty miles away. A vacuum integration in the same post is a future plan, not a completed workflow. Author-reported use. @SawyerMerritt
- G073 · Flag abusive replies from suspect accounts — Jason describes inspecting account age, follower count and insults to flag replies. Automatic removal is expressed as an intention, not a verified outcome. Author-reported use. @Jason
- G074 · Marketing OS role pack — A creator advertises a multi-role pack covering SEO, ads, copy, launches, pricing and analytics. Listed roles do not prove every workflow ran. Creator or vendor availability claim. @vladdubchak_x
- G075 · Higgsfield commercial and ad-variant workflows — The integration announcement proposes commercials, variant tests and localization. No customer campaign outcome is established. Creator or vendor availability claim. @higgsfield
- G076 · A phone number, calling and texting for bots — Bland advertises a Bot template for inbound and outbound calls and texts; Matt Palmer’s tutorial includes a live call. Historic promotional pricing is not repeated. Creator or vendor availability claim. @mattyp · @usebland
- G077 · Control an iPhone or iPad through Sightless — The creator says existing Grok Bots can operate a device through the macOS app. Grok-specific success is not separately demonstrated in the captured text. Creator or vendor availability claim. @BenjaminBadejo
- G078 · Operate rented iPhones for social workflows — Pamba advertises an MCP connection for posting and analytics on physical phones. Claimed reach and capacity are vendor reports, not Grok-specific results. Creator or vendor availability claim. @karolzdeb · @karolzdeb
- G079 · Trigger a routine with a webhook — Official and employee posts describe webhook support and possible triggers. Those example automations are suggestions, not all completed builds. Creator or vendor availability claim. @mattyp · @ericzakariasson
- G080 · Prediction-market experiment that lost its bankroll — A team member reports a bot turning $100 into a $210 balance on weather contracts before losing it on sports betting. No transaction history is provided. Secondhand report; loss disclosed. @codyschneider
- G081 · Crypto research and execution desk — A promotional account describes research, wallet monitoring, risk checks and trading bots, with a claimed $13,100 week. Returns and execution claims are unaudited. Promotional claim; returns unverified. @ridark_eth
- G082 · Token-launch fee experiment — An affiliate-linked post claims fees from six token launches. It supplies no audited basis for treating the income as reliable or repeatable. Affiliate-linked claim; returns unverified. @0xboan
- G083 · Self-funding prompt that led to unwanted outreach — An anecdote says a bot asked coworkers for paid work, an advance and a loan after being told to fund its subscription. Treat as a failure anecdote, with uncertain seriousness. Unverified failure anecdote. @0xz80
- Work can silently stall. @awilkinson reports bots disappearing mid-task; @Voxyz_ai reports similar failures and login friction.
- Some sites block the cloud browser. The same Voxyz account reports different behavior across sites and the need to preserve setup files across updates.
- Conversation is not a progress dashboard. @SherryYanJiang asks for clearer task structure and describes some jobs as slow.
- Recurring schedules still consume resources when quiet. A Galaxy viewer’s account describes routine audits and missing verification evidence.
- Reported money is not verified revenue. The catalog keeps negotiation claims, trading losses and affiliate-linked income claims explicit rather than treating them as validated business outcomes.
Bank-account access proposals; hypothetical directory and local-SEO businesses; proposed penny-stock website outreach; future Jev event-routing integrations; the planned GoHighLevel handoff; generic “99% of users / 20 agents” course promotions; giveaway requests; launch announcements; and competitors that merely compare themselves with Grok Bot.
The three-day Galaxy company build is source context, not proof that a viable company or paid business resulted. Specific workflows described in the captured accounts are included above. Short GTM teasers and media-only roundups were not expanded into invented use cases.
See rankings.md in this gist for 15 editorial picks and a capability portrait. Rankings reflect workflow clarity and practical usefulness, not independent product tests.