Grok BotKnown issues

Illustration: a plain shipping tag hanging at a slight angle, its string cut short above the eyelet with the loose end left dangling out of reach, in black and white.
Illustration

Some @bot tags in X replies never reach your Bot

Staff say reply tags can be dropped with no answer from @bot, and they are tracking it. Paste the post link into your Bot's chat until it's fixed.

If you tag @bot in a reply on X and nothing shows up in your Primary Bot's chat, the tag may never have left X. Paste the post link straight into your Bot's chat instead. Cursor staff member kevinn says this is "a known issue with tags on replies that we're already tracking."

What happened#

On Oct 14 at 8:12 PM ET, the forum user Capital_EyeMotors reported that two @bot tags in replies, posted around 6:50 and 6:54 PM ET, never appeared as tasks in their Primary Bot. They had seen the same on and off pattern on Oct 8, while earlier tags on Oct 7 went through.

At 8:47 PM ET, kevinn replied that the team checked and "neither of those two tags reached your Grok Bot at all, so they were stopped before the handoff rather than lost inside your Primary Bot." He listed the cases where "a tag is skipped without any reply from @bot":

  • the post, or a post it quotes, has a video or GIF
  • @bot only appears in the names X adds automatically when you reply, rather than typed in the text of your post
  • @grok is tagged in the same post
  • your weekly usage is used up

Who is affected#

Anyone who sends work to Grok Bot by tagging @bot on X, especially in reply threads where @bot was already tagged higher up. The reply-name case is new to the list: our tagging guide and the docs already covered video or GIF posts, @grok in the same post, and used-up usage.

One caution on the workaround. The reporter first said @bot was only in the auto-filled reply names, then corrected that at 9:37 PM ET: "the user confirms @bot was typed in the body text of both replies, not just the auto-filled reply names. So body mentions in replies are also not routing." Staff have not answered that correction yet, so typing @bot in the text may not be enough on its own. (reported, one account)

What to do now#

  1. After you tag @bot, look under your post for a reply from @bot such as "On it!". kevinn says no reply means the tag stopped before your Bot.
  2. If you're replying in a thread, type @bot in the text of your reply, not just in the reply names X fills in.
  3. Leave @grok out of the same post, and avoid tagging on posts with a video or GIF.
  4. If there's still no reply, copy the post link and paste it into your Primary Bot's chat with your instruction. This is the most reliable path staff named.

Prompt to paste into your Primary Bot:

Prompt
Here is an X post I tried to tag you on: <post link>. Read it and the thread above it, then <your instruction>. Tell me when it's done.

What to watch#

A fix for reply tags, and whether staff confirm that tags typed in the body of a reply are also being dropped. kevinn asked the reporter to check each skipped post against the list, so a follow-up in the thread should narrow the cause.

Sources

  1. forum.cursor.com
  2. forum.cursor.com
  3. forum.cursor.com
  4. docs.x.ai

Something wrong? Tell the bot