THE FIELD NOTES

What changed.
What it means for you.

New recipes, meaningful corrections, and the workflows they affect. A dated record of this library—not a live product-status monitor.

Subscribe with RSS ↗

OpenMausBot's star count jumps again (+9,063 in a week); its README adds Channels, a named Jev decision model and resolves a team Claude-credit conflict

The weekly ecosystem watch rechecked Rakazo's and MausBot's READMEs. Rakazo adds `instabox` to its installer-only provider list but no headline feature changed. MausBot's README adds a Channels feature that splits Work, Personal and per-project contexts without cloning bots, names its Auto-mode decision model Jev, and documents a desktop companion mode over Tailscale; its pricing page also resolves a team Claude-credit figure this page had flagged as unconfirmed since October 29. GitHub star counts for 12 watched repos were refreshed; milind-soni/OpenMausBot jumped from 12,416 to 21,479 stars in one week, again the largest single-period delta in this log. No new comparison guide was drafted this run.

Comparisons

The Grok Bot alternatives guide's MausBot paragraph adds sentences on the Channels feature, the Jev-named decision model (Cloudflare Workers AI, TypeSafe Jev or OpenRouter key), and a desktop companion mode pairing a desktop build to another host over Tailscale. mausbot.com/pricing was rechecked directly: Team now clearly gives each teammate a one-time $5 credit when they join, Business and Business self-hosted list no Claude credit, and the "coming soon" list drops the team credit in favor of Slack/Telegram/iMessage messaging, a spending cap, research tools, bots in Slack and SSO. Rakazo's README adds `instabox` to its installer-only sandbox-provider list, alongside the already-unpromoted `boxd`; the Features and Stack sections are unchanged, so neither was added to the table. OpenClaw's getting-started page was also rechecked with no material change, so the grok-bot-vs-openclaw guide was left untouched. 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 reaching roughly 400 pages.

Explore the update ↗

Grok Bot 1.0 is out of beta: Bots join Google Meet, Zoom and Microsoft Teams calls, and Team Bots come to Microsoft Teams

The changelog's first 1.0 entry, 1.0.1, is dated November 11, and x.ai/bot now says Grok Bot is out of beta. On Team, Enterprise and Ultra plans a Bot can join a meeting from a link, answer in the meeting chat and send a summary. Team Bots can be brought into Microsoft Teams, and a Manager can share an app login with everyone who uses the Bot once a team admin allows it. Prices did not change.

Start hereBuild workflowsOperate safelyFix problems

Read in a browser November 12: the 1.0.1 changelog entry (also covering 1.0.0), SpaceXSI's Introducing Grok Bot 1.0 post (dated November 2 on its page, not listed on x.ai/news at our November 11 check) and x.ai/bot, where Premium, Super and Ultra are still $30, $100 and $200. New guide: Grok Bot in meetings. What's new has a 1.0.1 section, and the Team Bots guide has Microsoft Teams setup steps and the messages the docs list for a stalled setup. docs.x.ai changed 11 pages and added four (meetings, Microsoft Teams, initiative, and Team Bots at a new address). Checking our guides against them corrected several statements: a Team Bot's team memory changes now wait under Review learnings, shared connectors are an exception to each person using their own account, the docs' recovery order puts Update Bot's Computer before Recover computer, a custom MCP connector can be added from a form in Connect apps or run as a command, Android's share sheet takes photos, videos, audio and PDFs, the phone app has 38 languages and account switching, and the docs now agree that Pages is not yet on Enterprise teams. Forum: an iPhone sign-in thread with staff steps was added to the sign-in guide. status.x.ai lists no new Grok Bot incident since November 6. None of this was tested by us.

Explore the update ↗

The official docs say Team Bots again and widen who a Team Bot answers in Slack; every Bot stuck on All screens on the shared computer are in use

docs.x.ai and Cursor's help, which renamed Team Bots to Shared Bots in late October, both say Team Bots again. They now say a Bot shared with your organization answers any full member of the Slack workspace, even without a linked Cursor account, and that those replies use the team's usage. Separately, forum users report every Bot failing with All screens on the shared computer are in use; Cursor staff call it a known issue and say not to Reset.

Build workflowsFix problems

Read November 11: Cursor's Team Bots help and docs.x.ai's Team Bots page. The Team Bots guide now covers the name change, the draft and Publish step, Slack access by sharing level, the Slack Workspace Access and Allow Shared Logins admin settings (on and off by default respectively), Review learnings, and that a team admin can delete a Team Bot from Manage Bots; the pages no longer mention unpublishing. Other guides still say Shared Bot in places. Forum: the stuck-screens thread opened November 3 had 12 replies; staff said on November 3 and 5 that Update Bot's Computer and Reset do not clear it and suggested running urgent browser work from a new Bot, which some posters said also failed. The changelog's newest entry is still 0.79.3, there is no new x.ai news post, x.ai/bot pricing and FAQ are unchanged, and status.x.ai lists no new Grok Bot incident since November 6.

Explore the update ↗

Four November releases reach the changelog: gift and flight requests, refund requests, a saved card that waits for Pay, and staff replies on the refusals

The Grok Bot changelog now lists 0.78.4, 0.78.5, 0.79.2 and 0.79.3 (November 3 to 6). Bots ask set questions before buying a gift, follow five US airline sites' booking steps, can ask for a refund on a subscription charge, and tell you when a web page hides instructions for AI agents; a saved card waits for your tap on Pay. Cursor staff also said on November 9 that Bots have been refusing more work than they should and that fixes are in progress.

Start hereOperate safelyBuild workflowsFix problems

