PulseAugur
实时 03:40:17
English(EN) SuperGrok Heavy + Grok Bot: matching .ru email gets policy_denied, support loop since Aug 16

Cursor用户报告Grok Bot访问.ru邮箱地址出现问题

一位用户在使用Cursor访问Grok Bot时遇到问题,尽管他已付费购买了声称包含此访问权限的SuperGrok Heavy。问题似乎源于用户的.ru电子邮件地址,该地址似乎被一项未发布的政策阻止,导致无法将其xAI身份与其Cursor账户关联。Cursor和xAI的支持都未能提供有效帮助,Cursor支持关闭了工单,而xAI则将用户转回Cursor。 AI

影响 使用非美国邮箱域名访问集成AI工具的用户可能会遇到潜在的阻碍。

排序理由 用户报告的产品集成特定问题。

在 r/cursor 阅读 →

AI 生成摘要 · Google Gemini · 来自 1 个来源。 我们如何撰写摘要 →

Cursor用户报告Grok Bot访问.ru邮箱地址出现问题

本文如何被排名

Signal score
0 / 100
Composite score across the factors below. Higher = stronger signal that this story matters right now.
Newsworthiness bucket
Tool
用户报告的产品集成特定问题。
Source corroboration
Single-source cluster
Only one publisher covered this so far. Single-source stories can still rank when the publisher is high-authority, but they lack cross-source corroboration.
Topics
product, other
Editorial topic classification. Feeds into how the story surfaces on /topic/<slug> hub pages and into the per-entity coverage mix.
AI-industry relevance
High
Clearly on-topic for AI-industry coverage.
Story freshness
1 days old
Coverage has settled into its steady-state source set.

完整方法见我们的编辑标准

报道来源 [1]

  1. r/cursor TIER_2 English(EN) · /u/coolak-fantom ·

    SuperGrok Heavy + Grok Bot:匹配.ru邮箱被policy_denied,自8月16日起陷入支持循环

    <!-- SC_OFF --><div class="md"><p>I’m posting because I still cannot get a substantive technical answer from either company, and I want to know whether other users can reproduce this.</p> <p>**What happens**</p> <p>- I pay for SuperGrok Heavy through my X/xAI identity.</p> <p>- x…