Grok refuses to submit code unless its on cursoor cloud?

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

what is this about? I have grok signed into my claude cli an dmy codex cli…been sneding jobs around as needed for certain tasks for a month..but now today:

It’s a workflow restriction, not a technical problem: repository edits must go through Cursor cloud agents. Claude CLI works on my computer, but I can’t use it for those edits. My earlier successful test was inconsistent with that restriction—not proof of an exemption.

Steps to Reproduce

install and log into claude cli on the bots computer and aks it to modify your website usuign claude code..it refuses saing its a workflow proplme, but wont’ fix it or provide any possible solutins bvesides forcin to go through cursor cloud.

Expected Behavior

expect it to listen to me and do what i told it to instead of flat our refusals to use a tool that it uses no problem regularly.

Operating System

Windows 10/11

Version Information

Version: 0.79.2
Built: 2026-11-05T07:54:25.505Z
Release Track: stable
OS: win32

For AI issues: which model did you use?

any.

Does this stop you from using Cursor

Yes - Cursor is unusable

5

I have the same issue - I want to request a refund

6

Same here!

7

Same here

8

Same here

10

Hey everyone - this is how Grok Bot is set up to work right now, not something broken on your end: by default it routes repository edits through a Cursor cloud agent rather than working locally.

To get a local change, ask for it explicitly in the same message, e.g. “I’m explicitly asking you to clone the repo onto your computer and make this change with the Claude CLI there - don’t use a cloud agent.” You’ll need to say it each time (there’s no standing setting for it yet), and it won’t apply to scheduled runs.

11

Grok Bot refuses to edit local code directly and requires Cursor instead

Despite an explicit request to edit code locally, Grok Bot launched Cursor without first confirming consent to use it and consume its usage allowance.

The bot claims it cannot modify repository code directly. However, it reported no file-write error, permission issue, or other technical failure. This appears to be a workflow restriction rather than an inability to edit local files.

Please clarify why direct local editing is blocked and whether it can be used without Cursor.

Related report: Other users describing the same issue.

12

Just want to add here, I posted this yesterday and Cursor’s bot immediately routed it to the black hole of the “Accounts” section.

This is messed up. I did not sign up for Cursor, do not want my stuff going to Cursor cloud (whatever that is), and do not want to grant even more access to even more tools now.

No notifications, no warning, just a switch and “yeah, that’s how it works now”. Seriously nutty.

14

What has changed since the beginning of November that now causes Grok to refuse to write code for me and forces me to use Cursor instead?

15

At lease a couple free usage resets. I used at least 30% of my allowance trying to convince grok to do what it used to do no problem.

16

If I’m forced to use Cursor, I don’t see the point of having Grok Bot. For me, Grok Bot was great because I could just input a task and it would handle everything on its own; now, I have to break things down across additional Cursor instances and pass tasks back and forth which just means burning extra tokens for the exact same work. I don’t see the sense in working this way.

17

Same here, and I hit the cursor limit and now I simply CANNOT edit code via grok bot. My god, that’s absurd. It broke my entire workflow.

18

I have my repo on my own computer, not even on Grok Bot’s and it still refuses to use the Claude CLI on my computer to make changes. Even when I have explicitly asked it to do so. Is there any word on a fix for this?

19

It is absolute disaster, at first they got us in grok bot because 200$ subscription limits are gone fast, and grok bot limits were independable and good, and now when grok bot can’t code we limited to cursor usage limits again. For 200$ that token limits of cursor are not enough even for 2 weeks of normal programmers use.
It is awful, please revert it and allow grok bot to code as soon as possible!!!

20

The plan is to stay that way? What’s the point to get worst then better???

24

exactly same issue. just start from few hours ago. They denied me using claude or codex CLI. forcing me to use cursor web service to use those claude or codex model

25

When are y’all going to fix this? And if this will be the new behavior going forward I want a refund and my account closed and deleted.

27

Agree. this arrangement sucks. Anyone knows how to fix this? I want them to use back CLI

28

Very disappointed with this sudden change to Grok Bot. Please reconsider before making it permanent.

One of the biggest reasons I started using Grok Bot was its ability to act as a true AI operations platform, including directly running Claude Code CLI to build, modify, and manage my software projects.

Until recently, this was working perfectly. I could delegate development tasks to my AI agents, and they could execute them using Claude Code without forcing everything through Cursor.

Now, suddenly, I’m being told:

“The coding workflow available to me in this chat now requires repository changes to go through Cursor rather than launching Claude Code directly, as I did last week.”

This is a major step backward.

The whole appeal of Grok Bot is the freedom to build autonomous AI workflows using the tools we choose. Claude Code, Codex, Cursor, and other development tools should be options, not restrictions.

I don’t want another AI platform that forces me into a single coding ecosystem. I want an AI agent that can orchestrate the best tools for the job.

If Grok Bot removes the ability to directly execute external coding CLIs, it risks losing one of the very things that makes it different from every other AI assistant.

Please don’t turn Grok Bot into just another locked-down AI coding platform.

Let users choose their tools. Let agents execute real workflows. Preserve the flexibility that attracted us in the first place.

I genuinely want Grok Bot to succeed. I’ve already invested considerable time building my agents, development workflows, and business operations around it.

I’m raising this publicly because I hope this is a temporary regression, not a permanent product decision.

To the Grok Bot/Cursor team: please clarify whether this is an intentional policy change, and if it is, reconsider it.

If other users are experiencing the same restriction, please share your experience so the team understands how important this capability is.

Don’t take away the flexibility that makes Grok Bot powerful.

29

I just canceled my subscription.