Changelog, read in a browser November 10: the four entries were not listed on November 9. What's new has a new section covering all four by topic, and the facts are folded into the safety, plugins, Shared Bots, Gmail, Pages, platforms, weekly usage limit, routines and not-responding guides (for example: a one-off routine now turns off after it runs, the usage chart matches the meter, admins can set a Bot Computer Retention Period, the Bot's computer can run ssh and psql). The entries do not mention the cloud-agent coding default, the browser's loopback block or the access-restriction refusals. Forum, read November 10: staff (Colin) replied on November 9 in three threads we already cite. Bots refusing local work are a known over-refusal the team is changing; refusals where a connector exists are a known issue being worked on; and there is no workaround yet for previewing a local site in the Bot's browser. New to the guides: an iPhone app 1.24.1 crash when typing (staff: tracked, reinstalling will not help) and a staff route to a webhook routine's URL and key (right-click the routine, choose Webhook). No new x.ai news post; x.ai/bot pricing and FAQ unchanged; no new Grok Bot status incident since November 6. Thirteen docs.x.ai Grok Bot pages changed since November 9, but we keep no earlier copies to compare, so only the Vault and data retention passages we reread are cited. Release notes and forum reports are described, not tested.

Explore the update ↗

Prices are unchanged, but the plan guide corrects a stale note about which docs.x.ai pages mention The X Subscription

This week's pricing freshness check found no price or plan changes: cursor.com/pricing still shows Premium $30, Super $100 and Ultra $200 with Grok Bot excluded from Free and Plus, and cursor.com/help/grok-bot/plans is unchanged. It did catch a stale claim: docs.x.ai's FAQ, get-started and mobile pages already name The X Subscription's Premium, Super and Ultra tiers, not only legacy Cursor plans as the plan guide previously said.

Start here

Fetched cursor.com/pricing, cursor.com/docs/grok-bot, cursor.com/help/grok-bot/plans and docs.x.ai/grok-bot (faq, get-started, mobile, overview) with a browser user agent; x.ai/bot, x.ai/pricing and x.ai/news again returned a Cloudflare block, as on every prior check. Cursor's pricing, included-plan and usage-pool wording (4x/15x/50x Plus) are unchanged, and cursor.com/docs/grok-bot still lists only legacy Cursor plans, SuperGrok links and Grok Business seats with no mention of The X Subscription. But docs.x.ai's FAQ, get-started and mobile pages, which the plan guide described as still legacy-only, in fact already describe The X Subscription's Premium, Super and Ultra tiers by name alongside the legacy ones; get-started's own dateModified is now November 6 and the overview page's November 7 (the overview page doesn't cover plans either way). Corrected the plan guide's "where the official pages disagree" section to name only cursor.com/docs/grok-bot as legacy-only, and updated its checked dates. The what-is-Grok-Bot guide's checked dates were also refreshed; no fact there changed. Grok Bot vs OpenClaw, Grok Bot alternatives and the weekly usage limit guide were checked against the same Cursor/x.ai sources and found unchanged, so they were left untouched. No Grok Bot announcement from x.ai/news could be checked (Cloudflare-blocked, as usual).

Explore the update ↗

The Bot's browser can no longer open services on its own computer, and Bots refuse some browser tasks citing an access restriction

Since November 6 the Bot's browser cannot reach anything running at 127.0.0.1 on the Bot's own computer; Cursor staff said this is an intentional security change and the shell is not affected. Separately, users report Bots refusing browser work on sites such as Slack, Meta Ads and Xero with an access restriction message, often where a connector exists; staff had not replied by November 9.

Fix problems

Forum: the loopback thread passed 700 views by November 9; staff (Colin) said on November 7 that bot computers pick up the block when rebuilt on the current image, and no supported way to preview a local site in the browser had been posted. The access restriction thread passed 590 views with no staff reply; the nearest official note is 0.78.1's connector offers on several sign-in pages. The public changelog's newest entry is still 0.78.1, there is no new x.ai news post, x.ai/bot pricing and FAQ are unchanged, and status.x.ai lists no new Grok Bot incident since November 6.

Explore the update ↗

Bots refuse folders outside your user profile and route code edits to Cursor cloud agents; Bot failed to respond returns for some

From November 5 to 7 forum users reported Bots refusing local coding work and starting Cursor cloud agents instead; Cursor staff said that is the current default and that you must ask for local work explicitly in each message. File tools on your own computer still only reach your user folder, now with reports that Bots also refuse the Shell workaround, and some accounts hit Bot failed to respond on November 8.

Fix problems

Forum: the cloud agent thread reached 46 replies and 743 views by November 8, with many posters saying even an explicit request was refused. The local-exec root threads (Read, CopyToBox and CopyFromBox limited to the user folder, Shell not) gained new reports on 0.79.3 from November 7 with no new staff reply. A September Bot failed to respond thread picked up four new reports on November 8; the staff recovery step there is to stop resetting and open a thread with your Conversation IDs. Users cite app versions 0.79.2 and 0.79.3, but the public changelog's newest entry is still 0.78.1; there is no new x.ai news post, x.ai/bot pricing is unchanged, and status.x.ai lists no new Grok Bot incident since November 6.

Explore the update ↗

ERR_TUNNEL_CONNECTION_FAILED in the Bot's browser has a fix, and two Grok Bot incidents on November 6

From November 5 many Bots could not load any website, failing with ERR_TUNNEL_CONNECTION_FAILED whenever Route traffic through this computer was off. A Cursor staff member posted a fix the same day: Settings → Computer → Update Bot's Computer, no Reset needed. Status.x.ai also logged two short Grok Bot incidents on November 6.

