# Grok Bot refuses all dev operations in its cloud computer — forces Cursor Cloud Agent, gives no reason **URL:** \ **Category:** Bug Reports\ **Tags:** cloud-agents, grok-bot\ **Created:** [November 9, 2026, 8:03pm UTC](https://forum.cursor.com/t/grok-bot-refuses-all-dev-operations-in-its-cloud-computer-forces-cursor-cloud-agent-gives-no-reason/177867 "2026-11-09T20:03:45Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![matrees](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/matrees/32/125695_2.png) [@matrees](https://forum.cursor.com/u/matrees)\ **Post date:** [November 9, 2026, 8:03pm UTC](https://forum.cursor.com/t/grok-bot-refuses-all-dev-operations-in-its-cloud-computer-forces-cursor-cloud-agent-gives-no-reason/177867/1 "2026-11-09T20:03:45Z")
### Where does the bug appear (feature/product)? Grok Bot ### Describe the Bug Since around Nov 8, my Grok Bot has stopped performing any development work directly inside its own cloud computer. It will not: edit/modify code in the repo on its VM run git commits or any repo operations do any development task locally on its computer Instead, it insists on launching a Cursor Cloud Agent to do the work. If I deny/block the use of Cursor Cloud, the bot simply says it “cannot work” and provides no explanation or reason at all. This is a major regression for me: I’m a legacy Cursor Ultra subscriber who previously used Grok Bot to code directly in its cloud computer without consuming Cursor quota. The forced Cloud Agent handoff wastes tokens/time and loses context in the handoff. Please clarify: Is this an intentional change or a bug? Do personal accounts have any opt-out / setting to restore “Grok Bot coding directly in its cloud computer”? Why does it refuse with no reason when Cursor Cloud is disallowed? Hoping for an official response. Thanks. ### Steps to Reproduce Open a code repository inside Grok Bot’s cloud computer (ensure the repo is accessible on its VM). Ask Grok Bot to perform a development task, e.g. “edit this function in file X”, “commit the current changes to git”, or “create a new function in the repo”. Observe: instead of executing directly in its cloud computer’s terminal/editor, the bot tries to launch a Cursor Cloud Agent to do the work. When you deny/block the use of Cursor Cloud Agent, the bot replies “I cannot work / I can’t proceed” with no explanation or reason given. ### Expected Behavior Grok Bot should be able to perform development operations directly inside its own cloud computer (VM) — editing code, running git commits, operating the repo, etc. — without being forced to route through a Cursor Cloud Agent, as it did before ~Nov 8. And when it genuinely cannot perform a task, it should state a clear reason rather than refusing without explanation. ### Screenshots / Screen Recordings ![ScreenShot_2026-11-10_040150_594@2x.png](https://us1.discourse-cdn.com/cursor1/original/3X/0/9/095f94f4d42adafb53e3307accc41db2dbe4b6ad.png) ### Operating System MacOS ### Version Information grokbot 0.79.3 ### For AI issues: add Request ID with privacy disabled Request ID: cb6bf813-5a3b-4f8b-a16a-5e4e5ef59fe9 ### Does this stop you from using Cursor No - Cursor works, but with this issue ---
**Author:** ![Sui\_Feng](https://avatars.discourse-cdn.com/v4/letter/s/b487fb/32.png) [@Sui\_Feng](https://forum.cursor.com/u/Sui_Feng)\ **Post date:** [November 9, 2026, 8:32pm UTC](https://forum.cursor.com/t/grok-bot-refuses-all-dev-operations-in-its-cloud-computer-forces-cursor-cloud-agent-gives-no-reason/177867/5 "2026-11-09T20:32:35Z")
我的机器人也拒绝工作，无法读取我电脑的目录，50美元额度大概用了5分钟就消耗殆尽 ---
**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\ **Post date:** [November 10, 2026, 9:59am UTC](https://forum.cursor.com/t/grok-bot-refuses-all-dev-operations-in-its-cloud-computer-forces-cursor-cloud-agent-gives-no-reason/177867/7 "2026-11-10T09:59:27Z")
Hey @matrees! Handing repo work to a Cursor cloud agent is Grok Bot’s intended default right now, but refusing outright when you explicitly ask it to work on its own computer (with no reason) isn’t. Others have hit this since around Nov 6 and it’s an issue we’re tracking. As a stopgap, ask for the local work explicitly in the same message with a reason, e.g. “Make this change directly in the repo on your own computer, since it depends on files only there, and don’t use a cloud agent.” It doesn’t land reliably for everyone yet. There’s no opt-out setting for the handoff today, though it’s a request we’ve seen from others. Merging this into the main thread so updates stay in one place: [Grok refuses to submit code unless it’s on Cursor cloud?](https://forum.cursor.com/t/grok-refuses-to-submit-code-unless-its-on-cursoor-cloud/177437) ---
**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\ **Post date:** [November 10, 2026, 9:59am UTC](https://forum.cursor.com/t/grok-bot-refuses-all-dev-operations-in-its-cloud-computer-forces-cursor-cloud-agent-gives-no-reason/177867/8 "2026-11-10T09:59:56Z")
Split this topic on November 10, 2026, 9:59am UTC A post was merged into an existing topic: [Grok refuses to submit code unless its on cursoor cloud?](https://forum.cursor.com/t/grok-refuses-to-submit-code-unless-its-on-cursoor-cloud/177437) ---
**Author:** ![matrees](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/matrees/32/125695_2.png) [@matrees](https://forum.cursor.com/u/matrees)\ **Post date:** [November 10, 2026, 1:32pm UTC](https://forum.cursor.com/t/grok-bot-refuses-all-dev-operations-in-its-cloud-computer-forces-cursor-cloud-agent-gives-no-reason/177867/9 "2026-11-10T13:32:36Z")
Thanks, @mohitjain — this stopgap worked for me. 🙏 For anyone else who lands here with the same symptom (Grok Bot refusing to do dev work on its own computer and silently forcing everything through a Cursor Cloud Agent, with no reason given): here’s the resolution and a reusable pattern. **What was happening** :​ As Mohit explained, handing repo work to a Cursor Cloud Agent is currently Grok Bot’s _intended_ default — but the bot outright refusing when you explicitly ask it to work on its own computer, with no reason, is a bug they’ve been tracking since around Nov 6. In my case I’d been asking the bot to develop while also instructing it not to use Cursor, which fed straight into that buggy refusal path. **The fix that worked (verbatim from the team’s stopgap**):​ Ask for the local work **explicitly, in the same message, with a reason** , and tell it not to use a cloud agent, e.g.: > “Make this change directly in the repo on your own computer, since it depends on files only there, and don’t use a cloud agent.” Two things that mattered for me: 1. The instruction has to be in the **same message** as the task (not just a standing rule buried somewhere). 2. You must give a **reason** (“since it depends on files only there”). Without the reason it didn’t stick. **Caveats (straight from the team**):​ - This stopgap “doesn’t land reliably for everyone yet.” - There’s **no opt-out setting** for the cloud-agent handoff today, though they’ve seen that request from others. So if you’re hitting this: don’t assume you misconfigured something — it’s a known issue. Try the explicit-with-reason prompt above, and hopefully a proper fix or an opt-out follows. Thanks again to the team for tracking it and merging into the main thread.