Skip to content

Repository files navigation

Awesome Grok Bot

EN · 中文 · 日本語 · Playbook prompts

Awesome Entry count Grok Bot status License

Grok App (GitHub) — open-source Grok Build desktop app · 铁柱AGI @cgnot996

Follow the WeChat official account, or add me as a friend.

WeChat official account 铁柱AGI     Add 铁柱AGI on WeChat

Official account (search 铁柱AGI) · Add friend

Grok Bot is the always-on AI teammate launched 2026-08-11 by xAI/SpaceXAI with Cursor. Each Bot shares one persistent cloud computer (browser, files, terminal) and keeps working after you close the laptop. It is not grok.com chat, Grok Imagine, or a Grok 4.x model writeup. Unofficial community list, not affiliated with xAI or Cursor.

Upcoming

Full meetup notes

Contents

Official Resources

  • @bot QoL: cleaner UI, Google Docs/Sheets/Slides, network routing, speed - Official @bot thread (2026-09-22 ~22:57 UTC / Sep 23 06:57 Asia/Shanghai): cleaner Bot UI; native Google Slides/Sheets/Docs plus better email file attach; route internet via your own network; faster replies (+6% usage) and desktop perf (53 fixes)—try x.ai/bot (no separate news page).
  • How SpaceXAI is using Grok Bot to scale customer support - Official case study (2026-09-22): SpaceXAI/Cursor rebuilt support around Grok Bot—ticket intake to resolution, Plain/Linear/Datadog, refunds, SLA/queue, X sentiment, and Bot-coaching-Bot—handling +175% tickets without new headcount at ~$0.20–$0.30/resolution.
  • Introducing Grok Bot - Launch note: always-on agents with their own computer, working inside your tools 24/7.
  • Grok Bot is now included with more plans - Official access expansion post (updated): Grok Bot is available for SuperGrok, Cursor Pro, and all Cursor Teams plans.
  • @bot: free trial and wider plan access - Official 2026-08-21: SuperGrok Plus, Cursor Pro+, and all Cursor Teams get Grok Bot, plus a limited free trial for everyone else.
  • @bot: mobile notifications grouped by Bot - Official 2026-08-18 QoL: mobile notifications group by Bot and use that Bot's icon.
  • @bot: Some ways people used Grok Bot this week - Official 2026-08-19 thread quoting 14 field jobs, from a Matic vacuum to Stripe refunds and a meeting stand-in.
  • Grok Bot overview - Canonical product page: one named Bot, one shared cloud computer, isolation is per user not per Bot.
  • Get started - Install desktop, sign in with Cursor, create the first Bot. No official Linux desktop.
  • Use cases - Official roster ideas: sales CRM nights, ops invoices, engineering bug squash.
  • Grok Bot for mobile (iOS + Android) - Official docs for Grok Bot on iPhone and Android (Android 9+ / iOS 18+), with App Store and Google Play install links.
  • Create and manage Bots - How a Bot is named and scoped, plus the public share link that copies identity, skills, and routines (not your computer or logins).
  • Message and collaborate - Bots message each other, join group chats, and assign ownership of work.
  • Files and results - Where artifacts live on the shared computer and how you pull results back.
  • Use the computer and apps - Browser, filesystem, terminal. No clean API? Click the site like a person.
  • Skills and routines - Teach a task (up to 10 minutes of screen, no mic), save as a reusable routine.
  • Settings and notifications - Notification grouping, mobile alerts, and how Bots follow up stalled work.
  • Approvals, security, and privacy - Bots do not see passwords; draw the approval line on irreversible actions and 2FA takeover.
  • Teams and enterprises - Team marketplace, SSO, shared analytics. Plugins follow existing Cursor policy.
  • Troubleshooting - Official fix list for reconnect, runners, and common beta failures.
  • FAQ - Short official answers on access, computer sharing, and what Bots can remember.
  • Link SuperGrok for Grok Bot - Cursor help: Grok Bot is now on SuperGrok Plus and Heavy; already on Ultra, linking Plus does not stack usage.
  • Grok Bot on mobile (Cursor help) - How the iOS companion talks to Bots that stay on the cloud computer.
  • Connect plugins - Prefer a plugin and fall back to the cloud browser when it is missing; Zoom desktop auth currently fails with error 4700 (invalid redirect) and has no workaround.
  • Store secrets securely - Use the secret card. Never paste API keys into the Bot chat.
  • Recover Grok Bot computer data - Official recovery guide: chat history lives outside the box; reopen restores synced files, Reset is last resort.
  • Grok Bot plans and billing - Official billing FAQ: paid Cursor plans and Teams include Grok Bot (Pro below Pro+ below Ultra); SuperGrok / Plus / Heavy can link, Lite and SuperGrok Team/Enterprise cannot; weekly usage resets; legacy request-based pricing is excluded unless you opt into usage-based.
  • Grok Bot on the App Store - Official iOS listing for the companion app.
  • xAI plugin marketplace - Official .grok-plugin marketplace Grok Bot inherits under Cursor plugin policy.
  • @bot: SuperGrok and Cursor Pro get Grok Bot; weekly usage reset - Official 2026-08-26: all SuperGrok and Cursor Pro subscribers get Grok Bot, and weekly usage limits were reset for everyone.
  • @bot: share Bot templates - Official 2026-08-28: you can now share templates of your Bots with others.
  • @bot: Grok Bot can buy things - Official 2026-08-28: connect Stripe Link and Grok Bot can complete purchases on your behalf.
  • Grok Bot on Google Play - Official Google Play listing: Grok Bot for Android is available — same Bots and threads as desktop/iOS; work continues on the cloud computer after you lock the phone (eligible Cursor/SuperGrok plan).
  • Sign in to Grok Bot - Official help: Grok Bot uses your Cursor account (no separate login); persistent auth loops or phone-verification blocks often need support after the listed retries.
  • Grok Bot now works with X - Official 2026-08-29: connect X in Grok Bot (a developer account is created if needed); paid users get free X API credits to search posts, timelines, and mentions.
  • Getting started with Grok Bot - Cursor help: first-agent setup, Sidebar Sections on iOS v1.2.0+ to group Bots, the beta label is not Cursor Beta Services terms, and a restart-first troubleshooting table.
  • Subscribe from the mobile app - iOS in-app purchase is monthly individual only; existing Cursor or SuperGrok access carries over, and SuperGrok linking still has to be done on desktop.
  • Delete your Grok Bot account - Grok Bot has no separate account: iOS has Delete Account, desktop only signs out, and wiping it deletes the Cursor account plus agents, chats, and the computer.
  • @bot: improved X support - Official 2026-08-29: Grok Bot now has improved X support; connecting your X profile auto-creates a developer account with included credits.
  • Get help (Cursor Help) - Official Cursor help: contact Grok Bot support at hi@cursor.com and include account email, app version/platform (Mac/Windows/iOS), what you tried, and a screenshot (billing issues same inbox).
  • @bot: Microsoft Outlook, Calendar, and OneDrive plugins - Official @bot (2026-08-31) says Grok Bot can now read, write, and act across Microsoft accounts via new Outlook, Calendar, and OneDrive plugins.
  • Identity and access - Official admin guide: widen Cursor SSO assignment (Okta/Entra) so non-engineering teammates get Grok Bot, and add an IdP auth rule so the Linux Bot computer can sign into device-trust apps (passkeys/Team Setup); do not create a separate Grok Bot SSO app.
  • Private networks - Official Enterprise guide: use Team Setup to install Tailscale, Cloudflare Tunnel, or other Linux VPN/mesh clients on every team Bot computer so Bots reach private APIs without exposing them; private reach does not replace the Grok Bot destination allowlist.
  • @bot: Grok Bot is now available on Android - Official @bot (2026-09-02): Grok Bot is now available on Android — same Bots and threads as desktop/iOS, work continues on the cloud computer after you lock the phone; download from Google Play with an eligible Cursor/SuperGrok plan.
  • Grok Bot for Enterprise - Official 2026-09-03: Grok Bot is available for enterprises with access, network, and audit controls; Grok and Cursor Enterprise customers get free usage for the next two weeks and can invite the whole org, including people without an existing seat.
  • Designing Grok Bot for a world of persistent agents - Official 2026-09-03 design essay: Grok Bot is built around persistent Bots (not disposable chat sessions)—roster, presence, each Bot’s own computer, and work that can start without a prompt—organized by Bots, Chats, Prompts/Skills/Routines, Tools, and Artifacts.
  • Grok Bot security - Official security guide (new docs page): Enterprise Network Controls, Action Recording, audit/OpenTelemetry/SCIM, isolation on a per-user Firecracker microVM, and how connector policy differs from network allowlists.
  • Grok Bot security FAQ - Official security FAQ (new docs page): per-user isolation, what a Bot can access, why blocking a plugin does not block that site in the browser, and that Network Controls (destination allowlists) are Enterprise-only.
  • Grok Bot Guides - Official Grok Bot Guides hub: practical playbooks for AI teammates (teams of bots, mobile app studio, design, GTM, PMs), with category indexes for engineering, product, design, and GTM.
  • How I run multiple teams of Grok Bots - Official guide (2026-08-27): coordinate Grok Bots like a human team—each project gets a channel, a roster, and a Notion board, with a Projects Manager bot for staffing and task tracking.
  • Grok Bot for mobile app development - Official guide (2026-08-25): six specialized Grok Bots run a mobile game studio end-to-end—build, ship, analytics feedback loops, and skills recorded on the Bot’s own computer.
  • Designing Grok Bot with Grok Bot - Official guide (2026-08-24): a designer uses always-on Grok Bot agents (Figma production, motion prototypes, experiments, eng Q&A) to explore more ideas with real production assets while keeping human judgment in the loop.
  • Grok Bot for GTM - Official guide (2026-08-16): Enterprise GTM with Grok Bot—Chief of Staff, prospecting/account prompts, live slides, and the rest of the GTM roster on persistent cloud computers.
  • Grok Bot for PMs - Official guide (2026-08-15): PM playbook—attention lists, shipping via Cloud Agents, and a concrete Bot roster (Chief of Staff, EM, eng ICs, analyst, PM, recruiter) that reports to you.
  • Grok Bot use cases - Official use-case gallery on x.ai/bot: browse handoff-ready Bot jobs across sales, marketing, support, recruiting, ops, product, and engineering (distinct from the docs.x.ai/grok-bot/use-cases guide page).
  • Setting Grok Bot loose on procurement (Haggle Bot) - Official (2026-09-04): xAI’s Haggle Bot case—give a procurement Bot spend/contracts/usage access plus permission lines, and it surfaced $100k+ in evidence-backed SaaS-seat and renewal savings with a human still making final vendor decisions.
  • @bot: usage limits reset for all Grok Bot users - Official @bot (2026-09-05): SpaceXAI/Cursor reset usage limits for all Grok Bot users in a short product status post.
  • Bot Marketplace — public Grok Bot templates - Official x.ai Bot Marketplace hub for Grok Bot: browse 69 public, handpicked Bot templates across 9 categories (From Grok Bot Team, Engineering, Sales, Marketing, Design, Personal, Recruiting & People, Operations, Product) from 43 creators and add them to your roster.
  • Configure TLS-inspecting proxies (Zscaler / SWG) - Official Cursor docs for Grok Bot behind TLS-inspecting gateways (e.g. Zscaler): allow both *.cursorvm.com and nested ..cursorvm.com, exempt those domains from SSL inspection and response buffering, apply rules to every off-network profile, and verify with Amazon RSA issuer + nslookup test.us9.cursorvm.com—docs.x.ai has no proxies page.
  • Download Grok Bot desktop (macOS / Windows / Linux) - Official Cursor download hub for the Grok Bot desktop app: macOS (Apple Silicon and Intel), Windows (x64 and ARM64), and Linux (.deb, RPM, and AppImage for x64 and ARM64).
  • @bot: in-chat form/login fill with any password manager - Official @bot (2026-09-08): you can fill out forms and logins for your Bot without leaving chat, with support for any password manager (demo video in the post)—so you need not paste passwords into ordinary chat.
  • @bot QoL: inline draft messages to approve before sending - Official @bot (2026-09-09): quality-of-life update — ask your Bot to draft messages inline for you to approve before it sends (thread root of a Sep 9 QoL series).
  • @bot: Grok Bot natively available for iPad - Official @bot (2026-09-09): Grok Bot is now natively available for iPad (App Store link in post). docs.x.ai mobile/faq still say iPhone-only / iPad not supported — treat X as the primary announcement until docs catch up.
  • @bot: switch Grok Bot accounts with one click - Official @bot (2026-09-09): switch between Grok Bot accounts with one click (screenshot in post) — part of the Sep 9 QoL thread.
  • @bot: support for over 20 languages - Official @bot (2026-09-09): Grok Bot now supports over 20 languages (screenshot in post) — part of the Sep 9 QoL thread.
  • @bot: share a file directly with Grok Bot on mobile - Official @bot (2026-09-09): share a file directly with Grok Bot on mobile (screenshot in post) — part of the Sep 9 QoL thread.
  • @bot: Grok Bot sales/GTM connectors (Salesforce, HubSpot, Gong, Clay, Granola) - Official @bot (2026-09-10): Grok Bot is more powerful for sales teams — connect Bots to Salesforce, HubSpot, Gong, Clay, Granola, and other GTM tools for accounts, follow-ups, and research (thread also shares installable sales templates).
  • Bot Marketplace · Sales category (x.ai) - Official x.ai Bot Marketplace Sales category: browse installable sales Bots (Outbound Prospecting, GTM Loop Closer, Sales Call Coach, and more) with connectors and routines ready to add.
  • Grok Bot (Cursor Docs hub) - Official Cursor Docs hub for Grok Bot: what Bots are, shared cloud computer model, platforms, pricing entry points, and links into get-started, use cases, Teams/Enterprise, and security.
  • Grok Bot for Teams and Enterprise - Official Cursor Docs for Teams/Enterprise admins: enablement, Firecracker isolation, Team Rules, Enforce Auto-review, Network Controls, Team Setup, Action Recording, and recommended rollout baseline.
  • Grok Bot security - Official Cursor Docs security guide: Network Controls modes, static egress, Auto Review, identity/sign-ins, audit vs Action Recording, data residency (US), local execution, and ISO scope.
  • Grok Bot security FAQ - Official Cursor Docs security FAQ for reviewers: isolation, plugin vs network policy, dedicated egress (no), on-prem (no), Auto Review coverage, certifications, and computer termination behavior.
  • Configure identity and access - Official Cursor Docs for Grok Bot identity: SSO/SCIM carry-over, Okta/Entra steps for the computer browser, and how Bots act only as the signed-in member.
  • Connect to private networks - Official Cursor Docs on reaching private services from Grok Bot computers via Enterprise Team Setup networking clients (no Cursor-operated VPN/private link).
  • Routines (Cursor Help) - Official Cursor Help for Grok Bot routines: schedules/time zones, Slack keyword listeners, webhook URL+Bearer key, Run history limits, usage tips when weekly allowance drops fast, and server-managed routines.
  • @bot: Microsoft Teams for Grok Bot - Official @bot (2026-09-11): Grok Bot can now search and act across Microsoft Teams—first-party plugin to search, read, and send chats/channel messages (Add to Grok Bot via x.ai/bot/plugin/63354504).
  • Teams for Grok Bot (plugin) - Official Cursor Marketplace plugin “Teams for Grok Bot”: search, read, and send Microsoft Teams chats and channel messages; published by Grok Bot with Add-to-Grok install.
  • Grok Bot 101 - Official guide (2026-09-11): stand up a Grok Bot in ~15 minutes, chain specialists, use routines/triggers and multi-bot handoffs, plus Auto-review allow/block lists on a persistent cloud computer.
  • Grok Bot for Engineering - Official guide (2026-09-10): engineer Bot fleets that manage Cursor Cloud Agents, close multimodal screenshot feedback loops, and scale past manual agent switching (mini-org patterns).
  • Grok Bot for Support - Official guide (2026-09-09): SpaceXAI support queue with Grok Bot—connectors plus five jobs (release tracking, bug repro, triage, knowledge sync, escalation) and routines that keep running after you close the laptop.
  • Templates for Grok Bot - Official guide (2026-09-08): Templates share a Bot as a recipe (skills, memories, plugins)—not a clone—so sensitive code stays out; covers publish, install, and what is packaged.
  • Manage Grok Bot computers - Official Cursor Docs (Enterprise org admins only): bulk Recreate or Terminate member Grok Bot computers from the dashboard—durable disk kept; Team admin rights are not enough because one computer spans every team the member belongs to.
  • Onboarding - Official Cursor Help onboarding: create your first Bot with a short name/title/description, start with a no-external-change task, and review before approving actions.
  • Bot Marketplace · From Grok Bot Team - Official x.ai Bot Marketplace “From Grok Bot Team” filter: installable public Bots published by the Grok Bot team across engineering, sales, marketing, design, recruiting, and product.
  • Bot Marketplace · Product category (x.ai) - Official x.ai Bot Marketplace Product category: browse installable product Bots (Last30Days, Competitor Watching, Product Idea Stress Test, Projects Manager, and more) with connectors and routines ready to add.
  • Bot Marketplace · Design category (x.ai) - Official x.ai Bot Marketplace Design category: browse installable design Bots (Imogen, Figma Bro, Critiquito, Sable Game Art, and more) with connectors and routines ready to add.
  • Bot Marketplace · Engineering category (x.ai) - Official x.ai Bot Marketplace Engineering category: browse installable engineering Bots (Projects Manager, Researchy, Engineer Bot, Tinkabot, Nightly Audit Engineer, and more) with connectors and routines ready to add.
  • Bot Marketplace · Marketing category (x.ai) - Official x.ai Bot Marketplace Marketing category: browse installable marketing Bots (SEO/AEO Desk, Image Gen Bot, Clip Bot, Human Copywriter, AI Search Visibility, and more) with connectors and routines ready to add.
  • Bot Marketplace · Personal category (x.ai) - Official x.ai Bot Marketplace Personal category: installable public Bots for everyday life (credit-card max, home robots, plant care, morning newspaper, outbound calls, and more).
  • Bot Marketplace · Operations category (x.ai) - Official x.ai Bot Marketplace Operations category: installable public Bots for office ops, event requests, executive assistance, and org design/governance (Alfred).
  • Bot Marketplace · Recruiting & People category (x.ai) - Official x.ai Bot Marketplace Recruiting & People category (slug recruiting-people): installable public Bots for interview-loop coordination and talent discovery.
  • @bot: ~10% more included usage from harness efficiency (up to 35%) - Official @bot (2026-09-09): users now get an average of ~10% more included Grok Bot usage from a more efficient harness (up to 35% for heavy users) — missed sibling of the Sep 9 QoL thread already in catalog.
  • Grok Bot can use 1Password — share vault items, approve each fill - Official @bot (2026-09-16): Grok Bot can now use 1Password—share items in a vault, approve each fill, and keep secrets in the password manager; partnership follow-up notes more credential improvements coming; try from x.ai/bot (no dedicated docs/news page yet).
  • Get started with Grok Bot (Cursor Docs) - Official Cursor Docs: install the Grok Bot desktop app, sign in with your Cursor account, create your first Bot, and hand it an end-to-end task.
  • Settings and notifications (Cursor Docs) - Official Cursor Docs for Grok Bot settings: app preferences, per-Bot profiles and notifications, plugins, usage visibility, and app/computer updates (cursor.com path; docs.x.ai uses settings-and-notifications).
  • Grok Bot use cases (Cursor Docs) - Official Cursor Docs: roles that work well as Bots, with starter prompts, tools to connect, and how to turn a one-off task into a durable teammate.
  • Work with Grok Bot (Cursor Docs) - Official Cursor Docs hub for day-to-day Bot work: create/manage Bots, message and collaborate, use the shared cloud computer, and automate with skills and routines (no docs.x.ai /work equivalent).
  • @bot: Grok Bot can talk now (Voice) - Official @bot (2026-09-17 ~18:53 UTC / Sep 18 ~02:53 Asia/Shanghai): Grok Bot can talk now—Voice is rolling out on desktop and mobile over the next couple of days (demo video in post; follow-up https://x.com/bot/status/2100659464781394222); download via x.ai/bot (no dedicated docs/help/voice page yet).
  • @bot: Grok Bot can now send you voice notes - Official @bot (2026-09-18 ~18:24 UTC / Sep 19 ~02:24 Asia/Shanghai): Grok Bot can now send you voice notes (follow-up CTA https://x.com/bot/status/2101014479299617188); distinct from the earlier live Voice talk rollout—try from x.ai/bot (no dedicated docs/news page yet).
  • Manage Grok Bot computers (docs.x.ai) - Official SpaceXAI docs (Enterprise org admins only): bulk Recreate or Terminate member Grok Bot computers from the Cursor dashboard—durable disk kept; Team admin rights are not enough because one computer spans every team the member belongs to.
  • Configure TLS-inspecting proxies (docs.x.ai) - Official SpaceXAI docs for Grok Bot behind TLS-inspecting gateways (e.g. Zscaler): allow nested ..cursorvm.com, exempt those domains from SSL inspection and response buffering, and verify computer setup when chat still works but the cloud computer never connects.

Tutorials & Guides

Field Cases

Skills, Plugins & MCP

Reviews & Comparisons

Open-Source Alternatives

Community & Failure Modes

  • Grok Bot 0.58.0: screen view moved under Bot name (staff) - Staff (@kevinn, 2026-09-24): in Grok Bot 0.58.0 the separate top-right computer button was folded into the Bot’s name at the top center—open the Bot chat, click the name, Back to details, then the live screen preview at the top of that panel (fixes “screen view disappeared” / fully collapsed divider).
  • Ultra weekly Bot pool: each messaged bot burns a turn - Staff (kevinn, 2026-09-23): on Ultra, Grok Bot has its own weekly allowance separate from Cursor; spawning ~60 bots plus group chats burned usage fast because every bot that receives a message runs its own turn—prefer fewer bots (one bot + subagents), delete unused, or enable on-demand under Spending.
  • Print via registered local computer only (no home-LAN printers) - Staff (kevinn, 2026-09-23): agents run on a cloud computer and cannot see home-network printers—send the file to any signed-in Grok Bot desktop machine that has the printer, then print there; set Settings → Computer → “Execution on this computer” to Always allow to cut approval friction (Auto-review still checks).
  • No per-bot reasoning effort control (staff) - Staff (kevinn, 2026-09-23): there is no per-agent reasoning-effort control in Bot or chat settings—Grok Bot chooses how much reasoning a turn gets, and you cannot set it per bot, role, or template yet (team aware).
  • Route-through-desktop only reaches public IPs (not private / split-horizon) - Staff (deanrie, 2026-09-23): “Route traffic through this computer” only relays to public internet addresses—desktop rejects CONNECT when the hostname resolves to private ranges (192.168/10/172.16–31); public cloud hosts still work. Docs currently imply internal hosts should work; mismatch filed with the team (no ETA).
  • Origin CLI on Grok Bot is read-only; merge via UI or your machine - Staff (kevinn): Grok Bot’s Origin CLI is intentionally read-only (repos/PRs/diffs/checks); undraft/merge isn’t direct yet—ask cloud agents to open PRs ready-for-review, then merge on cursor.com/codebase or origin pr merge locally.
  • Fleet cost tip: fresh chat per task + quieter Bot-to-Bot handoffs - Staff (kevinn): each turn re-reads the bot’s full chat history—so week-long threads burn 80–90k tokens/step; use + fresh chat per task, keep Profile/Notion state, silence ack pings between bots, and space Routines (hourly+) to cut fleet spend.
  • Grok Bot harness efficiency: ~10–35% more effective usage - Staff: harness routing/caching/context work yields ~10% average (up to ~35%) more effective usage; avoid noisy group chats and overused subagents that burn quota.
  • Precise geometry edits: give Grok Bot SVG/draw.io, not PNG - Staff: raster PNG edits guess pixel coords and misalign; for track/line snaps give SVG, draw.io, or CAD and keep one source file so the bot edits exact geometry.
  • Grok Bot file handoff limits + QuickTime still+ALAC recipe - Staff: chat video cap is 200 MB; Mac CopyFromBox only for small files; connectors cannot take large binaries yet — use H.264 still + ALAC in .mov under the limit for QuickTime.
  • Agent Computer stuck “starting up” for 48–72h - Agent Computer stayed “still starting up” / unreachable for days; Update and Reset failed across devices.
  • 1Password vault-only sharing request for Grok Bot - Feature ask: share a single 1Password vault with Grok Bot instead of the entire account.
  • Grok Bot false play/state claims in playtest loop - Arcade Lab Tester seat made false play/state claims that treated preview mismatches as successful playtesting.
  • Grok Bot hung on Updating computer at 43% - Bot unavailable while the “Updating Grok Bot’s Computer” dialog stalls around 43% transferring the environment.
  • Grok Bot Routines don’t auto-wake at day start - Routines and sub-agents never fire their first run at the beginning of a new day unless the user manually says “wake up”.
  • Grok Bot reconnect loop — api2.cursor.sh bad cert host - Grok Bot stuck on “Can’t reach your computer” because api2.cursor.sh resolves to 100.60.17.13 serving a mismatched certificate.
  • Grok Bot usage drains too fast on Cursor Ultra - Report that coordinated Grok Bot + Cursor Cloud Worker work burns weekly Ultra usage far faster than expected.
  • Grok Bot forever box: agent-transcripts mirror never created - Forum report: forever-box agent-transcripts mirror is never created while server-agent-proxy transcript tail stays connected.
  • Grok Bot 0.57.1 Windows — 0x0 off-screen window cannot reopen - Forum report: Grok Bot 0.57.1 on Windows saves a 0x0 off-screen window state so the app cannot be reopened normally.
  • Grok Bot 0.57.1 Windows — quits under local Shell/CopyFromBox + Chrome UI - Forum report: Grok Bot 0.57.1 on Windows exits when local Shell/CopyFromBox runs with Chrome UI while the idle process stays up.
  • Grok Bot unreachable on Windows and phone since Sep 20 evening KST - Forum report: interactive Grok Bot chat reconnect-fails on Windows desktop and phone since 2026-09-20 evening KST while routines still run.
  • Local-exec file tools stay in the user profile root (staff) - Staff (deanrie, 2026-09-19): On a registered machine, Read / CopyFromBox / CopyToBox are limited to the user profile folder (e.g. C:\Users<you>), while Shell is not—so D:/G:\ and junctions that resolve outside the profile are rejected by the file tools. Workaround: CopyFromBox into the home folder then move with Shell, or read/copy other drives via Shell (Get-Content / Copy-Item). Team is deciding whether file tools should match Shell’s reach or bots should prefer Shell when the path is outside the profile.
  • Forum: 1Password connector needs one-time Mac setup (Windows) - Staff tip (2026-09-19): the 1Password Connect button on Windows is misleading—initial 1Password linking for Grok Bot must be completed once on a Mac with the 1Password desktop app, then Windows can use it.
  • Forum: Introducing Grok Bot - Launch thread: what people actually asked in the first 48 hours.
  • Bots are not a security boundary - Must-read: every Bot on the account sees the same logins and files.
  • Always-on workers vs topic threads - Community consensus: a Bot is a standing coworker, not a chat tab.
  • Free Cursor Ultra with Grok (Heavy bundle) - How SuperGrok Heavy maps onto Ultra + Bot, and what does not stack.
  • Reconnect issue - Real screenshot of “can't reach your computer” after a reconnect.
  • X login lock on the Bot computer - Cloud computers hit site risk controls. X locks are not theoretical.
  • ExternalShell blocked despite Always allow - Allow-lists still fail. Do not assume Always allow means always.
  • Deleted Cursor account orphans the Grok link - Account deletion can pin the Bot to a dead Cursor identity.
  • Hacker News discussion - HN thread on the launch — useful for the skeptical read.
  • Native desktop on Arch / Linux - Linux desktop is not first-class; this is the request plus community packs.
  • Does Grok Bot support local MCP? - Staff-confirmed: Grok Bot cannot attach local or stdio MCP; use remote HTTP MCP or the cloud browser.
  • Is Grok Bot Down Currently? - Aug 20–21 outage thread: bots fail mid-turn; staff point to Reset Grok Bot’s Computer under Settings → Updates.
  • Grok Bot 0.23.0 first setup: createAgent / Cannot reach your computer - Staff: first-setup createAgent can fail before a computer exists (no Reset). A later note: bad ISP DNS for *.cursorvm.com can also block the computer while Cursor API still works — try 1.1.1.1 or 8.8.8.8.
  • Grok Bot: Mac chat works, local computer reported offline - Staff-confirmed split: chat stays up while the Mac local-computer link drops; full quit reconnects, 0.23 shipped a fix.
  • Computer refresh wipes WhatsApp linked-device session in Grok Bot - Staff: computer refresh keeps /workspace, the browser profile, and ~/.config — not ~/.local/state, so WhatsApp link sessions vanish.
  • Grok Bot cloud workspace after trial exhaustion - Staff: trial end deletes nothing; bots stop replying, but Computer view still lets you export until you Reset.
  • Reset Computer window opens behind Settings (0.24.0) - Staff: the Reset confirm dialog that opened behind Settings is fixed in the latest desktop; Tab then Enter was the workaround on older builds.
  • Grok Bot webhooks failing with internal server error - Staff: webhook POSTs to api2.cursor.sh returned internal error; they rolled back a change and the same curl started working again.
  • Grok Bot Gmail connector cannot download attachment bytes - Staff: the Gmail connector lists attachment metadata only; no download tool. Use the cloud browser or park the file in Drive.
  • Does logging into Grok Bot count as a separate computer? - Staff: a Grok Bot login is its own Cursor device, and the cloud workspace can count as a second one toward Too many computers.
  • Grok Bot Notion plugin OAuth Invalid redirect_uri - Staff: Notion sign-in is stored on the account, so retry fails; Re-authenticate (not Connect) clears it and OAuth succeeds.
  • Grok Bot now has Channels - Staff: Grok Bot now has Channels (sidebar +, up to 6 bots per named space). A thread view that keeps the main chat visible is still in progress.
  • Stuck Reconnecting can be a local cursorvm.com block - Staff: the cloud computer was healthy; the Mac never finished reconnect because traffic to cursorvm.com was dropped (VPN or firewall).
  • Agent never surfaces Take over for login - Staff: login tasks should hand you the computer; ask it to hand me your computer, and skip passkeys with Try another way.
  • Grok Bot Cursor Agent usage and model selection - Staff: agents Grok Bot starts run in your Cursor account and burn Cursor plan usage; Grok Bot chat has a separate allowance; unnamed-model agents use your Cloud Agent default.
  • How to track Grok Bot releases - Staff: latest stable is 0.24.0; no public changelog yet (Settings → Updates plus X); there is no official Debian/Fedora desktop app.
  • Grok Bot hanging at Cleaning up after reset - Staff: the reset usually finishes on the backend; the dialog just misses the done signal at Cleaning up. Fully quit and reopen, then Recover — don’t Reset again.
  • Grok Bot 0.24.0 Windows white flash then the app closes - Staff: the cloud computer was healthy; a white flash then the process dying is usually local (endpoint security, locked %APPDATA%, or a partial install), not GPU.
  • Bots workspace looks empty after a rebuild - Staff: after a rebuild, logging in while the computer is still starting can show first-run UI; bots are not gone. Fully quit and reopen, and don’t create your first bot in that window.
  • No compact / new session; full transcript is sent each turn - Staff: desktop and iOS have no explicit Compact or same-bot new session. Auto-summary is not compact; the full transcript is sent, and there is no model picker.
  • Overbooked then Bot failed to respond is model load - Staff: “overbooked” then “Bot failed to respond” is service-side Grok model load, not your account, usage, or computer; wait for a quieter window or reset again.
  • Black screen after setup: hosted computer never finished starting - Staff: black screen after “Setting up Grok Bot’s computer” means the hosted computer never finished starting; reinstall will not help, and if the same account still works on iOS do not Reset (that drops bots)—wait for a staff rebuild.
  • 0.27.0 Windows: local host stays disconnected after clean registration - Staff: on 0.27.0 Windows the agent can say the local machine isn’t connected even after a clean daemon registration; fully quit every Grok process and launch once, and if it still fails it is service-side.
  • Webhook URL and sender key are desktop-only, not on iOS - Staff: a webhook routine’s POST URL and sender key only appear on the Grok Bot desktop app, not iOS; open the trigger card there (keep the desktop app updated).
  • Official X plugin auth is broken on desktop, Cloud, and Grok Bot - Staff: official X plugin connect/refresh is failing across desktop, Cloud Agents, and Grok Bot (including “connected but tools=0”); no clean workaround while they fix X-side app config.
  • Weekly Grok Bot usage can spill into paid On-Demand with no warning - Staff: spend order is Grok Bot weekly allowance, then referral/promo credits, then paid On-Demand, with no in-app warning; a $0 On-Demand cap does not block credits, so pause near 100% weekly meter if you want no spill.
  • Pro weekly pool is separate; overflow hits shared On-Demand - Staff correction: on Pro, Grok Bot has its own included weekly pool, separate from Cursor plan usage; overflow still bills the shared On-Demand pool, so set a $0 On-Demand cap if you want no paid spill.
  • Access is live for paid plans, not legacy request-based - Staff: Grok Bot is live for all paid individual plans (Pro / Pro+ / Ultra) and self-serve Teams with no percent or region rollout; legacy request-based pricing does not get it unless you opt into usage-based.
  • Gmail plugin OAuth is broken; authorize from Cursor - Staff: the Grok Bot Gmail plugin OAuth is broken; authorizing Gmail from Cursor uses a different path and the connection is shared with Grok Bot until the plugin is fixed.
  • iOS 1.3.2 sends a question list on the first tap - Staff: iOS 1.3.2 sends a question list as soon as you tap one option; multi-select before send needs a newer Grok Bot app build.
  • Grok-launched agents hide behind the Source filter - Staff: Grok-launched cloud agents do appear on cursor.com/agents — enable the Source → Grok Bot filter; middle-click “Open in Cursor” opens the same agent in the browser.
  • Days-long “Can’t reach your computer” needs a staff restore - Staff: a days-long “Can’t reach your computer” can be a stuck hosted box that Reset / Recover / reinstall cannot clear; staff restores it on their side, then fully quit and reopen the app.
  • Fresh-install white screen is a local profile, not the cloud box - Staff: a fresh-install white window is a local profile bug, not a stuck cloud computer; fully quit, rename ~/Library/Application Support/Grok Bot to Grok Bot.bak, then relaunch — reinstall alone will not clear it.
  • Grok-spawned Cloud Agents can ignore your non-Fast default - Staff: Grok-spawned Cursor Cloud Agents can start in Fast even when your default is not; hover Cursor Grok 4.6 → Edit and uncheck Fast, and switch the follow-up box back if it flips.
  • Local execution offline while chat still works - Staff: the local-exec helper can register then drop its server link, so the Mac shows offline while chat still works; fully quit and reopen, and if it fails again send ~/.grokbot/local-exec-daemon.log.
  • Reset stuck at 50% Starting is a server-side bad state - Staff: a Reset hung at 50% “Starting Grok Bot’s computer” is a bad hosted state, not your install; Bot data is not lost — wait a few minutes, and reply on the thread if it still fails.
  • Local CLI orchestration and always-allow are intended use - Staff: local-CLI orchestration (including Cursor CLI), always-allow local execution, and authenticated browser sessions are intended Grok Bot use; third-party ToS stay separate, bots share one computer, and a continuous Pro orchestrator burns the weekly pool fast.
  • Local-computer helper fails registration - Staff: the local-computer helper can start then fail registration after an update; full-quit plus sign-out recreates it, and desktop 0.31.0 is rolling out.
  • Mac black screen is local DNS not cloud - Staff: Mac 0.30.0 black screen with working iOS bots is a local network/DNS block to the healthy cloud computer, not a recreate-computer problem.
  • Grok Bot does not spend Pro $20 IDE credit - Staff: Pro’s $20 Other Models credit is not Grok Bot’s weekly pool; dashboard “Included in Pro” is shared billing — and with On-Demand off the Bot can still drain Cursor credits (referral/promo) before stopping (see 169982).
  • Does GrokBot not have access to my Cursor Codebase? - Staff: Grok Bot has no codebase plugin and does not index your repo; coding work is handed to a Cursor Cloud Agent on a GitHub-connected account (Dashboard → Integrations), with an optional GitHub PAT connector for read-only, auto-created repos from scratch, and no Origin access yet.
  • Phantom in Grok Bot is a Mess - Staff: the Phantom plugin runs on @phantom/mcp-server and each new auth creates a separate dedicated agent wallet, not your personal Phantom wallet, so reconnects show a new address while funded funds stay on the old agent wallet (recover via chat history or Phantom Support).
  • Grokbot custom connectors - Staff: there is no settings form for custom connectors; tell the Bot in chat to add an MCP server (public HTTPS streamable HTTP/SSE), confirm the details, and new tools appear from the next message — localhost-only MCP on your PC is unreachable from the cloud computer.
  • Grok Bot: Drive MCP should write Google Docs body and Sheet cells, not only file metadata - Staff: in-place Google Doc/Sheet editing lives in the dedicated Docs and Sheets connectors (edit content against the existing file ID), while Drive is file-level only; add both from the connector marketplace with the same Google account.
  • Blank screen after opening Grok Bot - Staff: a blank/white screen usually means the desktop app cannot reach the cloud computer; Cloudflare WARP can intercept that traffic even on a hotspot — turn WARP off or use split tunneling/excluded routes, and prefer builds after 0.28.0 that show an error+retry instead of a blank screen.
  • Cloud Agents created in Grok Bot not displayed in Cursor - Staff: Cloud Agents launched from Grok Bot keep running under your account but stay hidden on cursor.com/agents and the desktop sidebar until you enable filter Source > Grok Bot (once per client: web and desktop).
  • Can't reach your computer from last 72 hours - Staff: when the cloud computer is healthy but the app still says Can’t reach, set both IPv4 and IPv6 DNS to 1.1.1.1/8.8.8.8 (JioFiber routers often keep IPv6 DNS) or confirm via a phone hotspot on another carrier.
  • Grok Bot 0.30.0 stuck on "Setting up your Grok Bot" on macOS - Staff: endless Setting up your Grok Bot on a free Cursor plan means no hosted machine is provisioned — needs Pro/Pro+/Ultra/Teams or linked SuperGrok/Plus/Heavy; the spinner instead of an access message is a known UX bug.
  • Grok Bot Zoom plugin OAuth hardcodes http://localhost:8787/callback — Zoom rejects hostname localhost (error 4700) - Staff: the catalog Zoom plugin OAuth hardcodes http://localhost:8787/callback, which Zoom rejects (error 4700); no user workaround until the redirect moves off localhost (e.g. 127.0.0.1).
  • Unable to reconnect to my Grok Bot's computer after attempted update - Staff: bots/files/logins live on the remote computer; Can’t Reach plus failed Recover/Reset often means a lost app login session — fully quit, sign out/in (or reinstall and sign in), since Recover/Reset need a working session.
  • Grok Bot Computer Stuck in Partial State — Reset Failed, Existing Cloud Computer Unreachable - Staff: hold off on Reset/Recover after a scary partial-state dialog — data is remote and failed resets often failed on the app side; re-login, verify via mobile on cellular, and try public DNS / disable VPN before resetting.
  • Grok Bot couldn't finish setup - Staff: Can’t reach your computer on Linux Grok Bot 0.18.0 is not your network — Grok Bot is not officially available on Linux yet and that old build is rejected; supported platforms are macOS, Windows, and iOS.
  • Grok Bot 0.30.0 (Windows) — setup fails with Can't reach your computer, all network checks pass - Staff: the app reaches a per-computer subdomain under cursorvm.com, not the apex — if nslookup test123.us8.cursorvm.com is Query refused while the apex works, change DNS on both IPv4 and IPv6 (router RA can keep the ISP resolver even after 1.1.1.1).
  • Grok Bot draining Cursor credit pool - Staff: after the Grok Bot weekly pool on Pro+ is gone, usage keeps going onto Cursor credits (referral/promo) first, then on-demand if enabled; a $0 on-demand cap stops paid overage but not credit drain, and claude-opus / grok-4.6-high-fast lines are models the Bot picks server-side.
  • Grok Bot templates: preview shows skills, but the export ships skills: [] — skills are never delivered - Staff: Bot template preview lists skills, but import does not apply them (export ships skills: []); until that is fixed, copy the skill body from the preview and ask the new Bot to recreate it.
  • Cloud computer wipes packages after rebuild - Staff: Update Computer keeps files and logins but rebuilds the OS image, so apt/apps/daemons are gone; the box also sleeps when idle (background processes die) and can auto-update during idle — keep a package list in a file and ask the Bot to reinstall after an update.
  • /review-bugbot is missing on cloud agents launched from Grok Bot - Staff: /review and /review-bugbot do not attach to cloud agents created by Grok Bot (decided at create time); start a new agent from cursor.com/agents on the same PR branch and include /review-bugbot there.
  • Grok Bot Bug Report (empty roster / black screen after reconnect) - Staff: empty bot list and black/white loading after reconnect usually means the Agent Computer was slow waking from sleep—nothing deleted; do not Reset; fully quit and relaunch once the box is awake.
  • Grokbot and GitHub (Connected but Authorization header badly formatted) - Staff: GitHub connector shows Connected but fails with “Authorization header is badly formatted”—tracked bug; workaround is press-and-hold the account → Remove, then reconnect and sign in again.
  • Authorization death by 1000 clicks - Staff: “Always allow” for local-computer actions lives only in the desktop app on that machine; iOS can only one-time-approve, and those approvals clear on every new message—set Always Allow under desktop Settings → Execution on Local Computer.
  • Wrangler/box auth reminder stays stuck after auth already succeeded via another path - Staff: the “help on its computer” / Waiting-for-you reminder only clears when you answer that card (“I’m done, continue” or Skip) or send any chat message—it does not auto-dismiss if the Bot finished login another way.
  • Fastmail Filters & Rules Save is a silent no-op (Chrome on the box) - Staff: Fastmail Settings → Filters & Rules Save on the box Chrome fires zero network requests; workaround is manage filters/Sieve via Fastmail’s API (JMAP) with a token—the mail helper already uses that path successfully.
  • VPN, SSO, Passkey, and YubiKey Within Grokbot - Staff: Grok Bot’s cloud computer cannot join a corporate VPN today (don’t install a VPN client on it — that can knock the box offline); Atlassian Cloud / public SSO works via browser takeover (Okta etc.), YubiKey works on macOS/Windows under Settings → Security Key, and internal VPN-only sites need Execution on Local Computer on your VPN’d machine.
  • Unable to connect - Staff: chats and agents live on the hosted Grok Bot computer — during an outage recovery that computer can be temporarily replaced with a blank one (roster looks empty); Cursor can restore it from saved data, then quit and reopen the app to see agents/history again.
  • GrokBot Linux Execution on Local Computer not working - Staff: empty ListMachines / local execution failing on Grok Bot 0.30.0 Linux is a known bug with a fix already merged for the next desktop update; interim workaround is an unlocked system keyring (gnome-keyring or KWallet), fully quit leftover Grok Bot processes, then relaunch.
  • New report, Windows, leftover daemon on 0.30.0 - Staff: 0.30.0 fixed one macOS daemon exit/no-respawn path, but Windows leftover local-exec-daemon is a different known failure; when the machine is unreachable, Quit from the tray, end remaining “Grok Bot” and local-exec-daemon processes in Task Manager, relaunch, and wait about a minute to re-register.
  • Grok bot failed to respond - Staff (kevinn): “Bot failed to respond” on every bot—including fresh copies—means the shared cloud computer is stuck, not something you can fix by restarting or recreating bots; after staff recovery, fully quit (Cmd+Q / force-close iOS), update every install, keep one open, and test in a new chat.
  • Grok Bot 0.30.0 Stuck on Black Loading Screen During Initial Setup on Mac - Staff (Colin): Team admin role alone does not provision a Grok Bot computer — Grok Bot is included with a paid team seat (Standard or Premium), not the admin role. If the signed-in account has no seat, the app sits on the black loading screen with no computer to reset. Fix: assign yourself a seat in Cursor dashboard Members, fully quit and reopen Grok Bot; or sign in with a seated team account.
  • Grok Bot: weekly usage hits 100% after bot-to-bot reviews the user asked to stop - Staff (mohitjain): Each bot-to-bot message burns a weekly-usage turn; asking bots in chat to “stay quiet” is only a hint. Reliable fixes: run work in one Command Agent with subagents (they finish and stop), and delete unused specialist bots (idle bots can still be woken; deleting also clears that bot’s chat — save first). Double limit banners are blocked retries, not double charges.
  • Grok Bot Windows — fresh profile setup fails with “Can’t reach your computer” after backend fix - Staff (deanrie): Grok Bot ignores the Windows system proxy / local HTTP proxy and connects direct to the Agent Computer — so DNS/TCP/CONNECT checks through a proxy can pass while the app fails. Use VPN/proxy TUN (Enhanced/Global/virtual adapter) mode, then verify with curl.exe --noproxy "*" -I https://test123..cursorvm.com (expect 404 awselb/2.0). User confirmed TUN fixed setup. Region may be us10 not us8.
  • Grok Bot 0.30.0 stuck on black loading screen on Windows 11 - Staff (Colin): Healthy cloud computer + black spinner on both LAN and hotspot can be Zscaler Client Connector still tunneling (including on hotspot). Quit Grok Bot, pause/disable Zscaler, relaunch; ask IT to allowlist/exclude SSL inspection for *.cursorvm.com and **.cursorvm.com (both levels).
  • Grok Bot cannot attach inline images to Cursor bug reports (chat drop and forum upload) - Staff (mohitjain): To get a screenshot into Grok Bot chat, use the composer + button (or drag a saved file) and wait for the thumbnail before send — drag-from-browser/other-app or Enter-before-thumbnail usually drops it. Forum upload by the assistant is a current limitation; attach the screenshot yourself or reply to support email.
  • Grok Bot routines don't auto-run on schedule - Staff (Colin): Editing bot instructions or which platform created a routine does not break schedules — late “Next run: Run now” usually means the slot fired but sat in a queue (often 10–37 min), and some runs finish without posting to chat; don’t recreate routines; message the bot for an on-demand check-in.
  • Grok Bot 0.30.0 — Agent Computer unreachable after Update, Recover, and Reset all failed - Staff (kevinn): An “Aw, Snap!” Chrome page on the Bot screen after idle wake is the Bot’s browser crashing inside a healthy computer — reload the tab or ask the Bot to reload, fully quit/reopen Grok Bot if needed, and do not run Update/Recover/Reset; idle machines take a moment to wake and a first message can miss, so resend is safe.
  • Grok Bot Mac “unavailable” after password reset (expired session) - Staff (deanrie): After a password reset, Grok Bot on Mac can keep an expired session and show “isn’t available on this account yet” even though SuperGrok/Cursor access and your cloud computer/Bots are fine — Log out from the bottom of that screen, fully Quit (Cmd+Q), reopen and Sign in with the new password; Check Access→download is a misleading expired-session UI, not a missing entitlement.
  • Homepage “Approval needed” stuck after card timeout - Staff (Colin): A homepage “Approval needed” tile with nothing pending usually means an approval card timed out (~10 minutes unanswered); open the agent and send a short message or restart the app to clear a stuck badge — the tile is supposed to clear when the card expires.
  • File contents and grokbot — viewer Copy vs Download - Staff (Colin): The in-app file viewer only offers Download today; for .md/.txt you can click-drag to select and Cmd/Ctrl+C, while .docx/.pdf won’t highlight — ask the Bot to paste the full text into chat and use the message Copy action as a workaround.
  • Grok Bot Canva connector failing — Invalid redirect URI on iOS - Staff (deanrie): Canva “Invalid redirect URI” on Grok Bot iOS 1.4.0 is a known app-link vs web-redirect mismatch (not your Canva settings) — connect Canva from desktop Grok Bot on the same account and the connector syncs to iPhone.
  • Local computer looks connected but CopyFromBox/Shell flaps after large transfer timeout - Staff (deanrie): A large CopyFromBox (or timed-out Shell) can drop the local machine from the agent list for ~1 minute while Settings still says connected — split big copies, wait a minute before retrying, and if stuck Cmd+Q then pkill -f local-exec-daemon and reopen.
  • Why does Grok Bot chat use so many sand-* tokens? - Staff (mohitjain): Conversations use the Grok Bot weekly pool, but routines/automations and browser/CUA actions run as cloud agents on your Cursor plan and can drain Other Models (blocking Claude/GPT) even when the Grok Bot bar still has room—pause heavy grok-bot-automation / grok-bot-cua routines or enable on-demand.
  • Grok Bot Windows — Can't reach computer on Free plan / after SuperGrok link - Staff (deanrie): “Can't reach computer” can mean the signed-in Cursor account is Free with no Grok Bot entitlement (not DNS)—link SuperGrok on the same Cursor account via cursor.com, then fully sign out/in (or Quit from the Windows tray) so the desktop app refreshes access.
  • Grokbot failing to connect to cloud agent — Privacy Mode (Legacy) false positive - Staff (deanrie): Launching a Cloud Agent from Grok Bot can falsely hit the “Privacy Mode (Legacy)” check after a recent release even when your account uses current Privacy Mode—Cursor Desktop launch still works; sign-out/reset won’t help; staff are tracking a server-side fix.
  • Grok Bot 0.39.0 first setup: Reconnecting forever until Privacy Mode is saved - Staff (deanrie): First-setup “Reconnecting to your computer” can mean the account never saved an explicit Privacy Mode choice (data notice alone is not enough)—set Privacy Mode in cursor.com/dashboard → Settings → Privacy, fully Quit (Cmd+Q), reopen; Retry/Recover/Reset will not fix a missing privacy choice.
  • Grok Bot reset usage early — Sep 1 global weekly reset - Staff (deanrie): Seeing weekly usage drop to 0% mid-cycle can be the Sep 1 global Grok Bot weekly-usage reset (announced on X), not an account bug—the next-reset countdown keeps running, so remaining days may look unchanged while the bar restarts at 0%.
  • Status beat leaks between bots — one Bot memory across 1:1 and groups - Staff (Colin): Status “leaks” across chats are expected—each Bot has one conversation and one memory spanning its 1:1 and every group it joins; group turns are room-tagged but memories belong to the Bot, so keep Project X and Y on separate Bots (or file notes under a project folder, which is less reliable than separate Bots).
  • Shopify browser blocked — use Admin API / custom MCP, not agent Chrome - Staff (Colin): Shopify’s anti-bot check blocks the agent computer’s browser—skip login pages and use a store custom app Admin API token via Settings → Plugins custom MCP (community Shopify Admin MCP) until a first-party Shopify connector ships.
  • Unreachable after heavy media — 16 GB RAM exhaustion - Staff (Colin): “Unreachable” during heavier media work often means the cloud machine hit its ~16 GB RAM ceiling within minutes—Recover keeps Bots/files/logins intact; until the machine rides it out, keep jobs under that memory budget.
  • Can’t reach after Active Sessions revoke — sign out/in, not Retry - Staff (Colin): Apps showing Can’t-reach after an Active Sessions revoke on cursor.com still hold the old session—Retry/Update/Reset and VPN won’t help; sign out and back in on each device (0.39.0 is unrelated), and bots load once the new session sticks.
  • Linux RPM Access Denied — use direct package / yumrepo links - Staff (deanrie, 2026-09-05): Download page RPM buttons still point at an old filename (Access Denied)—packages are fine; use the direct x64/arm64 0.39.0 RPM URLs or install via downloads.cursor.com yumrepo/grok-bot + anysphere.asc until the page is fixed.
  • Connected but “temporarily unreachable” — local-exec slower than 10s wait - Staff (deanrie, 2026-09-05): On 0.43 Windows, ListMachines can show connected while Shell fails with temporarily unreachable when the PC answers ~11s but the agent stops waiting at 10s—commands did run; renaming the PC / toggling Local execution won’t help; share local-exec-daemon.log and check AV, OneDrive/AppData redirect, VPN/proxy.
  • Windows instant crash — Codex sandbox ACL missing S-1-15-2-2 - Staff (deanrie, 2026-09-05): Quiet Windows launch crash (int3 / 0x80000003) is often AppData\Local install ACLs left by CodexSandboxUsers without ALL RESTRICTED APPLICATION PACKAGES (S-1-15-2-2)—--disable-gpu/--jitless won’t help; diagnose with --disable-gpu-sandbox, then icacls grant S-1-15-2-1/2 (RX) on the Grok Bot folder (and optionally %LOCALAPPDATA%\Programs) or remove the orphaned Codex SIDs and /reset.
  • SuperGrok vs Heavy for Grok Bot — usage grant size only - Staff (deanrie, 2026-09-05): Documented SuperGrok vs SuperGrok Heavy difference for Grok Bot is linked usage-grant size only—no published latency/queue/tool-speed advantage while in allowance; linking any SuperGrok tier is a usage grant and does not change your Cursor plan (late-August “free Ultra with Heavy” materials are outdated—see Plans and Link SuperGrok help).
  • “Bricked” after Reset — graphrag embedding RAM OOM - Staff (deanrie, 2026-09-05): A “bricked” Agent Computer after heavy indexing can be graphrag embedding hitting the VM RAM ceiling (not disk)—Reset may take up to ~1 hour and re-clicking restarts the timer; after it returns, stop auto-indexing, check free -h, and run embedding/graph builds in smaller batches so memory stays under the limit (apt/pip outside working files need reinstall after Reset).
  • Windows: secret-card chat — replies missing in main pane (sidebar/mobile OK) - Staff (deanrie, 2026-09-06): On 0.43 Windows, a chat where the bot asked for a key/password (secret card) can stop showing new replies in the main pane while sidebar preview and mobile stay current—messages still reach the bot; computer is fine so don’t Reset/Recover/reinstall/clear data; server-side fix rolls out automatically (≤24h), no app update needed; use mobile for that thread meantime.
  • Mac 0.43: secret-card chats — “Couldn’t load conversation” (iPhone/sidebar OK) - Staff (deanrie, 2026-09-06): On 0.43.0 Mac desktop, a conversation where the bot asked for a secret/credential can stop opening (“Couldn’t load conversation”—misleading; not network); iPhone and sidebar preview still work and Mac sends still reach the bots—don’t Reset Agent Computer, reinstall, or update the app; background server fix applies per computer (few hours, ≤24h).
  • Mac 0.43: lost computer after password change — sign out/in, don’t Reset - Staff (deanrie, 2026-09-06): On 0.43.0 Mac, a Cursor password change/reset (or sign-out elsewhere) can invalidate the desktop session so the app keeps the old token and shows “Couldn’t Reach Grok Bot’s Computer,” with Update/Recover/Reset also failing—computer and Bots are fine; sign out and back in on desktop (Quit from menu bar if Sign out is missing), don’t Reset.
  • Mac 0.43: main chat pane misses replies (sidebar + iOS OK) — don’t Reset - Staff (deanrie, 2026-09-06): On Mac app 0.43.0 the main chat pane can stop live-updating so sends look undelivered and replies never appear there, while iPhone and the left sidebar preview stay current—bots still receive messages; don’t Reset/Restore/reinstall or recreate the Bot; use iOS (or unaffected bots) until the tracked UI bug is fixed.
  • Bots “not responding” / Reset failed — save Privacy Mode on dashboard - Staff (deanrie, 2026-09-06): Account-wide unreachable bots with “Couldn’t refresh,” black bubbles, and “Reset failed” can mean no explicit Privacy Mode choice was saved (data notice alone is not enough)—computer/bots/files are safe; set Privacy Mode (not Legacy) at cursor.com/dashboard → Settings → Privacy, fully quit/reopen apps, wait ~1 minute; don’t keep hitting Reset/Retry/Recover.
  • Local Shell Auto-review: “executable content could not be bound” — pipe workaround - Staff (deanrie, 2026-09-06): Local-exec Auto-review can reject before any approval card when Grok Bot can’t read a compiled binary (e.g. /usr/bin/python3) or flag-first args like python3 -c / bash -c—“Allow once” won’t help; pipe code in (echo "print('exec-ok')" | python3) or run a home-folder .py with just the interpreter name; avoid absolute program paths, -c, heredoc-on-stdin, and ~/ inside interpreter args until fixed.
  • computerUse GTK Open Files no-ops — dock overlap; bypass with DOM.setFileInputFiles - Staff (deanrie, 2026-09-06): On the Bot computer, GTK “Open Files” Open/Cancel often sit on the bottom dock so clicks hit the dock and the dialog no-ops (file itself is fine)—ask the Bot to set the page file input via DevTools DOM.setFileInputFiles to a /home/box/... path (no dialog), or drag/maximize the dialog so Open clears the dock; known dialog-geometry issue, tracked.
  • Can’t send (computer screen still visible) — server disconnect; prefer wait over Reset - Staff (deanrie, 2026-09-07): When every send fails with “Couldn’t send / Failed to send” on all devices but the Agent Computer screen stays visible, it can be a temporary server-side loss of connection for some Grok Bot computers—not Mac/Android/app 0.44.0; connection usually returns without data loss, so message staff before Reset; Reset rebuilds from the last snapshot and may drop the newest unsynced changes.
  • Gmail MCP: Spam search empty by default — use in:anywhere (+ label:SPAM) - Staff (deanrie, 2026-09-07): Grok Bot’s Gmail connector search excludes Spam and Trash by default, so search_threads can return empty while list_labels still shows Spam counts—includeTrash only adds Trash, and in:spam / label:SPAM / is:spam do not override; ask the Bot for search_threads with in:anywhere label:SPAM (or in:anywhere is:unread); connector can move/label to Trash/Spam but Google’s server exposes no permanent-delete tool.
  • 0.44.0 Shell Auto-review pre-check: absolute interpreter path — use relative + cwd - Staff (deanrie, 2026-09-07): On 0.44.0 the “executable content could not be bound” rejection is a pre-check before review, so no approval card (and no approval-request retry) appears—trips on absolute interpreter paths (/…/venv/bin/python), python3 -/ -c / -m, and heredocs into the interpreter; desktop updates won’t help (check isn’t in the app); until fixed, set working_directory and run a relative interpreter+script (e.g. venv/bin/python script.py) with no flags between them, or plain python3 script.py for short scripts.
  • CallDynamicTool Missing namespace/toolName — put keys top-level (or Duplicate) - Staff (deanrie, 2026-09-07): When CallDynamicTool fails with “Missing required fields: namespace, toolName” while Shell/files still work, the bot nested namespace/toolName inside arguments—and bad shapes in chat history keep repeating. Reset Computer won’t help (history isn’t on the computer). Tell the bot: namespace and toolName must be top-level keys alongside arguments, never inside arguments, then have it SendToAgent a one-line hello; if that still fails, Duplicate the bot for a clean chat. Confirmed: Step 1 fixed SendToAgent/Task.
  • Export/backup Bot memory — ask bots to zip durable state (no one-click yet) - Staff (mohitjain, 2026-09-07): No one-click export yet—memory lives as plain text on the Bot computer. Per bot, ask it to make backup/, copy full memory (profile + every memory-log month) to memory.md, list routines and connectors, zip and attach; ask Chief of Staff for shared-memory.md + skills-library zip; for other folders, zip/split (attachments cap 25 MB). Connector logins can’t be exported (list only). Optional: also write a SKILL.md per memory topic into the zip.
  • iOS Inkbox “Unsupported redirect_uri” — auth on desktop (account-default shared) - Staff (mohitjain, 2026-09-07): For account-default shared connectors like Inkbox, the identity you authorize on desktop carries to phone—you usually don’t need the iOS Connect card. If iOS still shows “Unsupported redirect_uri” but tools work after desktop auth, skip Connect on mobile and just ask the bot to use the tool (or reopen the app). Mobile connect-flow redirect_uri bugs remain tracked separately.
  • Teams: grok-bot-* under Cursor Models is display-only — separate weekly pool - Staff (mohitjain, 2026-09-07): On Cursor Teams, Grok Bot does not use your Cursor Models allowance—it has its own weekly pool (shown in the Grok Bot app); dashboard grok-bot-* rows under Cursor Models are display-only (grouped by model, not product) and won’t rate-limit you, but cloud agents launched from Grok Bot still count toward your Cursor plan.
  • Ahrefs plugin “Failed to load connector” — provider rate-limit (don’t reinstall) - Staff (Colin, 2026-09-07): Ahrefs marketplace connector showing “Failed to load connector” / tools=0 is Ahrefs rate-limiting Grok Bot’s connection attempts—not a bad install; reinstalling or re-adding the account won’t fix it; retry later may occasionally work until Cursor changes the connector to back off and retry.
  • Mac 0.43 one-agent Failed to send (iOS OK) — update desktop to 0.44.0 - Staff (mohitjain, 2026-09-07): If one Bot’s Mac chat shows “Failed to send” / missing replies while iPhone has the full thread and other Mac bots work, the bot is fine—desktop 0.43.0 can’t load that conversation; Reset/reinstall won’t help; update Grok Bot desktop to 0.44.0 (Settings → Updates; fully quit Cmd+Q if it claims you’re current) and use iOS until then.
  • Shell Auto-review: npm/pnpm/yarn substring blocks before approval card - Staff (Colin, 2026-09-07): “executable content could not be bound” can fire in a pre-check before any approval card when the command text contains npm/pnpm/yarn anywhere—including a full path like /workspace/.../bin/npm; until fixed, run PATH=/path/to/node/bin:$PATH npm ci (or npm install / npm run) as a single command with working_directory set—avoid absolute .../npm, npm -v alone, and && chains with npm.
  • Synced skills reach Agents Window only — not Grok Bot-started cloud agents - Staff (deanrie, 2026-09-07): “Sync Skills for Cloud Agents” can hang on the final verification step after downloads finish (reason=missing), and even when sync succeeds only cloud agents started from the Cursor desktop Agents Window pick up ~/.cursor/skills—agents started from Grok Bot (or cursor.com/agents) do not yet; workaround: launch the cloud agent from Agents Window until the gap is fixed.
  • Public template publish “team must be selected” — leave leftover workspaces - Staff (mohitjain, 2026-09-08): On personal Ultra, Public template export can fail with “A team must be selected to share a team template” when the account is still attached to leftover team workspaces (old invites/trials)—leave extra teams at cursor.com/dashboard, then ask the Bot to share as Public again for the review card and x.ai/bot link.
  • stdio MCP wrappers in bot secrets break after bot delete — use shared path - Staff (mohitjain, 2026-09-08): Account-wide stdio MCP servers that spawn a wrapper under agents//secrets die when that bot is deleted—keep wrappers/creds in a bot-independent path (e.g. /home/box/mcp-wrappers/), re-point the server command (or register npx/uvx + env keys directly), then Restart MCP.
  • MCP “needsAuth” badge for non-OAuth connectors is cosmetic - Staff (mohitjain, 2026-09-08): The Plugins badge only treats OAuth as authenticated, so public/API-token connectors (e.g. Cloudflare docs, Fastmail) can show needsAuth even when tools already run—Authenticate just reconfirms and a restart re-reads the same state; leave them as-is unless the badge blocks other bots.
  • GitHub plugin “Needs auth” / no sign-in link — PAT Setup Values already work - Staff (mohitjain, 2026-09-08): The GitHub plugin signs in via the personal access token under Setup Values (Edit Values), not a browser OAuth link—so Needs auth plus “Github didn't provide a sign-in link” is a labeling bug when tools already load; confirm with “Using the GitHub connector, which GitHub user am I signed in as?” and ignore the badge.
  • Trial ended shows as “Can’t reach your computer” — renew/link plan - Staff (deanrie, 2026-09-08): After the 1-week free Grok Bot trial ends, the app can keep showing “Can’t reach your computer” / *.cursorvm.com / Zscaler copy even though Retry/Recover/re-login won’t help—pick a plan that includes Grok Bot (or link SuperGrok at cursor.com with the same email), fully quit from the menu bar, reopen, and sign in again; bots/files stay saved.
  • Desktop reconnect overwrites in-chat secure secrets - Staff (Colin, 2026-09-08): When the Grok Bot desktop app reconnects to your cloud computer (e.g. after sleep or an overnight drop), it re-syncs the app’s secrets list and currently overwrites secrets saved via the in-chat secure input—re-enter those credentials after reconnect until the sync bug is fixed; Update/Reset are not the cause.
  • Robinhood MCP OAuth: https callback + 15-minute window (connect on desktop) - Staff (deanrie, 2026-09-09): Robinhood Agentic Trading MCP sign-in from Grok Bot no longer uses grokbot://—since 7 Sep it uses an https://www.cursor.com/agents/... callback—and the auth code expires in about 15 minutes, so finish Allow quickly (approve the Robinhood device first if asked); if phone OAuth keeps failing, connect once from Grok Bot desktop or Cursor on the same account so the trading tools sync to mobile.
  • Home Wi-Fi: curl OK but streaming fails — Private Relay / cellular IP - Staff (deanrie, 2026-09-09): When the cloud computer is healthy and hotspot works but home Wi-Fi fails—even if short curl to api2/cursorvm looks fine—the app needs long-lived streaming that your network may drop; fully Quit, then try iCloud Private Relay off, DNS back to router-automatic (remove 1.1.1.1/8.8.8.8), and check cellular routers that rotate multiple IPs (fine for curl, cuts long-lived app links).
  • Cursor password reset → ~30 min Authentication error (auto-reconnect) - Staff (mohitjain, 2026-09-08): Resetting your Cursor password signs out every session—including the Bot cloud computer’s background session—so chat can return “Authentication error” for about 30 minutes; it reconnects on its own (no reinstall / Reset / Update). Sign the phone in with the new password; distinct from Mac “unavailable” expired-session UI (170389) and 0.43 sign-out tips (170775).
  • Routines need Cursor Pro+ — SuperGrok + Cursor Start won’t schedule - Staff (Colin, 2026-09-09): Routines (scheduled runs) are the one Grok Bot feature that checks the Cursor plan—if Grok Bot access comes from a linked SuperGrok account while Cursor is on Start, the server refuses to schedule routines no matter how often you reset the bot or computer; move Cursor to Pro or higher and routines start syncing with no other changes (other Bot features keep working).
  • Weekly allowance lasts longer: fresh chats, space routines, cloud-agent manager - Staff (mohitjain, 2026-09-10): Grok Bot bills for work done (tools, browser, subagents, re-reading history each turn)—not message count; long threads with high cache-reads get pricey. Biggest wins: start a fresh conversation per task; space routines (avoid every-few-minutes; prefer hourly / dedicated bot); delegate heavy implementation to Cursor cloud agents (manager pattern) so execution burns Cursor plan, not the weekly Bot pool; scope tightly and check the meter.
  • Windows F-Secure: DeepGuard delays local-exec past 10s (folder exclusions miss Temp) - Staff (mohitjain, 2026-09-10): F-Secure often delays each local-exec command past the agent’s ~10s wait (not a hard block)—folder exclusions fail because each command is a fresh one-off PowerShell under %LOCALAPPDATA%\Temp. Bisect: DeepGuard off only → real-time off only → allow Grok Bot.exe from %LOCALAPPDATA%\Programs\Grok Bot in DeepGuard → temporary Temp exclude as last test; report which step works for a proper allowlist. Complements the generic “connected but >10s unreachable” tip.
  • Cursor Ultra ≡ SuperGrok Heavy for Grok Bot (no stack; free Ultra offer ended) - Staff (deanrie, 2026-09-10): For Grok Bot, Cursor Ultra and SuperGrok Heavy are the same top tier—same weekly quota, models, speed, priority; having both does not stack (highest wins). Ultra also includes Cursor IDE/Agent/Cloud Agents; Heavy adds grok.com/Grok app features but not a Cursor plan. The free Cursor Ultra-with-Heavy promo ended end of August. After weekly quota, on-demand needs a saved payment method on cursor.com.
  • Linux RPM links for GrokBot not working - Staff (kevinn, 2026-09-10): download-page RPM links point at an old filename — use direct 0.47.0 x64/arm64 RPMs or the yumrepo + anysphere.asc dnf install path until the page is fixed.
  • Why is Grok Bot usage included in my Cursor Models usage? - Staff (deanrie, 2026-09-10): grok-bot-default/automation do not consume monthly Cursor Models quota — they use Grok Bot’s weekly pool; rows under Cursor Models are a display bug, while Cloud Agents Grok Bot spawns still bill the Cursor plan.
  • SuperGrok on-demand appears to require Cursor Pro - Staff (deanrie, 2026-09-08): don’t buy Cursor Pro for more Grok Bot — Pro and SuperGrok pools don’t stack; keep SuperGrok linked and use on-demand on that same account (add a card) when the weekly grant runs out.
  • Which Grok Bot usage counts against the weekly pool? - Staff (deanrie, 2026-09-07): chats, routines, browser/computer use, shell, sub-agents, MCP, and bot-machine repo work draw the weekly Grok Bot pool (grok-bot-* rows); helper model names without the prefix can still be Grok Bot metering until that pool is exhausted.
  • macOS setup fails with unreachable — Bot name too long - Staff (kevinn, 2026-09-10): “Can’t reach your computer” on first-Bot setup can be a >255-character Name field rejection misreported as connectivity — quit/reopen and create with a short name, then put long instructions in the first chat.
  • Can't reach computer — dual computer copies - Staff (mohitjain, 2026-09-09): unreachable can mean the app points at a half-started computer copy while bots live on another — stop Reset/Update/Recover and wait for backend reconnect so the good copy stays intact.
  • Windows Kaspersky HTTPS scan → ConnectError.Internal / Can’t reach computer - Staff (deanrie, 2026-09-11): Grok Bot trusts public CAs only—Kaspersky Encrypted connections scanning swaps the api2.cursor.sh issuer to Kaspersky Anti-Virus Personal Root Certificate and the app never reaches the Agent Computer (ConnectError.Internal). Turn scanning off or exception Grok Bot; do not Reset/Recover; confirm the cert issuer is Amazon RSA again, then quit/reopen and update past 0.44.0.
  • Server-stored webhook routines: desktop missing POST URL / crsr_ key - Staff (deanrie, 2026-09-11): New Bots keep routines on the server, and the desktop app currently does not fetch webhook POST URL, crsr_ secret, or Authorization—recreate and deep links stay empty; bot cannot emit them. Known issue; temporary wake options are Slack channel message triggers or a schedule (not webhook credentials).
  • Windows in-app update Authenticode fail → install Setup.exe manually - Staff (Colin, 2026-09-11): Windows in-app updater can download then fail Authenticode verification (installer removed; app stays old)—often AV holding the file or a slow check, not a bad signing cert. Workaround: run the signed Setup.exe from Cursor · Download Grok Bot (silent /S OK); Agent Computer needs no Reset. Optional: Measure-Command Get-AuthenticodeSignature on the downloaded installer to help triage.
  • Desktop reconnect re-sync wipes secure-card secrets - Staff (deanrie): After sleep/drop/quit-reopen, desktop re-sync of the secrets list overwrites values saved via the secure in-chat card—Update/Reset/reinstall won’t help. Workaround: store keys in the Bot’s agent folder on the computer (less secure) until fixed.
  • Hung custom MCP remotes: delete via cursor.com/agents - Staff (mohitjain): One hung custom HTTP MCP remote can stall discovery so Plugins→Yours never lists it and Uninstall times out. Self-serve fix: open cursor.com/agents → + → MCP Servers → Delete user config on that remote (works even while discovery hangs).
  • Unreachable from Bot OOM / parallel fan-out - Staff (mohitjain): Recurring unreachable can be Agent Computer OOM when a Bot spins too many parallel processes—not your network. Prevention: worker concurrency 1 on production paths, no mass-resume after rematerialize, batch large fan-outs; avoid Reset while support restores.
  • Authentication error banner → Update Grok Bot’s Computer - Staff (Colin): Persistent “Authentication error / try logging out” can be an outdated Agent Computer build after a backend change—accounts are fine; skip sign-out/reinstall. Fix: Settings → Updates → Update Grok Bot’s Computer, then reopen and send a message.
  • Higgsfield MCP drops until you reconnect before use - Staff (mohitjain): Higgsfield’s sign-in can’t renew itself, so the connector drops after the first session expires—no Grok Bot setting holds it open. Workaround: reconnect Higgsfield right before you need it instead of leaving it connected all day.
  • X connector 402 → top up credits or use Bot browser - Staff (mohitjain): When X plugin search returns 402, top up credits on the X developer app behind the bearer—or skip the API and ask the Bot to use its cloud-computer browser on x.com for accounts you follow.
  • No Chrome extension yet — iOS share sheet / paste URL workarounds - Staff (deanrie): There is no separate Chrome extension for Grok Bot yet. On iOS, share a page/link/selection into Bot via the share sheet; from anywhere, paste a URL into chat so the Bot opens it on its cloud computer to summarize or act.
  • Ubuntu eCryptfs: sand-client ENAMETOOLONG blocks first setup - Staff (Colin, 2026-09-13): Grok Bot stores ~140–200-char files under ~/.config/Grok Bot/sand-client-persistence/; Linux allows 255 but eCryptfs (“Encrypt my home folder”) caps names at 143 → ENAMETOOLONG on Ubuntu first setup. Check with getconf NAME_MAX ~/.config and mount | grep -i ecryptfs; team is shortening names.
  • Secure-card secrets miss running agent shells — spawn a fresh agent - Staff (Colin, 2026-09-13): tokens saved via the secure card land in the Agent Computer’s main environment, but agents already open in their own window started a separate shell session that does not pick up later env changes—card shows Saved while the executor cannot see it. Workaround: after saving, create a brand-new agent (or rely on files on disk, which every agent can read); re-saving into an existing agent does not help.
  • Signature-Agent = Grok Bot computer Chrome, not Cloud Agents - Staff (Colin, 2026-09-13): Signature-Agent / cursorusercontent.com traffic is the browser inside your Grok Bot Agent Computer—not Cloud Agents or the IDE browser. Health-check tabs stay open after the task and keep polling; stop by Open computer → close those Chrome tabs (or quit Chrome), pause/delete the Automations routine, or Reset Grok Bot’s Computer as last resort.
  • Trim a fat Grok Bot chat: Duplicate + handoff file - Staff (kevinn, 2026-09-14): No in-place compact for a Grok Bot chat—auto-summary near the limit still lets busy threads refill. Workaround: ask the Bot to save a handoff file (responsibilities, decisions, active work, refs) → Bot actions → Duplicate (keeps profile/skills/routines/avatar; clears conversation/memory) → have the copy read the handoff → Hide the old Bot. Prefer short pointers over dumping long specialist handoffs into the Chief chat.
  • Private Slack channels need /invite @Cursor for routine triggers - Staff (kevinn, 2026-09-15): Slack-triggered Grok Bot routines never see messages from a private channel unless the Cursor Slack app is a member. Test Run bypasses Slack entirely; Slack plugin replies use a different app than the routine listener—so both can work while the trigger stays silent. Fix: in the private channel run /invite @Cursor, wait ~1 min, post a canary message, then check the routine Run history.
  • Take over shows main desktop — Bot may be on another display (Xvfb) - Staff (deanrie, 2026-09-14): A “blank” Computer viewer can still be connected—Take over renders the Bot machine’s main desktop, while the Bot may have launched apps on a separate display (e.g. Xvfb :1); ask it to open something on the main desktop or align DISPLAY, don’t Reset.
  • Network Debugger when computer is healthy but app can’t connect (Windows) - Staff (Colin, 2026-09-14): If Recover fails but the Agent Computer is healthy server-side, fully quit, reinstall from cursor.com/download/bot (keeps bots/files/logins), then open Settings → General → System → Network Debugger (or “Open Network Debugger” on the trouble-connecting screen); expand Details and check Api tls / Api unary / Computer tls / Updates feed, and name any AV (Kaspersky etc.)—OP fixed it by trusting sites in Kaspersky, without Reset.
  • One bot silent / failed to send — reply runner stuck server-side; do NOT Reset - Staff (deanrie, 2026-09-16): when one Bot fails to send while others and the Agent Computer stay fine, reply processing for that Bot is stuck on Cursor’s side—not your setup; skip Update/Recover/Reset; files and history stay; report last message time + Bot ID if it happens again after a tool call.
  • Server-stored webhook routines: URL/key panel fixed in desktop 0.53.0 - Staff (Colin, 2026-09-16): missing Webhook URL / crsr_ key / Pause-Delete on newer server-stored routines was not a Pro+ plan limit—fixed in Grok Bot desktop 0.53.0; update the app (was 0.51.0) so the routine panel shows credentials again; interim workarounds were schedule or Slack triggers via chat.
  • GitHub “issue assigned” routine never fires on github.com - Staff (deanrie, 2026-09-16): with correct repo access and filters, the GitHub issue-assigned trigger still does not fire for github.com repos (known server-side); filter matches the assigner; no user-facing event log yet; temporary workaround is a scheduled routine (webhook may also be blocked by the 171324 panel bug until 0.53.0).
  • Onboarding provisioning fails — create first Bot on mobile, then Update Computer - Staff (deanrie, 2026-09-16): first-Bot provisioning can fail when the account’s cloud computer is stuck server-side—reinstall/retry won’t fix it; workaround is create the first Bot in the phone app, then on desktop Settings → Updates → Update Grok Bot’s Computer; staff can also recreate the computer.
  • update_state memory writes fail fleet-wide — write memory files directly; don’t Reset - Staff (deanrie, 2026-09-16): update_state target:memory fails fleet-wide with “brain docs snapshot was cut short before completing” while settings updates and direct file edits still work—known server-side; workaround is write facts into memory/profile.md or memory/log/YYYY-MM.md; Update/Reset Computer won’t help.
  • Custom MCP OAuth DCR: cursor:// callback breaks Cloudflare https-only allowlists - Staff (deanrie, 2026-09-16): Dynamic Client Registration sends three redirect_uris—cursor://anysphere.cursor-mcp/oauth/callback, https://www.cursor.com/agents/mcp/oauth/callback, and http://localhost:8787/callback; Grok Bot desktop uses localhost, but Cloudflare Managed OAuth rejects the whole set because it can’t allowlist cursor://—tracked server-side fix to drop non-https callbacks.
  • Windows Ctrl+, Settings shortcut blocks Traditional Chinese full-width comma - Staff (Colin, 2026-09-16): on Windows, Bopomofo/Zhuyin Ctrl+, for full-width 「,」 still triggers Grok Bot’s Settings shortcut—flagged to the team; interim workaround is Shift+Space to full-width (全形) mode then press , alone (no Ctrl), then Shift+Space back to half-width.
  • Routine Edit opens chat by design; webhook panel needs desktop 0.53.0 - Staff (kevinn/Colin, 2026-09-15–16): the routine Edit button now opens a pre-filled Bot chat message by design—ask the Bot in chat to change or create routines; missing Webhook URL/crsr_/Authorization on server-managed routines is the known panel bug fixed in desktop 0.53.0 (same family as 171606/171324).
  • Frozen “sending” after trial usage — check Settings → Usage; don’t Reset - Staff (deanrie, 2026-09-17): Agent Computer was fine—Grok Bot free-trial included usage was exhausted, so every send (including new bots) is rejected before a reply; the app should show “trial usage used” but currently can look frozen on “sending”—confirm in Settings → Usage and do not Reset/Update/Recover or reinstall; bots/files/logins stay safe until usage is available again.
  • Confused over Grok Bot — Cursor vs Bot (staff) - Staff (deanrie, 2026-09-17): Cursor and Grok Bot are different products sharing one account/subscription—Cursor for coding in the editor/cloud agents/CLI; Grok Bot for work outside the editor on its always-on cloud computer. The in-Cursor tip is optional for non-coding first messages; Pro keeps a separate weekly Grok Bot allowance.
  • UI rename fails — ask the Bot to rename itself (staff) - Staff (mohitjain): Grok Bot UI rename often doesn’t stick (tracked bug). Best workaround for now: ask the Bot/agent to rename itself — that sticks. Not a local setup issue.
  • Parent Bot goes quiet after Cloud Agent handoff (staff) - Staff (Colin, 2026-09-17): When a Grok Bot hands work to a Cursor Cloud Agent the parent chat goes quiet until that agent finishes (auto-wakes then)—expected today, not a hang. Watch live status at cursor.com/agents or Cursor desktop, or ask the parent to attach the agent card for Running/Done inline; in-flight visibility in the parent chat is being improved.
  • iOS Settings scroll can flip Auto-review — scroll on the label (staff) - Staff (kevinn, 2026-09-17): On Grok Bot iOS Settings, a scroll that starts on a switch can flip it (reproduced; tracking). The protective control is Auto-review (not labeled “Agent guards”). Workaround until fixed: start the scroll on the row text, not on the switch itself.
  • 172033 Sidebar sections: desktop New Section + no agent create tool - Staff (kevinn): agents can list sections and CreateAgent can place into one, but there is no tool to create/rename/delete/move sections — on desktop right-click Move to → New Section (mobile long-press).
  • iOS 1.11.1+ Voice icon is a gradual account rollout (staff) - Staff (kevinn, 2026-09-18): Missing voice/call icon on Grok Bot iOS 1.11.1 is not a device bug—Voice chat is rolling out gradually to accounts on 1.11.1+; reinstall/sign-out will not speed it up. Desktop Voice stays available; phone composer dictation mic still works until the button appears.
  • No delete/redact of sent messages — use secure input for secrets (staff) - Staff (kevinn, 2026-09-17): Grok Bot cannot delete or redact a sent message (only failed-to-send messages have Delete)—rotate any pasted secret on the provider. Prefer asking the bot to request the credential: it shows a masked secure input card, stores the value as a bot secret, and keeps it out of the transcript and model context.

Related Lists

Contributing

1675 curated entries across 8 sections. Please read CONTRIBUTING.md before opening a PR: the resource must be about Grok Bot the cloud-computer teammate, the link must work, and the blurb is one sentence ending with a period.


Unofficial community list. Not affiliated with xAI/SpaceXAI or Cursor. List content CC0 1.0.

About

Curated bilingual list of Grok Bot resources — always-on AI teammates with their own cloud computer.

Topics

Resources

Contributing

Stars

331 stars

Watchers

1 watching

Forks

Releases

Packages

Contributors

Languages