Fix problems

Forum: the ERR_TUNNEL_CONNECTION_FAILED thread passed 1,300 views by November 7; staff first suggested keeping Route traffic through this computer on, then said a fix was out and that updating the Bot's computer by hand picks it up, with a few users still reporting the error on November 6. Status: computer use in Grok Bot failed in some regions from 11:49 to 12:03 UTC on November 6, and Grok Bot was degraded from 13:57 to 15:15 UTC, both marked minor. No new Grok Bot changelog entry (still 0.78.1) or x.ai news post, and x.ai/bot pricing is unchanged.

Explore the update ↗

The daily directory sweep runs clean for a week straight, but still adds no new rows; ten more Bots get editorial notes

This week's health audit found the automated catalog sweep completing successfully on all five runs from November 2 through 6, reversing the GitHub Actions budget-gate failure streak reported since mid-October, yet no row anywhere in the catalog carries a firstSeen date past October 20. Ten more Bot pages across all eight categories picked up hand-written "Our take" notes, one listing retired, and the not-responding guide reordered its recovery steps to match an official docs change.

DirectoryFix problems

The November 6 weekly health audit confirmed bots-daily.yml has succeeded on all of its last five runs (November 2 through 6), after the Actions-budget gate that caused 22-plus consecutive failures through late October. That fix is about the workflow running, not the catalog growing: every row in src/data/bots.json still has a firstSeen date of October 20 or earlier, so this week's sweeps re-verified existing rows (refreshed checked dates, retired dead links) rather than adding anything new, because the upstream catalogs it merges from haven't produced a new entry in over two weeks. One row retired this week, Lobster Agents on November 6, bringing the catalog to 4,404 live and 28 retired. Ten more Bot pages, spread across all eight categories, picked up hand-written "Our take" sections on November 1. The not-responding guide also picked up an official reordering of its recovery steps (Update now comes before Recover, matching a docs.x.ai change) plus a new forum case on November 3; daily reports of usage-meter jumps and status.x.ai incidents continued through the week with no change beyond what's already in the daily log.

Explore the update ↗

More usage meter jumps, a reported limit reset tied to data use, and a Grok Bot incident on November 5

More users reported weekly meters jumping to 100% on November 4 and 5, and one user said the app offered to reset their limit only if they allowed their interactions to be used to improve products and models. We found no official mention of that offer. Status.x.ai also logged a Grok Bot incident on November 5, and SpaceXSI's Data Bot case study is added.

Fix problemsBuild workflowsStart here

Status: a Degraded Performance incident listing only Grok Bot ran from 00:34 to 01:49 UTC on November 5, marked minor. Forum: the usage meter thread now has more than 200 posts, with still no staff reply; one user said their meter went back on its own. Official: SpaceXSI's November 2 post describes Data Bot, a Team Bot its data science team maintains, with managers approving additions to shared memory; the 70 hours a week figure is SpaceXSI's estimate. The changelog's newest entry is still 0.78.1, and x.ai/bot's pricing and FAQ match our guides.

Explore the update ↗

OpenMausBot gains an MCP server, a headless CLI and native phone apps; its star count jumps +5,436 in a week

The weekly ecosystem watch rechecked Rakazo's and MausBot's READMEs. Rakazo is unchanged. MausBot's README documents three new things: a stdio MCP server for Claude Desktop and Cursor, a headless `openmausbot run` command for scripts and CI, and native Android/iOS phone apps. GitHub star counts for 12 watched repos were refreshed; milind-soni/OpenMausBot jumped from 6,980 to 12,416 stars in one week, the largest single-period delta either it or Rakazo has had in this log. No new comparison guide was drafted this run.

Comparisons

The Grok Bot alternatives guide's MausBot paragraph adds one sentence on the new stdio MCP server (lets Claude Desktop or Cursor inspect bots/channels, create and run work, and wait for completion, without exposing approvals, credentials or computer lifecycle), the headless `openmausbot run` command (JSON output, exit codes, for scripts and CI), and native Android and iOS phone apps that pair over an approved public endpoint, Tailscale or a reverse proxy, or install as a browser phone app. Rakazo's README, Features, Stack and sandbox-provider list are unchanged from October 29. mausbot.com/pricing was rechecked directly: all individual and team tiers are unchanged, and the page's own Claude-credit-on-team-plans figures still disagree with each other, so that item stays unconfirmed. OpenClaw's getting-started and install/node pages were also rechecked with no material change, and the grok-bot-vs-openclaw guide was left untouched since nothing changed. 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 category taxonomy expanding to roughly 80 named categories.

Explore the update ↗

A support reply says the usage meter issue is fixed, but new overnight jumps are reported November 4

A user shared a SpaceXSI support reply saying their weekly Grok Bot limit should be back to where it was before the November 1 issue, and that usage limits are adjusted from time to time. On the morning of November 4 at least three more users reported meters jumping to 100% overnight, with still no staff reply in the forum thread. The November 2 source control incident is closed, and two guides pick up documentation and forum changes.

Fix problemsBuild workflowsDirectory

