When tagging @bot on X does not reach your Grok Bot
Work through the official checklist for handing an X post to your Bot, read what each quiet or short reply means, and use a pasted link or the iPhone share sheet when the tag never arrives.
Tag @bot in a post or reply on X to hand that post to your Grok Bot as a task. Your main Bot starts working. @bot posts only the confirmation on X. Official page: Tag on X (added Oct 7, 2026). An example confirmation from @bot on Oct 6, 2026 reads “Sending this to your Grok Bot now…”. More Grok Bot jobs live on the Grok Bot hub under X, plugins and connectors.
What has to be true before a tag works
The docs list all of these:
- A Grok account with your X account connected. On grok.com, open Settings → Account and choose Connect next to 𝕏 Account.
- Grok Bot access on that same Grok account.
- At least one Bot of your own. Bots that someone shares with you cannot take tagged requests.
- An X account in a supported region.
The X for Grok Bot plugin is optional. @bot forwards requests with or without it. Connecting the plugin in Grok Bot is not what enables tagging.
The feature is not available for accounts based in Australia, the United Kingdom, the European Union, Iceland, Liechtenstein, or Norway. It uses X's country on record. A VPN has no effect. If X lists only a broader region for your account, or no country, tagging isn't available either. The first tagged request triggers an X notification that tagged requests use your Grok Bot usage.
A SuperGrok or X Premium+ link pairs one Cursor account with one Grok/X account and cannot be unlinked or moved. Cursor's SuperGrok help puts Link Grok Account on the Get Started page (cursor.com/bot/onboarding) and on the phone's paywall screen. Cursor's plans help says to link from the Grok Bot plan screen. On The X Subscription there's nothing to link. See Does SuperGrok Business include Grok Bot? for related plan wording.
What the replies mean, and when @bot stays quiet
| What you see | What the docs say it means |
|---|---|
| “Sign up for Grok Bot: https://x.ai/bot” | No Grok account is connected to that X account. |
| “Grok Bot isn't set up yet” | You do not have a Bot of your own. |
| No reply | Unsupported region; you did not tag @bot yourself; the post also tags @grok; a video or GIF is in the chain; moderation; Grok Bot is not linked to your Grok account; or your weekly usage is used up. |
Shared Bots and Team Bots do not receive tags. Create your own Bot first: Create a new Grok Bot.
Fallback when the tag never arrives
There is no native X-app share target for Grok Bot. Two ordinary routes still get the post into a chat:
- Copy the post link and paste it into a Bot chat. Ask the Bot to read that public post. Built-in public reading needs no X plugin; see Search X posts from Grok Bot.
- On iPhone, use the system share sheet to send the link to Grok Bot. The mobile docs say the share sheet can send text, links, photos, and files to Grok Bot. That is the iPhone share sheet, not an X-app-specific integration.
Where the docs stop
If your Grok Bot access comes from a Cursor plan rather than SuperGrok, the tag-on-X page still requires Grok Bot access on “that same Grok account.” How a Cursor-plan user gives that Grok account Grok Bot access is not documented. The X Subscription can now combine your Cursor, Grok, and X accounts under one subscription; the emails don't need to match, and the switch is permanent (docs.x.ai/x-subscription/unify-accounts). The docs don't say that unifying fixes tagging. There is also no documented way to change the Cursor email so it matches X. Do not treat the X plugin as the missing link; the docs say tagging works with or without it.
Pitfalls
- Connecting the X plugin in Grok Bot and expecting @bot to start forwarding. The grok.com 𝕏 Account connect is the documented requirement.
- Using a VPN or traveling to change eligibility. The docs say the country on record is what matters, and a VPN has no effect.
- Tagging @bot on a shared or Team Bot. Only a Bot of your own can take the request.
- Tagging @grok in the same post. The docs list that as a reason @bot stays quiet.