Cursor Grok 4.6 Not Working


Where does the bug appear (feature/product)?

  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)

Describe the Bug

Grok 4.6 fails on every prompt. Instead of a model response, Cursor returns a provider error containing Cloudflare HTML: “Sorry, you have been blocked” / “You are unable to access x.ai”.

Other models work normally. Only Grok 4.6 is affected.

Steps to Reproduce

  1. Open Cursor (Pro+ account).
  2. Select Grok 4.6 in the model picker.
  3. Send any prompt in Chat/Agent (short or long, new or existing thread).
  4. Observe the error on every attempt.

Expected Behavior

Grok 4.6 should return a normal AI response like other supported models.

Screenshots / Screen Recordings

(Attach screenshot of the Cloudflare error if you have one.)

Error text includes:

  • Cloudflare Ray ID: a3498cabbd0a17b8
  • Blocked IP shown: 52.44.113.131 (AWS)

Operating System

  • Windows 10/11

Version Information

IDE: (fill from Menu → About Cursor → Copy)

Version: [paste from About Cursor]
VSCode Version: [paste from About Cursor]
Commit: [paste from About Cursor]

For AI issues: which model did you use?

Grok 4.6

For AI issues: add Request ID with privacy disabled

Request ID: 522f2b3b-40ef-44a3-adee-9fa338b37054

Additional Information

  • Plan: Pro+
  • Failure rate: 100% of Grok 4.6 prompts
  • Error appears to be a Cloudflare WAF block on x.ai, not a local/network issue
  • Blocked IP (52.44.113.131) looks like Cursor provider egress (AWS), not my home IP
  • Suggests a routing/allowlist issue on Cursor ↔ x.ai, not user configuration

Does this stop you from using Cursor?

  • Sometimes - I can sometimes use Cursor (other models work; Grok 4.6 is unusable)

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.


Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!


Expected Behavior
What is meant to happen here that isn’t working correctly?


Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)


Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)


For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…


Additional Information
Add any other context about the problem here.


Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

Hey @V111
This isn’t an x.ai block, and your account is fine. The failing requests are going out under a personal API key that’s enabled in your settings, and Grok 4.6 is one of Cursor’s own hosted models, so it can’t run on a personal key. That’s also why Auto and your other models keep working.

Fix: in Cursor Settings → Models, turn off any enabled personal key - check Use Azure OpenAI, Use OpenAI API Key, and Override OpenAI Base URL - then start a new chat with Grok 4.6.

Let me know if it still fails!

That worked!! Thank you so much Mohit!!