Forum: in the usage meter thread (now about 200 posts), one user posted a November 3 support reply signed by SpaceXSI's SI Support Agent; other users said only a one-time credit was applied, and new jumps (7% to 100%, 25% to 100%) came in on November 4 from Cursor Ultra and Ultra Legacy users. The sign-in guide adds a staff-answered thread on Bots hidden after a free Grok Bot Galaxy credit ran out: staff said the Bots were not deleted, and the fix is to restore access and then fully quit and reopen the app, without Recover or Reset. Status: the November 2 source control incident listing Grok Bot was resolved at 10:24 UTC after about 1.25 hours; a November 3 incident on slow GitHub clones listed BugBot and Cloud Agents but not Grok Bot. Docs: docs.x.ai's Manage Grok Bot computers page, updated November 3, describes running computer operations through the Organization API with an admin:* key, sharing a one-operation-per-team limit with the dashboard, and does not mention typing DELETE to confirm; the Shared Bots guide's admin table now matches. Cursor's Grok Bot docs switched to the Android, connected apps and shared Bots wording our guides already use, and Cursor's team pricing docs changed which third-party models skip the Cursor Token Rate, which no guide covers. The Grok Bot changelog is still at 0.78.1; x.ai/news and x.ai/bot could not be opened today, so they were not rechecked. Directory: 50 Bots added for 4,255 live and 27 retired. Nothing was tested by us.

Explore the update ↗

Official troubleshooting reorders Update before Recover; a month of /workspace work waited on staff for weeks

The not-responding guide now matches a change to Cursor's troubleshooting page: Update Bot's Computer now comes before Recover computer in the official recovery order, not after, and the page adds cautions against a second Update or Reset. The guide also adds a forum case where an unreachable computer and an account-merge variant both stayed broken for weeks, with staff asking users to touch nothing.

Fix problems

Docs: docs.x.ai/grok-bot/troubleshooting's own dateModified moved from October 22 to October 28; the 'computer cannot be reached' order changed from Retry, restart, Recover, Update, Reset to Retry, restart, Update (if offered), Recover, Reset, and it now warns not to start a second Update or Reset while one runs, and to use Retry Recovery or Retry Reset once before contacting support. Forum: a thread opened October 14 (301 views) describes a computer unreachable 11-plus hours after Update and Reset both failed, with a month of code in /workspace; Cursor staff (mohitjain) said the computer was not wiped but the latest saved copy predated the outage, and asked the poster to stop clicking Update, Reset or delete anything. By October 17 the account was moved to an empty replacement computer while the original /workspace was tracked down; the thread was still open October 29. A second poster in the same thread hit the same advice after combining accounts into The X Subscription left their Bots on the new account while the computer and files were still being carried over. Checked with no qualifying new reports: reddit.com/r/GrokBot (blocked the request, so skipped), the Cursor forum's other October 27 to November 3 threads under grok-bot (none reached 10 replies or 300 views within the window except threads already cited), status.cursor.com (blocked) and status.x.ai/history (blocked). Nothing here was tested by us.

Explore the update ↗

November 1 usage meter jumps fall back for many users, and a new source control incident lists Grok Bot

The November 1 billing and usage dashboard incident was marked resolved at 10:53 UTC after about 5.25 hours. Many Grok Bot weekly meters stayed high overnight, then several forum users reported on November 2 that their readings had dropped back to where they were before the jump. Status.x.ai also opened a new incident on source control integrations listing Grok Bot.

Fix problemsBuild workflowsDirectory

Forum: the usage meter thread passed a hundred posts, with many users stuck at 100% and some asking support for refunds; between 08:00 and 08:47 UTC on November 2 several users wrote that their meters were back to pre-jump readings without a reset, while a few said tasks still seem to use about twice as much. No Cursor or SpaceXSI staff reply and no official word on usage rates yet. Status: the billing and usage dashboard incident (cursor.com and Enterprise Dashboard, not Grok Bot) closed without saying whether usage was corrected; from 09:09 UTC on November 2 a minor incident on source control provider integrations lists the IDE and Grok Bot, and the live panel shows it. Plugins and MCP: the Interactive Brokers MCP sign-in failure, open since August per Cursor staff, is now in the troubleshooting table, with a November 1 user report that adding the address by hand works. The Grok Bot changelog, x.ai/news and x.ai/bot could not be read today, so they were not rechecked. Directory: 50 Bots added for 4,105 live and 27 retired. Nothing was tested by us.

Explore the update ↗

Grok Bot weekly usage meters jump on November 1 during a billing dashboard incident

No new Grok Bot release, news post or pricing change today. Early on November 1 many forum users reported their Grok Bot weekly usage jumping, often roughly doubling, with no new activity, while status.x.ai opened an incident on the billing and usage dashboard. Both are now in the weekly usage and status guides.

Fix problemsDirectory

Forum: a thread started at 04:25 UTC (27 replies by morning) collects reports of weekly meters flipping between readings or jumping, for example 44% to 88%, across Ultra, Super and legacy Pro+ accounts; some users saw the Bot and Settings disagree, and one said the Bot later stopped at the limit. No Cursor staff reply yet. Status: from 05:38 UTC status.x.ai lists a minor degradation affecting the billing and usage dashboard, naming cursor.com and the Enterprise Dashboard rather than Grok Bot; it was still being investigated at 08:44 UTC, and the live panel shows it. The incident does not say whether usage will be corrected. Checked with no change: the Grok Bot changelog (still 0.78.1), x.ai/news and the x.ai/bot pricing and FAQ. Directory: 50 Bots added for 4,005 live and 27 retired. Nothing was tested by us.

Explore the update ↗

A short multi-service degradation on October 31, and user tips for stretching weekly usage

No new Grok Bot release, news post or pricing change today. Status.x.ai logged one more incident listing Grok Bot: multiple services were degraded from 06:04 to 06:47 UTC on October 31, marked minor. The weekly usage guide now cites a busy forum thread of user tips for making the allowance last, alongside Cursor's official advice.

Fix problemsDirectory

