New Bots worth adding, picked from this week’s listings
Plan, limit and app changes, with sources
Incidents and what to do about them
Free starter pack when you join: the printable workflow checklist and our 16 best Bots by task.
How your email is used
We store your email privately in a dedicated Grok Bot Wiki list in Resend, to send the emails you ask for. We don’t sell your email or include it in site analytics. Every email has a way to unsubscribe.
Rakazo swaps its Box sandbox for Boat; MausBot cuts its entry price to $15 and adds triggers
The weekly ecosystem watch rechecked Rakazo's and MausBot's READMEs. Rakazo's optional sandbox-provider list now names Boat where it previously named Box. MausBot's README adds a Triggers (schedules and webhooks) feature, and its pricing page now lists a $0 Free tier and a $15 Starter tier in place of the $29 tier this guide previously carried. GitHub star counts for 12 watched repos were refreshed; no new comparison guide was drafted this run.
Comparisons
The Grok Bot alternatives guide's Rakazo row and prose now read Boat instead of Box among its sandbox/compute providers (Docker, E2B, Daytona, CreateOS, Boat, Railway or local), matching the README's Features, Stack, Quick start and server-install sections, all of which switched together. The MausBot paragraph adds one sentence on a new Triggers system — schedules, webhooks and app-event triggers with a sidebar run-history page — and the pricing figures were rechecked directly against mausbot.com/pricing rather than trusted from a prior check: a new $0 Free tier appeared, the entry paid tier is now called Starter at $15/month (was $29), and Pro and Max now include a monthly Claude credit on top of the existing one-time trial credit; Pro ($49), Max ($99) and the team tiers are unchanged. OpenClaw's getting-started page was also rechecked with no material change. See docs/research/ecosystem-log.md for the full star-count table, the community-piece search (nothing qualified this run), and the competitor/marketplace notes, including grokbotsdirectory.com's pagination growing to roughly 250 pages.
Sign-in guide adds an account-linking cause for stuck local-tool permission
The Cursor forum's grok-bot tag was rechecked for threads active in the last week. One new thread cleared the bar: local tool execution stuck on "Never" despite Settings showing Always allow, traced by the reporter to X, Grok and Cursor logins pointing at different accounts. The sign-in guide now covers it alongside the official account-linking note it already carried.
Fix problems
A thread opened October 16 (7 replies, 346 views as of today) described Grok Bot refusing every local action on a Mac with "Local tools are turned off. The user has set local tool access to 'Never'", even after setting Execution on Local Computer to Always allow, and only on one account while other accounts on the same machine worked normally. The reporter found the cause was account linking: their X and Grok logins were on one account while Cursor was signed into another, so the local-tool permission never synced between them; merging the Cursor account into the same login fixed it. A Windows 11 user replied the same day with an identical symptom after upgrading to X Premium for Cursor and Grok Bot access, unresolved as of this check. Cursor has not posted a staff reply in the thread. The sign-in guide's "What the Windows threads found" section now cites this case, since it reinforces the existing FAQ point that signing in alone does not link or combine X, Grok and Cursor accounts. No other thread on the tag page cleared the 10-reply/300-view bar this run without already being linked from an existing guide; the official troubleshooting page (last updated October 12) and the CellCog problems tracker (last updated September 7) were both rechecked with no material change since our last read.
64 new Bot listings this week, 5 retirements, and a stalled daily sweep
This week's catch-up sweeps added 64 new directory listings, led by personal-admin (43), and five Bots retired after their share links stopped resolving. The automated daily sweep has not completed successfully since October 8, and the catalog hasn't grown at all since October 14.
DirectorySite health
64 rows were added between October 10 and October 14 — personal-admin picked up the most (43), followed by content-publishing (9), research-briefings (6), inbox-calendar (4), coding-shipping (1) and customer-sales (1); new entries include Zambo Receipt Bot, Weekly SEO Brief, Traffic Drop Watch, Tool Finder and Ancestry Bot. Fab Four, Little x, Porter, RIZALBOT and SniffBot retired this week after their share links stopped resolving; readers who bookmarked those pages now see a noindex retired notice instead. The scheduled daily sweep (`bots-daily.yml`) has failed every run since October 8 — the weekly health audit traced this to a GitHub Actions budget gate on the repository, confirmed from the job's own check-run annotations, not a bug in the sweep scripts. Two manual catch-up runs on October 11 and 14 are the only reason the directory grew at all this week; no new rows have landed since October 14, so the catalog is now three days stale as of today. Resuming automated sweeps needs an owner-authorized change to the repository's Actions budget — nothing here was changed without that. See /bots/changes for the full weekly breakdown and the retired-link list.
Rakazo adds Railway sandboxes; MausBot adds BotMRR teams and voice calls
The weekly ecosystem watch rechecked Rakazo's and MausBot's READMEs. Rakazo's optional remote sandbox providers now include Railway alongside Docker, E2B, Daytona, CreateOS and Box. MausBot's README now names BotMRR as a source for installable multi-Bot teams and documents a voice/calling feature. GitHub star counts for 12 watched repos were refreshed; no new comparison guide was drafted this run.
Comparisons
The Grok Bot alternatives guide's Rakazo row and prose now list Railway as a sandbox/compute provider option, matching the README's quick-start and setup sections. The MausBot paragraph now credits BotMRR, a site of outcome-driven team listings, as a source for the one-Markdown-file team install (alongside any other .md file), and adds one sentence on its voice/calling feature (ElevenLabs, Fish Audio, Grok/xAI keys, built-in Mac voices, local Chatterbox; calls stay macOS-only). MausBot's pricing page was rechecked directly and still matches this page's figures. OpenClaw's getting-started page was also rechecked with no material change. See docs/research/ecosystem-log.md for the full star-count table, the community-piece search (nothing qualified this run), and the competitor/marketplace notes, including that grokbotsdirectory.com's listing count (4,714) has overtaken our own live catalog (3,471) for the first time.
The X Subscription, Grok Bot 0.70.2, and an October 13 routines incident
SpaceXSI launched The X Subscription on October 12: Grok Bot now comes with Premium ($30), Super ($100) and Ultra ($200), not Free or Plus, and existing Cursor and SuperGrok plans keep working. Twelve guides now cover releases 0.69.0 to 0.70.2, and the Fix problems guides add the October 13 routine-trigger incident.
Pricing: the plan guide leads with The X Subscription's tiers, annual prices, team seats and the shared weekly usage pool, explains what existing Cursor, SuperGrok and X Premium subscribers can do (keep their plan, or switch with a prorated refund; switching is permanent, and an App Store-billed Cursor plan must be cancelled with Apple separately), and lists where official pages disagree: x.ai/bot and Cursor's help still describe the older plans while cursor.com/pricing shows only the new tiers. Its title changed because the old $20 entry price is no longer what Cursor lists. The usage, getting-started, Team Bots, comparison and glossary pages were updated to match. Releases: the 0.69.0 to 0.70.2 changelog entry (October 11) adds Bot email addresses whose sends wait for approval, X search without an X account, in-chat app cards, payments with X Money or Stripe Link, a check for your approval before irreversible actions, Team Bot approvals from a teammate's own messages, and many connector and Gmail fixes; the what's-new, safety, plugins, Gmail, platforms and other guides now reflect it. The Secure Form password-in-snapshot issue still has no confirmed fix as of October 14, so keep typing passwords yourself. Fix problems: Cursor posted an October 13, 17:52 to 20:29 UTC incident in which many event-triggered routines did not run and will not be retried; resend events from that window. The live status table now shows Grok Bot notices posted without a component. Settings paths were corrected to the new Settings → Computer → Bot's computer layout, and the sign-in guide notes that Cursor sign-in moves to accounts.spacex.ai and accounts.x.ai on October 30, which filtered company networks need to allow. Nothing was purchased or tested by us.
Settings moved the computer-update control; a new October 13 outage
The Cursor forum's grok-bot tag was checked across its last five pages of activity. One new thread cleared the 300-view bar: a staff-confirmed root cause for the local-exec daemon dropping on unattended, locked Macs. The official troubleshooting page also moved rebuilding the cloud computer out of Settings → Updates into its own Settings → Computer section, which three guides now match, and a new October 13 outage was added to the status guide.
Fix problems
The tag's first five pages (150 topics, covering activity back to October 5) were checked against a 7-day window with a 10-reply-or-300-view bar. Most qualifying threads were already cited. Two were not: a 310-view thread in which Cursor staff (Colin) explained that the desktop app's local-exec daemon is deliberately stopped by a power-saving behavior when a Mac is locked or the Grok Bot window has been backgrounded, and only restarts once someone is back at that machine, not when a Bot requests it remotely — the routines-not-running guide's local-execution paragraph now cites this as the root cause, with the thread's later Windows, Mac Studio and Mac-mini-fleet reports as corroboration. The other was a five-week-old 'Grok bot failed to respond' thread that picked up fresh replies during the October 6 outage and got the same staff answer (no reset needed); it's now cited in the not-responding guide alongside the incident's other thread. Four other candidates were checked and left out of Fix problems: an X Subscription announcement, a Bot-info-pane UI feature request, a Microsoft-connector feature request, and a plan-access rollout question — none describe a reproducible Fix problems symptom. Reddit's r/GrokBot blocked the request (403) even with a browser user agent; we continued without it, per policy. Separately, Cursor's official troubleshooting page, last updated October 12, now rebuilds the cloud computer from its own Settings → Computer → Update Bot's Computer rather than from Settings → Updates (which still only checks app updates); the not-responding, routines-not-running and sign-in-error guides are corrected to match, and the routines guide's checklist picked up two items from the same update (event-trigger validity, and Test run performing real actions). The status guide adds a October 13, 00:22–03:07 UTC incident that affected the IDE, Cloud Agents, Automations, Grok Bot and Origin together; Grok Bot itself recovered by 01:49. The CellCog tracker and Cursor's status history were otherwise unchanged since the last check.
Every guide rechecked: Grok Business seats, Bot email, October outages
All 26 guides were checked against the October 11 help pages, docs, forum staff replies and status history. New: Grok Business seats include Grok Bot, Bots can have their own email address, @bot on X, Cursor's official plan pairings, and the October 7–9 incidents. The maker now brands itself SpaceXSI.
Corrections: the getting-started guide described separate link buttons before sign-in; you now sign in first and link from there, and a SuperGrok link can be made from the phone's paywall, not only on desktop. The plan guide replaces 'tiers line up by name only' with Cursor's own pairing (Pro with SuperGrok or X Premium+, Pro+ with SuperGrok Plus, Ultra with SuperGrok Heavy). The Team Bots guide now follows the October 8 docs on managers. Comparisons picked up new ChatGPT, Claude, Manus, Hermes and MausBot prices and plans. The status guide adds the October 7, 8 and 9 incidents, and the routines guide covers the October 8–9 scheduler failures. The Secure Form password issue still had no posted fix on October 11. Tables on guide pages are now readable on phones.
This week's daily sweeps added 341 new directory listings across all eight categories, led by personal-admin (169) and research-briefings (47), bringing the live catalog to 3,376 entries. Four Bots retired after their share links stopped resolving, and the October 9 sweep run failed before it wrote anything.
Directory
The catalog grew by 341 rows between October 3 and October 7 — personal-admin added the most (169, including Aaron, Event Finder and Admissions Wizard), followed by research-briefings (47, including Apex and Bet Tester), inbox-calendar (38), content-publishing (28), finance-ops (19), customer-sales (14), teams-handoffs (14), and coding-shipping (12). Beowulf, gb-live, Sunlight, and Marcus Aurelius retired this week after their share links stopped resolving; readers who bookmarked those pages will now see a noindex retired notice instead. The October 9 daily sweep run failed at the runner-startup stage before any row was written, so no new rows landed that day; the weekly health audit flagged it for the owner to watch and no reader-facing content was affected. See /bots/changes for the full weekly breakdown and the retired-link list.
Ecosystem watch: MausBot adds team installs, no new alternative crosses the bar
This week's star-count and README check found MausBot's README now documents installing a full Bot team from one Markdown file and an auto-routing room mode; the alternatives guide's MausBot section picked up one sentence. Rakazo's tool sources, OpenClaw's Node requirement and channel list, and MausBot's cloud pricing all rechecked unchanged. No tracked alternative repo newly crossed 1,000 stars without existing coverage, and no community comparison piece this week cleared the named-author bar.
ComparisonsStart here
The weekly watch re-read MausBot's README and found two features not yet in our guide: installing a full multi-Bot team from one Markdown file (with a review screen before anything is created) and an "Auto" room mode that routes an unmentioned message to the best Bot; the Grok Bot alternatives guide's MausBot paragraph and updatedAt now reflect that. Rakazo's README (tool sources: Composio, Pipedream, Treg, remote MCP, OpenAPI), OpenClaw's getting-started page (Node 24.16+ or 26.1+, channel list), and MausBot's pricing page ($29/$49/$99 cloud workspaces, AI usage not included) were all rechecked in full and matched the guide's existing facts, so those parts were left untouched. Among the twelve tracked repos, rome-os/rome grew to 727 stars and OnlyTerp/opengrok to 474, both still below the 1,000-star bar; Rakazo (3,476), OpenMausBot (4,185) and gawkbot (1,488) are all over that bar but already have dedicated comparison coverage inside the alternatives guide (their standalone grok-bot-vs-* pages redirect there since October 7), so no new guide was drafted. GitHub API access worked this run (via the repository search endpoint) and gave exact star counts and pushed_at timestamps for all twelve repos; see docs/research/ecosystem-log.md for the full table, deltas against last week's rounded figures, and the competitor-directory notes (botdirectory.ai, grokbotsdirectory.com, grokbotlist.com, and the official Marketplace). x.ai/news could not be checked again (Cloudflare blocked every attempt). No web search for a new third-party comparison piece, restricted to the last 7 days with a named author or established publication, turned up anything that cleared the bar; no community links were added.
One pricing page, eight new guides, and guides that link to each other
The pricing and plan guides are now one page with yearly prices and the mobile purchase rules. New guides cover getting started, plugins and MCP, safety, Team Bots, October's releases, a glossary, Obsidian and Gmail. Seven thin or overlapping guides now redirect to stronger pages.
Corrections: the What is Grok Bot page said xAI acquired Cursor; SpaceXAI's own wording is that Cursor became part of SpaceXAI on August 14, three days after Grok Bot launched. The plan guide now notes that SpaceXAI announced the SuperGrok, Cursor Pro and Teams tiers on August 26, adds yearly prices from Cursor's pricing page ($16, $48 and $160 a month for Pro, Pro+ and Ultra; $32 and $96 per Teams seat) and Cursor's rule that only monthly plans are sold in the mobile apps. The platforms guide lists Windows 10 and 11 from the x.ai/bot download list. The Marketplace guide reflects that Bot templates left the in-app Marketplace in 0.63.0 and moved to the web when it became Connect Apps in 0.67.0. Redirects: the pricing, access and download guide goes to the plan guide; the stuck-Bot triage guide to the not-responding guide; the morning brief and two-Bot handoff guides to their workflow recipes; and the Rakazo, OpenMausBot and gawkbot comparisons to a new alternatives guide. Guides now link to each other and to matching directory listings, and the best-Bots picks were re-reviewed against their current descriptions. Sources are the official docs, Cursor's help pages, the changelog and attributed forum replies; nothing was tested by us.
A free workflow checklist, and optional help putting a plan together
Five readiness questions and a downloadable blank brief are now free to use. The independent Workflow Studio adds a $199 audit and a $749 total setup for one agreed workflow, starting with an enquiry.
Workflow planningOptional services
The checklist helps define a task, inputs, output, acceptance checks and boundaries. It does not run or validate a Bot. The studio explains its scope, pricing and an explicitly illustrative sample audit; no customer result or performance claim is implied. The setup total includes the audit. Enquiries are reviewed for fit and availability before any work or payment is agreed. Free guides and editorial ranking remain independent of purchases.
Shared-computer guide picks up a 990-view thread on context pruning
This week's Cursor forum tag check found one thread clearing the 10-reply-or-300-view bar in the last 7 days: a long-running request to prune or compact a Bot's context without creating a new Bot. The shared-computer guide's start-fresh section and FAQ now cite it, including staff confirmation that an explicit new-session, Compact, and working-set meter are still unshipped.
Fix problems
The grok-bot tag's two most recent pages (60 topics) were checked against a 7-day activity window; only one thread cleared the 10-reply-or-300-view bar, a 990-view, 26-post thread opened August 13 asking SpaceXAI to let a Bot's context be pruned or compacted without spawning a new Bot. Cursor staff (deanrie) replied across August 20, September 23, and September 30: durable state already lives apart from the transcript and survives a reset, a new chat on the same Bot already starts with a clean working set, but an explicit same-Bot new-session-with-archive control, a manual Compact, and a visible working-set meter are not shipped and have been passed to the team with no ETA. The shared-computer guide's 'Long threads, and how to start fresh' section and its context FAQ now cite this, plus the thread's community workaround of a durable per-Bot notes file a routine rewrites each session. Two other qualifying threads were considered and left out: a 734-view feature-request thread on shared team rosters (resolved when Team Bots shipped September 30, but a feature announcement rather than a fix-problems symptom) and a 389-view Grok Bot vs Cursor Projects/Automations positioning Q&A, which doesn't describe a reproducible symptom any Fix problems guide covers. The official troubleshooting page (last updated September 16 per its own byline), the CellCog problems tracker (last updated September 7), and Cursor's status history were rechecked and had no content not already reflected in the guides; the status history page still does not render its incident list to a plain fetch. Reddit's r/GrokBot blocked the request (403); we continued without it, per policy.
962 new Bot listings, a plan-guide trial correction, and every correction link now opens an email
This week's daily sweeps added 962 new directory listings across all eight categories and retired two Bots whose share links stopped resolving, bringing the catalog to 3,038 live entries. Every correction link on the site — on Bot pages, works-with hubs, the workflow review sheet, and the contact and privacy pages — now opens a prefilled email instead of a GitHub issue queue that returns 404 to the public, and the plan guide picked up a real correction about a renewing trial offer.
DirectoryPricing guideEditorial correctionsSearch
The catalog grew by 962 rows between September 26 and October 2 across all eight categories — personal-admin added the most (364), followed by research-briefings (200) — bringing live listings to 3,038; Coach Tony and Marcus Aurelius retired after their share links stopped resolving, and ten more Bots picked up hand-written 'Our take' entries. Readers who click 'report a correction' from a Bot page, a works-with hub, the workflow review sheet, or the contact and privacy pages now get a prefilled email draft instead of a link to the GitHub issues queue, which returns 404 for anyone without repo access since the source repository is private; Bot submissions still go to the private review queue first and fall back to the same email draft if that queue is unavailable. The 'Which plan for Grok Bot' guide now distinguishes the Grok Bot usage-credit trial, which never renews, from an Apple App Store introductory offer, which renews into a paid Apple subscription unless cancelled in Apple ID → Subscriptions — readers trying a plan on iOS should check which offer their account is showing before confirming it. The MCP template-search tool was also tightened to require every search term to match rather than just half, so a multi-word search through Grok Bot's own MCP connection returns fewer off-topic Bots.
Ecosystem watch: Rakazo picks up Treg, no new alternative crosses the bar
This week's star-count and README check found Rakazo added Treg as a user-installed tool source; the OpenMausBot and OpenClaw comparisons held up unchanged against their current docs. No tracked alternative repo newly crossed 1,000 stars without a guide, and no community comparison piece this week cleared the named-author bar.
ComparisonsStart here
The weekly watch re-read Rakazo's README and found it now lists Treg alongside Composio, Pipedream, MCP, and OpenAPI as a tool source; the Grok Bot vs Rakazo guide's Tools row and updatedAt now reflect that. OpenMausBot's README and OpenClaw's getting-started page were both rechecked in full and matched their guides' existing tables and prose, so neither guide's date was bumped without a real change. Among the twelve tracked repos, rome-os/rome grew from 523 to roughly 661 stars but remains below the 1,000-star bar for a new comparison guide. This sandbox's GitHub API access was unavailable this run, so star counts are GitHub's rounded on-page figures rather than exact API counts; see docs/research/ecosystem-log.md for the full table, deltas, and the competitor-directory notes (botdirectory.ai, grokbotsdirectory.com, grokbotlist.com, and the official Marketplace). x.ai/news could not be checked (Cloudflare blocked every attempt). No web search for a new third-party comparison piece, restricted to the last 7 days with a named author or established publication, turned up anything that cleared the bar; no community links were added.
Fix problems guides: a corrected usage-pool answer, and a stuck update that recurred
Two guides pick up fresh forum evidence: a Cursor staff correction on how the weekly Grok Bot allowance and on-demand billing actually share (or don't share) Cursor's quota, and a second 43-percent-stuck-computer thread showing the update stall was not fully fixed on September 21 as earlier reported.
Fix problems
This week's Cursor forum tag check (30 topics on the grok-bot tag) surfaced two threads active in the last 7 days that cleared the 10-reply-or-300-view bar and described symptoms our six Fix problems guides already cover. The weekly-usage-limit guide now cites a 1,369-view thread where a Cursor staff reply first said Grok Bot used the same Cursor plan quota, then corrected itself after the user quoted the launch email: the weekly included Grok Bot pool is genuinely separate, but once it's exhausted, on-demand overflow bills from the same shared on-demand pool as the rest of Cursor usage. The not-responding guide now cites a second 43-percent-stuck-computer thread (12 replies) showing the stall that a first thread and staff reply seemed to close on September 21 continued through September 23, with one user reporting it unresolved for about two weeks; staff cleared accounts individually rather than announcing a systemic fix, so the guide's table and recovery text now say to report the issue in-thread rather than expect it to be over. A third thread that cleared the view threshold, a privacy/Legacy-Privacy-Mode Q&A, didn't describe a reproducible fix-problems symptom and was left out. The official troubleshooting page and the CellCog problems tracker were rechecked and had no new content since the last pass; Cursor's status history page did not return its incident list on this fetch, so status.cursor.com/incidents links already in the guides stand unverified this round. Reddit's r/GrokBot blocked the request (403); we continued without it, per policy.
777 new Bot listings this week, one retirement, three dead forum links fixed
This week's daily sweeps added 777 new directory listings across all eight categories and retired one Bot whose share link stopped resolving, bringing the catalog to 2,078 live entries. The weekly site health audit checked all 412 non-slug pages plus a sample of Bot pages, found no broken pages, and fixed three dead Cursor-forum links cited in the not-responding guide.
DirectoryFix problems
This week's daily sweeps (2026-09-19 through 2026-09-25) added 777 new directory listings across all eight categories — research-briefings (122) and personal-admin (266) picked up the most, every other category added at least 39 — bringing the catalog to 2,078 live entries. One Bot, AISØN Vice Captain, retired on 2026-09-19 after its share link stopped resolving. Separately, the weekly health audit fetched all 412 non-slug pages plus a 40-page sample of Bot pages, found zero broken pages or metadata issues, and caught three dead Cursor-forum threads that the not-responding guide cited for a specific incident description; those citations were removed and the sentence they supported was rewritten to match what the guide's remaining live sources actually say. Readers who bookmarked the not-responding guide's forum links should reload the page to see the corrected citations. This week also shipped a new Grok Bot vs gawkbot comparison, five other new guides, and a refresh of eleven existing guides against current sources — see the entries below for specifics on each.
A fourth open-source comparison: Grok Bot vs gawkbot
gawkbot passed 1,000 GitHub stars as a self-described open-source Grok Bot with no existing comparison here, so it gets a verdict page alongside Rakazo and OpenMausBot. Rakazo and OpenMausBot's guides also pick up two real changes: a new sandbox provider and a terminal install option.
ComparisonsStart here
The weekly ecosystem check found najmuzzaman-mohammad/gawkbot at 1,463 stars, actively pushed, with repository topics including grok-bot-alternative and a README that calls itself an open source Grok Bot — meeting the bar for a new comparison guide. Grok Bot vs gawkbot covers gawkbot's local-first, bring-your-own-CLI model, its approval gate on every external write, and its Sustainable Use License, which is source-available but not a permissive open-source license (it restricts commercial redistribution). The Rakazo comparison's sandbox-provider row now includes CreateOS, which Rakazo's README added since the last check. The OpenMausBot comparison's install row now covers its `npx openmausbot` terminal quick start alongside the existing desktop downloads. This week's web search for new third-party Grok Bot comparisons, restricted to pieces from the last 7 days with a named author or established publication, turned up nothing that cleared the bar; no community links were added. Full details, including GitHub star counts and a competitor-directory watch, are in docs/research/ecosystem-log.md.
Five new guides: status and outages, choosing a plan, templates, a three-way comparison, and platforms
New pages cover where to check whether Grok Bot is down, which plan to buy, how Marketplace templates work, how Grok Bot compares with ChatGPT Work and Claude, and which devices it runs on.
Fix problemsStart hereComparisonsPricing guide
Is Grok Bot down? lists Cursor's status page as the official source, notes that xAI's status page has no Grok Bot entry, and tabulates every September incident with UTC times. The plan guide turns Cursor's billing rules and staff replies (plans don't stack, links are permanent, Ultra and SuperGrok Heavy are the same top tier) into a decision table. The Marketplace guide explains what a shared template copies and leaves out, Public vs Team-only links, and the third-party bot terms. The comparison notes that OpenAI retired ChatGPT agent in favor of ChatGPT Work and that Anthropic merged Cowork into Claude on September 16; it compares documentation, not test runs. The platform guide lists builds, store listings and mobile and Linux limits, and records where official pages still disagree. Every claim cites a page checked today; nothing was tested by us.
Eleven guides updated: full plan table, September outages, routine and webhook fixes, fresh chats
The pricing guide now lists SuperGrok, X Premium+ and Teams alongside Cursor plans. Troubleshooting guides now cover the September outages and Cursor's routine and webhook fixes, and the ways to start a Bot in a fresh chat. Comparisons no longer say Grok Bot runs only xAI models.
Pricing guideFix problemsComparisonsWhat is Grok BotEditorial corrections
We rechecked every guide against the official docs, Cursor's plans page, the x.ai/bot pricing panel, and Cursor's status history. Corrections: the not-responding guide had dated the 180-plus-reply forum thread to August; it opened September 16, during status-page incidents on September 16 to 18. The routines guide now reports Cursor staff's explanation (queued and silently skipped runs, fixed September 15 to 16), and the webhook URL bug fixed in desktop 0.53.0. The shared-computer guide had said a Bot cannot start fresh; Cursor staff now recommend a new chat per task, and the docs describe Duplicate. The usage guide no longer says there is no spending cap: an on-demand monthly limit exists but does not stop a run in progress. Grok Bot security docs say Cursor chooses the model and the serving mix can change, so comparison tables no longer say xAI models only. The pricing guide now opens with a dated direct answer and the plan table; the not-responding guide adds a table of quoted error messages with their likely causes; nine guide titles were shortened, with URLs unchanged. Forum staff replies are attributed; nothing here was tested by us.
Fix problems guides: settings menu renamed, SSO sign-in note added
The official troubleshooting page moved computer recovery and app-update controls from Settings, Beta to Settings → Updates, added an SSO-specific sign-in check, and clarified that some sites require re-verification even after a Bot signs in. Three Fix problems guides now match.
Fix problems
This week's Cursor forum tag check found no new thread meeting the 10-reply or 300-view activity bar that describes a symptom our six Fix problems guides don't already cover; the two threads that cleared the view threshold were a plan-comparison question and a general 'what is Grok Bot' explainer, not troubleshooting reports, so neither was added as a source. The official troubleshooting page itself changed since our last check (last updated September 16, 2026): the Settings, Beta menu is now Settings → Updates for both Check for Updates and Update under Grok Bot's Computer, mobile has its own named controls, and the sign-in checklist now calls out organization SSO as a distinct failure mode. The not-responding, sign-in-error, and shared-computer guides were updated to match and re-cite the page.
Access corrections, readable mobile guides, and better Bot discovery
Corrected iPad and eligibility guidance, repaired mobile tables, and made directory search easier to use. Listings remain source descriptions, not independently tested recommendations.
GuidesDirectorySearchEditorial corrections
The September 19 update overstated an earlier link audit: a reachable page can still contain outdated claims. The later audit found factual drift, mobile overflow and analytics test gaps. We corrected those claims and are recording verified repairs in the repository remediation ledger.
First daily sweep: 149 new listings, one retirement
The daily verification job ran for the first time this week and added 149 genuinely new Bot listings, spread across all eight categories, then retired its first dead share link a day later. An earlier link audit checked reachability; its original freshness conclusion was overstated and is corrected in the September 20 update.
Bot directoryChanges feedSite health
The 149 rows added on 2026-09-18 are new by firstSeen, not part of the original catalog seed, and show up on /bots/changes grouped by week. Personal admin (46) and research & briefings (24) grew the most; every category picked up at least 11 rows. One row, AISØN Vice Captain, stopped resolving and was retired on 2026-09-19 after its share link 404'd — the first retirement since launch. Separately, a full route-by-route audit of the live site (165 pages, all data routes, all 34 external source links in the guides) found zero failures, but reachability did not establish content accuracy or usability. The September 20 audit identified further required fixes.
The Bot directory: 1,153 public share links, checked daily
Every public Grok Bot share link we could find, with the creator credited, a plain-words summary, category and collection pages, and a scheduled sweep that retires dead links.
Bot directorySubmissionsChanges feedHomepage
Submit your own through the checked form; new and retired links appear on the changes page, by RSS, and as JSON. Rows are seeded from community catalogs published under CC0 and CC BY 4.0, with per-row attribution kept on every page. A listing is not a test result and nothing is sponsored. The verifier only retires a row on a 404 and never writes when x.ai is unreachable. Ask for a correction or removal through the report link on any Bot page.
Pricing rechecked, three comparisons, and a Fix problems section
The pricing guide now carries the full plan table, the August timeline, and the trial terms. OpenClaw, Rakazo, and OpenMausBot comparisons give verdicts. Five new pages cover the problems people actually report.
Pricing guideComparisonsFix problemsStart here
Grok Bot access expanded three times in August and the official eligibility pages still disagree with the Cursor pricing page; the guide records both. Comparison verdicts are ours, based on documentation and attributed community head-to-heads, not on a published benchmark. Fix-problems pages combine the official troubleshooting order with linked Cursor forum threads; forum reports are attributed, not reproduced.
The field guide now includes morning briefing, competitor research, and a two-Bot research team, each with a fictional practice pack and an answer key.
Workflow libraryTeam recipesReader review sheets
These are authored recipes, not recorded Grok Bot runs. Download a practice pack, run it with your own Bot, and keep an assessment. The access and comparison guides link current official sources; conflicting eligibility descriptions are called out rather than reconciled by guesswork.
Found an outdated instruction or tried a recipe? Share the precise step and a public or sanitized example. Community reports stay distinct from independent tests.