Check your Cloud Agents default before Grok Bot launches agents

What's new (Grok Bot/Cursor portion for the issue)#

No new Grok Bot version is on the changelog (still 0.70.2 from Oct 11), no new Cursor release, and Cursor's status page is All Systems Operational this morning. (confirmed)

Agents your Bot launches can inherit Grok 4.7 Fast (confirmed, staff)#

What happened (one user's report, plus staff steps): A Premium user reported at 1:07 AM ET that Cloud Agents seemed stuck on Grok Fast. At 3:45 AM ET, Cursor staff member deanrie found the account's Cloud Agents default "is saved as Grok 4.7 with Fast turned on," and "All Cloud Agents that ran today, mostly through Grok Bot, picked up that default and ran as Grok 4.7 High Fast." Grok 4.7's default variant is High Fast, and "Fast is an option inside the model itself."

Who could be affected: staff confirmed it for that one account. It could apply to Cursor users on plans with Cloud Agents and Fast mode (Premium and up, per the docs) who let Grok Bot launch agents. Beyond the weekly pool, Grok 4.7 Fast is $4, $1 and $12 per million input, cache-read and output tokens against $2, $0.5 and $6 for Grok 4.7.

What to do now: on cursor.com/dashboard, open Cloud Agents, hover over Grok 4.7 High Fast in the Default Model dropdown, turn Fast off, keep Effort on High, reload, and check it reads Grok 4.7 High. When you ask your Bot for an agent, deanrie suggests saying "use Grok 4.7 High with Fast off".

What to watch: a visible non-Fast entry in the picker. Separately, the automations page now shows your saved variant; deanrie said "The change has already been rolled out on cursor.com".

Grok BotHow people are using it#

• A Grok Bot 101 video from a voice clone. Texas Twins Dad posted at 9:53 PM ET Oct 16 that he "Made a Grok Voice clone of me," gave it his script, dropped the clip into Grok Bot, and "Grok Bot made the video with captions and animated visuals." (reported, one user)
• Health data by email. Ragnar Heil said at 3:32 AM ET he sends his RingConn 3 wearable data "directly to my #GrokBot email address" and gets back "a dashboard and recommendations." Bots got their own email addresses in v0.70.2. (reported, one user)
• A phone front desk. @faiAI0 described at 11:38 PM ET Oct 16 a phone line on Telnyx where Grok Voice answers as a receptionist and Grok Bot "handles callbacks, outbound calls, encrypted logs and daily backups, and texts me friendly summaries," with scam checks such as "Money or emergency means hang up and call a known number." (reported, one user, small account)

Grok BotThe digest#

Grok Bot#

• Local tools still say "Never" for some new X Premium users. Follow-up to yesterday's item. Overnight, a new X Premium subscriber reported at 1:57 AM ET the same error on 2 Macs, adding "I only use Cursor through Grok Bot via the X Premium bundle," so an account mix-up doesn't fit their case. Another Mac user said at 2:48 AM ET it "persists after a complete local cleanup, reinstall/sign-in, a new machine ID, updating to 0.71.2, and re-granting macOS Full Disk Access." No new staff reply since kevinn's note that it's tracked and "the bot can still work on its own cloud computer." (confirmed issue; new reports are user reports)
• A Mac that shows up as a new machine breaks routines tied to it. jsolly reported at 9:05 PM ET Oct 16 that their Mac "now shows up as a new machine" after what they think was an auto-update, though "I did not reinstall the app," and a routine that runs on that Mac by machine ID failed both runs. No staff reply. Our read: if a routine runs on your own computer, check Settings, Computer for a duplicate entry. (reported, one user)
• Voice calls: "logged it," then nothing. Yvonne Lee wrote at 7:02 PM ET Oct 16 that on voice calls her Bots "would say "logged it" or "noted" and then seem to not do it." Her fix: "nothing counts as done until it's written down, every call gets summarised in chat, and dates are worked out from stored facts and not guessed." (reported, one user, no staff reply)
• Voice call speed. The Oct 11 changelog says "voice calls offer 0.5x speed," and since Sep 29 a Bot keeps "the voice, speed, and language you set for it." (confirmed, changelog)
• Blank panes when switching Bots, still on Windows. Parag_Chhibber said at 7:23 PM ET Oct 16 the glitch is "still present for me on Windows 11 26H2 using GrokBot 0.71.2," and "Turning hardware acceleration on did not seem to make a difference." Keeping it on was staff's Oct 10 advice, which we ran in our Oct 11 issue. (reported, one user)
• X Subscription limits: no staff answer yet. In the X Subscription thread, a Teams user said at 4:43 AM ET that after moving to Super, "my limits on GrokBot are exactly the same" as on old Premium, though "it has only been a day since the shift." Another user asked Colin for the weekly limit by tier. Cursor hasn't answered. (user claims)

Cursor#

• Team plan checkout blocked. deanrie said at 4:22 AM ET that the team-plan checkout error isn't caused by their browser or network, so incognito and ad blockers won't help; it's tracked with no date. Keep using an existing support ticket rather than opening a new one. (confirmed, staff; tracked)
• Parent .cursorignore files block agent file tools. deanrie confirmed at 4:25 AM ET that "Agent file tools apply .cursorignore from parent folders even when Hierarchical Cursor Ignore is turned off." A * pattern in a parent folder blocks any nested workspace. Workaround: rename the parent .cursorignore files and leave them that way until a fix. (confirmed, staff)
• Python remote debugging hangs after a restart. deanrie reproduced it at 5:35 AM ET: with "restart": true in a debugpy listen config, Cursor doesn't enter the paused state on a restarted session, "so this is on our side." "It started with the 3.23.12 build." Workaround: remove "restart": true and press F5 after each worker restart, or attach instead. A fix is proposed. (confirmed, staff)
• Windows hooks: use python.exe, not pythonw.exe. deanrie explained at 4:59 AM ET why a slow beforeSubmitPrompt block was ignored: Windows doesn't wait for GUI programs like pythonw.exe. "With python.exe, the hook runs as a console process," so responses before the timeout count. (confirmed, staff)
• One user's report: a CLI session that used about 318M tokens. M_Y reported at 8:48 PM ET Oct 16 that a read-only investigation "appears to have triggered unintended recursive agent execution, resulting in approximately 318 million tokens of usage within 33 minutes," and their allowance "dropped from 63% to 40%." Their theory is that the CLI read an agent automations list command as a prompt. No staff reply yet, and we haven't confirmed the number. (reported, one user)