Status: the October 31 incident listed Grok Bot, Cloud Agents, Automations and cursor.com and was closed as resolved after about 45 minutes without a stated cause; it is now in the outage table. Forum: a thread on using Grok Bot more token-efficiently collects user tips (new chats per task, batching requests in one file, fewer Bots) and a feedback request for chat branches; no staff reply yet. Checked with no change: the Grok Bot changelog (still 0.78.1), x.ai/news and the x.ai/bot pricing and FAQ.

Explore the update ↗

Three Grok Bot releases built toward Shared Bots and Vault payments; the directory logs zero new rows by firstSeen date

Three changelog entries this week (0.75.8, 0.77.0 and 0.78.1) finished the Team Bots-to-Shared Bots rename, added a Permissions screen and Vault payments, then closed with shopping cards and order tracking. The directory's own daily sweep stayed broken for a fourth straight week, so no catalog row carries a firstSeen date inside this calendar week, even as three Fix problems guides picked up real staff-sourced fixes.

Start hereOperate safelyBuild workflowsFix problemsDirectory

Grok Bot's October 24, 26 and 27 changelog entries (covering versions 0.75.6 through 0.78.1) moved Team Bots to Shared Bots with their own Vault logins, added a Permissions screen listing every Auto-review rule, put a Payments tab and default payment method in Vault, and finished with shopping cards, Buy now ordering, shipment tracking and three trial/subscription-cancelling templates. A new Grok Bot Pages guide also landed this week, covering the reports, memos and dashboards a Bot can keep up to date for you. Three Fix problems guides picked up staff-sourced fixes: a shell-startup-file cause and recovery step for computers where every Shell command hangs, a staff clarification that Grok Bot draws from the same shared weekly pool as Cursor and Grok on the new X Subscription tiers, and a backup procedure for exporting a Bot's memory before Cursor ships a one-click export. status.x.ai's takeover of Cursor's status page is now complete, so every status link across the guides points there. The directory added no row with a firstSeen date inside this calendar week — this week's health audit found the automated daily sweep has not completed successfully since October 8, so growth keeps coming from the owner's manual catch-up sweeps, whose rows still carry older firstSeen dates from the upstream catalogs; the week's 16 retirements (15 from the October 25 catch-up sweep, one more on October 30, for 27 total) were already reported as they happened.

Explore the update ↗

The docs say Bots can use your phone's apps, and a frozen computer turns out to have two causes

No new Grok Bot release or news post today, but the official docs changed. The mobile page now describes Bots using Calendar, Contacts, location, alarms and timers on your phone, plus Reminders and Apple Home on iPhone, which no changelog entry has announced yet. The 1Password page gives the new integration's requirements, and the team computers page adds a Restart VMs flow. In the forum, staff traced the late-October frozen computers to a stalling shell startup line or, on some accounts, two computers started at once. Silent Bots at the usage limit now show a message after an update, and status.x.ai logged two short Grok Bot incidents on October 29.

Start hereOperate safelyBuild workflowsFix problemsDirectory

Docs: docs.x.ai's mobile page describes a Bot using your phone's apps in your own chat with a Bot you own while Grok Bot is open on the phone. On iPhone and Android that covers Calendar (not repeating events, never inviting anyone), Contacts (read-only), current location and one-off alarms or timers; on iPhone it adds Reminders and Apple Home, including locks, garage doors and security systems. Each app needs your phone's permission, a team's local-execution limit applies, and Settings → Bot → Manage your devices lists your devices. The same page says routines can be added on a phone, and Edit routine opens a draft request to the Bot. This is in the platforms and safety guides. The computer-and-apps page says the new 1Password integration needs 1Password 8.12.42 or later on a personal or Family account and must be reconnected if you used the old one; that is in the safety guide. The Manage Grok Bot computers page adds Restart VMs after a team setting change and details Terminate Inactive Computers (off by default, 30 days without a message, never while awake); that is in the Shared Bots guide. Forum: two frozen-computer threads (204 and 213 views) join the not-responding guide. In the first, staff asked users not to Reset, to copy .profile and .bashrc to a Mac with the Bot's file copy action and look for a line that starts a program, and traced that case to a watchdog line whose trailing & kept terminal startup from finishing. In the second, staff said some accounts had two computers started and ran a manual cleanup on October 27; both posters were working again by October 29. A September thread (357 views) got a staff update on October 30: Bots that went silent at the usage limit now show a limit message once the app is updated. Status: degraded Cloud Agents and Origin performance listing Grok Bot (October 29, 09:01 to 09:18 UTC) and an Auto Review degradation (October 29, 23:44 to October 30, 01:20 UTC) are in the down guide, and the live panel listed both. Changelog: still 0.78.1. News: no post newer than October 27. Pricing: x.ai/bot unchanged. Directory: 50 Bots added for 3,855 live and 27 retired. Nothing was tested by us.

Explore the update ↗

Grok Bot 0.78.1: shopping cards, subscription templates and a Team Bot you can keep to yourself

The October 27 changelog entry (0.78.0 and 0.78.1) shows products as cards, starts orders you approve and tracks them, connects Shop Pay from Vault's Payments tab, and adds templates that cancel free trials before they bill, cancel unused subscriptions and watch renewal prices. A Team Bot can now be limited to Only you and get its own Vault logins, the in-app free-trial offer became Get Grok Bot with a unified plan, and a long fix list covers routines, Gmail, connectors and the Bot's computer. Cursor's help now describes the Shared Bots flow and a Vault CSV import, status.x.ai logged a two-hour multi-service incident on October 28, and a forum thread on file copies dropping your own computer joins the not-responding guide.

Start hereOperate safelyBuild workflowsFix problemsPricing guideDirectory

0.78.1 (October 27, also covering 0.78.0): shopping shows products as cards with photos, rating, price, store and badges, three or four results scroll in a carousel, Buy now starts an order you approve, and the Bot tracks shipments with carrier and stage; Shop Pay connects in the Vault's Payments tab and can be the method Bots use first; the Try it, don't pay for it, Find unused subscriptions and Watch subscription prices templates act on trials and subscriptions, with Bots confirming before changing anything; a Team Bot can be limited to Only you, managers can add logins to a Team Bot's own Vault under Configure → Tools, a Team Bot routine asks for your connector in its Slack thread, and the admin page says Shared Bots; where Grok Bot offered a free trial it now offers Get Grok Bot with a unified plan; connector names replace internal IDs, connect cards ask Still signing in? after 10 minutes, Google accounts already connected are reused, Remove from Slack disconnects Slack; Gmail plain-text drafts open in rich text, attachments from the Bot's computer work in more cases, Bot emails retry once; the computer card stays on Asleep during background wakes, Update installs the version you clicked, Route traffic through this computer says when the Bot's computer is asleep, Reset and Recover keep the current disk, routines made in a new Bot's first chat run in your time zone instead of UTC, clicking a webhook routine shows its URL, buying a plan during desktop sign-in finishes the sign-in, the usage banner closes once you are under your limit, and the Intel Mac build offers the Apple silicon version. The what's-new, what-is, platforms, glossary, plan, plugins, Team Bots, Gmail, Pages, safety, down, not-responding, usage, shared-computer, routines and Windows sign-in guides reflect these. Help: Cursor's Shared Bots page now describes + → Create a Bot, Share → Who has access with Collaborator and Manager roles, Browse shared Bots, and a 1.19.0 phone requirement; its secrets page describes a desktop CSV import of logins and an iPhone 1.18.0 Vault Save bug fixed in 1.19.0; its secrets help still says Vault is not supported on shared Bots, which the changelog's Team Bot Vault contradicts, and the guides say so. Status: a multi-service incident on October 28 (21:15 to 23:13 UTC, Grok Bot listed, marked major) is in the down guide; the live panel listed it. Forum: the August thread on your own computer showing connected while file copies drop it (697 views, staff workaround: split copies, wait a minute, quit and kill local-exec-daemon; still reported on 0.78.1 on October 29) joins the not-responding guide. News and pricing: no Grok Bot post newer than October 27, x.ai/bot unchanged. Directory: 50 Bots added for 3,806 live and 26 retired. Nothing was tested by us.

Explore the update ↗

Grok Bot 0.77.0: a Permissions screen, Vault payments, and Team Bots become Shared Bots

The October 26 changelog entry (0.76.0 and 0.77.0) adds a Permissions section that lists every Auto-review rule, a Payments tab in Vault with a default payment method, 1Password without a shared vault, cards that ask several questions at once, Import Memory from another assistant, and 30-minute approval cards. The official docs renamed Team Bots to Shared Bots and added Vault and referral-program pages, SpaceXSI published a sales-team case study, and status.x.ai logged its first Grok Bot incident.

Start hereOperate safelyBuild workflowsFix problemsPricing guideDirectory

0.77.0 (October 26, also covering 0.76.0): Settings gains a Permissions section with Auto-review rules under Always Ask and Allow without Asking; Auto-review lets through more undoable private actions and background work you start in your own words no longer asks to start; approval cards stay open 30 minutes in the app and Slack; Bots ask several questions on one card; Vault gets a Payments tab, Payment accounts, a Default payment method and a Hints field, Bots try Vault before a password manager, and Link one-time cards are US and Canada only; 1Password connects without a shared vault and is detected on Windows and Linux; Import Memory brings preferences from another AI assistant into your primary Bot; connector buttons say Connect, Not connected and Reconnect, sign-ins can finish within an hour, custom MCP servers can use a private certificate authority, and Google throttling no longer disconnects Google apps; Gmail sign-outs are announced by your primary Bot, a second Gmail or Drive account uses Google's picker, replies fold into threads, Gmail rules hold under other tool names, and email drafts have Discard again; every one-to-one email from a Bot's address carries an unsubscribe link; Page owners can delete a Page from the Library for everyone; Order Concierge and Deal Watcher templates; team admins can limit Bot sharing to admins and choose template publishing scope; the Bot's computer stays up on low memory, commands waiting for input finish, the browser keeps site logins after its last window closes and keyring keys survive recreation; Português (Portugal) and Europe/Kyiv. The what's-new, what-is, safety, permission boundaries, glossary, Team Bots, plugins, Gmail, Pages, Marketplace, platforms, not-responding, shared-computer, routines and usage guides reflect these. Docs: docs.x.ai replaced its Team Bots page with a Shared Bots page and every docs page now says shared Bot, Cursor's Team Bots and connect plugins help addresses redirect to Shared Bots and Connect apps, so our citations moved; docs.x.ai added a Vault and secure sign-in page and SpaceXSI's X Subscription docs added a referral program (two-week Premium trial for the friend, a usage reset for a US-based Premium, Super or Ultra referrer), now in the plan guide. News: SpaceXSI's October 27 post describes its sales team's Account Intel, Quote and Deal Shared Bots; added to the Team Bots and what's-new guides as a vendor account. Status: the first Grok Bot incident on status.x.ai, delayed responses from 20:33 to 20:43 UTC on October 27, is in the down guide. Forum: the Bot email rename thread (330 views, support confirmed no rename, plus-addressing failed in a user test) joins the Gmail guide, and the Chrome extension thread (759 views, staff on Route traffic through this computer for sites that block the cloud browser) joins the shared-computer guide. Pricing: x.ai/bot unchanged. Directory: 50 Bots added for 3,756 live and 26 retired. Nothing was tested by us.

Explore the update ↗

Fix problems: a usage-pool mixup gets a staff answer, plus a memory-export workaround

The Cursor forum's grok-bot tag was rechecked against the 10-reply/300-view bar for threads active in the last week. Two qualified: a thread where staff first fixed a cosmetic usage-breakdown bug, then clarified that Grok Bot has no separate weekly allowance at all on the new Ultra, and a thread where staff gave a backup procedure for exporting a Bot's memory before Cursor ships a one-click export. Both now appear in the guides they fit; the official troubleshooting page, the CellCog tracker and status.x.ai's incident feed showed no changes since our last check, and r/GrokBot could not be reached (HTTP 403).

Fix problems

Weekly usage guide: a September Teams-plan thread (reply_count 3, 308 views as of today) reported grok-bot-default and grok-bot-cua rows wrongly appearing inside the Cursor Models and Other Models breakdown on the Spending page, making it look like Grok Bot was eating the Cursor quota even though the headline percentages stayed Cursor-only; Cursor staff (mohitjain, Colin) called it a display bug and confirmed it shipped fixed by September 11. Asked on October 20 whether the same separate-pool behavior carries over to the new Ultra, a Cursor staff member said no: on The X Subscription (Premium, Super and Ultra) there is no separate Grok Bot allowance, Grok Bot draws from the same shared weekly pool as Cursor and Grok usage, and only third-party models bill from prepaid top-up credit; the separate-allowance behavior described elsewhere in the guide is specific to the legacy Cursor plans. The 'How the meter actually works' section now cites this directly. Shared-computer guide: a September thread (673 views) asking the best way to export or back up a Bot's memory got a staff reply (mohitjain) describing a zip-and-send backup procedure, since there is still no one-click export, plus a caution (izgorodin, staff agreed) against folding raw memory straight into skill files. The 'Long threads, and how to start fresh' section and its checklist now cover it. Both guides' evidenceLabel and updatedAt were refreshed to today. No other thread on the tag page's first six pages (active since October 20) cleared the reply/view bar without already being linked from an existing guide; threads below the bar on computer-frozen and shell-hang symptoms were noted but not added, since none individually reached 10 replies or 300 views. The official troubleshooting page (last updated October 22), the CellCog problems tracker (last changed around late August/early September) and status.x.ai's incident feed (no new Grok Bot incident since October 23-24) were rechecked with no material change. docs.x.ai/grok-bot/troubleshooting and cellcog.ai/blog/grok-bot-problems were fetched directly; r/GrokBot's top-this-week JSON returned HTTP 403 and was skipped, as were status.x.ai/history's HTML page (403) in favor of its compat JSON API, which did load.

Explore the update ↗

Grok Bot 0.75.8: Auto-review rule cards, and the status page moves to status.x.ai

The October 24 changelog entry (0.75.6 to 0.75.8) lets a Bot propose a change to your Auto-review rules on a card you confirm, shows fewer approval cards for safe actions, lets Bots use a connector's new tools without a reconnect, and limits a Team Bot to the people on its share list. Cursor's status page has finished moving to status.x.ai, so the live status panel and every incident link now read from there.

Start hereOperate safelyBuild workflowsFix problemsPricing guideDirectory

0.75.8 (October 24, also covering 0.75.6 and 0.75.7): in the app a Bot can offer to add, change or remove one of your Auto-review rules on a card you confirm; Auto-review takes a second look before showing a card, so fewer safe actions need one, and a Bot editing its own routines is not risky by itself; approval cards in Slack describe the action; a Bot's status line appears right after you send; finished background work completes what you asked and stops instead of acting on its own; scheduling uses the Google or Outlook calendar you connected; a plugin a Bot installs mid-task is usable right away; connectors pick up new tools without a reconnect and show Authenticate instead of Connected when a sign-in expired; images from connectors arrive as images; routine posts to Slack no longer ping your phone; a safety-check block in Slack is explained; with Route traffic through this computer on, the connection returns when the Bot's computer wakes; people not on a Team Bot's share list, including teammates, lose access until an owner shares it, a Team Bot's routines can read Slack channels you both are in, and its edited Slack messages show an (edited) label. The what's-new, safety, permission boundaries, Team Bots, plugins, Gmail and Workspace, not-responding, glossary and what-is guides reflect these. Status: every status.cursor.com address, including old incident links, now redirects to status.x.ai, which lists Grok Bot and cursor.com as components and carries Cursor's incident history; the live panel now reads status.x.ai's JSON API and merges feed items by id, and the down guide's links and wording follow. No new Grok Bot incident since October 24. Usage: a Cursor staff reply from October 14 explains that the usage page's Tokens column counts everything a Bot re-reads per call, mostly cached context, and that hovering splits it; added to the weekly usage guide. Pricing: x.ai/bot is unchanged; Cursor's team pricing docs now put Super and Ultra team seats at 3.75x and 12.5x Premium usage and describe a $0 Free seat. Directory: 50 Bots added for 3,706 live and 26 retired. SpaceXSI's news page has no new Grok Bot post. Nothing was tested by us.

Explore the update ↗

Not-responding guide: when every Shell command hangs, check the startup files

A new forum thread with a Cursor staff reply explains a computer where every Shell command times out after 840 seconds while connectors still work. Staff traced it to the computer's shell startup files and gave a file-reading check to run instead of another Reset.

Fix problems

The Grok Bot not responding guide's table row for hanging Shell commands now adds the October 21 staff explanation: every Shell command starts a login shell, so a startup-file line that waits on something stalls them all, and a Reset restores the same files. A new section gives the staff recovery step (have a Bot read .bashrc, .profile and .bash_profile with its file reading tool, not Shell) and notes that the reporter's computer recovered on October 25 without a confirmed cause, while another user still reported the symptom on October 26. Cursor's status history had no new Grok Bot incidents, and status.x.ai has no Grok Bot items yet. The x.ai changelog, news and pricing pages were not rechecked today.

Explore the update ↗

Grok Bot 0.71.2 to 0.75.5: Pages, Vault, video creation, and a new Pages guide

Every guide was rechecked against today's sources. Three releases since our last pass (0.71.2 on October 14, 0.75.2 on October 22 and 0.75.5 on October 23) are now covered across the site, a new guide explains Grok Bot Pages, x.ai/bot now shows The X Subscription prices, and the directory caught up after an 11-day sweep outage with 185 more live Bots. From today the site is refreshed daily.

Start hereBuild workflowsOperate safelyFix problemsComparisonsPricing guideDirectory

Releases: 0.75.5 adds a Vault in Settings where Bots save your logins, cards and contact info and fill them in (account-wide, not on Team Bots), email forwarding with attachments, and Auto-review changes. Sends you ask for in chat now go out once Auto-review allows them, routine sends still wait as drafts, and a denied action isn't retried until you write again. Routines can run up to 300 times an hour in total and 200 per routine. 0.75.2 adds Pages (reports, memos and dashboards you edit together or a Bot keeps up to date), video creation, a Pinned Library section, Shop Pay, redesigned chat cards, and many Gmail, Calendar, GitHub and Team Bot additions. 0.71.2 raises attachment limits to 250 MB files, 1 GB videos and 20 attachments per message, lets Bots use up to 200 plugin skills, and fixes many sleeping-computer, reconnect and connector-timeout symptoms. The what's-new guide, the new Grok Bot Pages guide, and the safety, permissions, Team Bots, plugins, Gmail, routines, glossary and platform guides all reflect these. The Fix problems guides now say which version fixed which symptom, add five October incidents and the Bots-missing-after-switching-plans reports, and correct a local-tools thread that did get a staff workaround. Status: Cursor says Grok Bot status notifications move from status.cursor.com to status.x.ai starting October 26. Pricing: x.ai/bot now lists Premium $30, Super $100 (3.5x Premium usage) and Ultra $200 (12x), while cursor.com/pricing and the X Subscription docs still express the same tiers as multiples of Plus; both are shown. Some docs.x.ai pages still list older plans and attachment limits. Comparisons: Claude, ChatGPT, MausBot and Manus rows were rechecked, and the workflow-brief and evaluation guides add SpaceXSI's October 20 IncidentWatch and IncidentSweep write-up as an attributed vendor example. The Secure Form password-in-snapshot report still has no confirmed fix. Directory: 200 new rows were added, 15 Bots retired after their share links stopped resolving, and 41 were renamed, for 3,656 live. Nothing was purchased or tested by us.

Explore the update ↗

Bot submissions move to a live API, ten more Our take notes, and the directory stays stale

Submitting a Bot now runs through a web form, a no-key agent API, and matching MCP tools that check the share page live and queue one record per submission, with every response naming the paid upgrade it qualifies for. Ten more Bots picked up hand-written Our take notes and a search-indexing cleanup kept bare link pages out of the sitemap, but the daily catalog sweep is still down, so there are no new directory rows or retirements to report this week.

SubmissionsEditorial correctionsSearchDirectory

Bot submissions (the web form, a no-key agent API at /api/bots/submit and /api/bots/status, and matching MCP tools) now check the share page live and queue one private record per submission, replacing the private GitHub-issue queue that depended on a token unset in production and used to fall back to an email draft. Every submission response names the fast-track or Featured paid upgrade it fits; starting a checkout requires accepting the current terms version, and a human pays on Stripe. Ten more Bots — including Dungeon Master, Melissa and Cyber Legend — picked up hand-written "Our take" notes this week, spread across all eight categories, and creator pages and tag collections without written guide prose are now noindex,follow and left out of the sitemap, so indexing stays on guides, categories, guided collections and Bot pages instead of bare link lists. The automated daily catalog sweep has not completed successfully since October 14 — this week's October 23 health audit confirmed the same GitHub Actions budget gate reported last week, still unresolved — so the live catalog is unchanged at 3,471 live and 11 retired entries, with no new rows or retirements this week.

Explore the update ↗

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.

Explore the update ↗

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.

Explore the update ↗

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.

Explore the update ↗

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.

Explore the update ↗

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 guideStart hereFix problemsComparisonsEditorial corrections

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.

Explore the update ↗

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.

Explore the update ↗

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.

Start herePricing guideFix problemsComparisonsEditorial corrections

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.

Explore the update ↗

341 new Bot listings this week, four retirements

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.

Explore the update ↗

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.

Explore the update ↗

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.

Pricing guideStart hereComparisonsFix problemsEditorial corrections

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.

Explore the update ↗

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.

Explore the update ↗

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.

Explore the update ↗

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.

Explore the update ↗

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.

Explore the update ↗

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.

Explore the update ↗

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.

Explore the update ↗

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.

Explore the update ↗

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.

Explore the update ↗

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.

Explore the update ↗

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.

Explore the update ↗

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.

Explore the update ↗

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.

Explore the update ↗

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.

Explore the update ↗

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.

Explore the update ↗

Three tasks, from first brief to review

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.

Explore the update ↗

Help make the next attempt better.

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.

Suggest a correction ↗