@bot not replying on X? Where tagging works, what each reply means, and how to fix a quiet Grok Bot (unofficial guide)

The short answer

When @bot stays silent, the request never reached your Bot, so there's nothing to wait for. Check in this order: your X account's region, then the post itself (no video or GIF, no @grok, and @bot tagged by you), then your setup (X connected on grok.com, Grok Bot on the same Grok account, at least one Bot of your own), then your weekly usage.

When @bot does reply, read the reply. It tells you whether your Bot has the task or what's missing.

This guide is independent and unofficial. It isn't affiliated with or endorsed by xAI, Grok, X, or Cursor. Availability changes, so check the linked docs for the current list.

Where tagging @bot works (and why a VPN won't help)

The docs say tagging @bot works for X accounts based in most countries. It isn't available yet for accounts based in Australia, the United Kingdom, the European Union, Iceland, Liechtenstein, or Norway.

@bot goes by the country X has on record for your account, not where you are. Your current location and any VPN make no difference.

If X lists only a broader region for your account, such as "South Asia", or no country at all, tagging isn't available yet either. In every one of these cases @bot doesn't reply.

If you're in one of these places, you can still use Grok Bot itself. Paste the post link into a chat with your Bot in the desktop or phone app and ask for the same thing. Bots can read public X posts without you connecting an account.

Other reasons @bot stays quiet

You replied in a thread that already includes @bot, but didn't tag @bot yourself. Add @bot to your own reply.

Your post also tags @grok. Tag only @bot when you want your Bot to do the work.

Your post, the post it replies to, or a quoted post has a video or GIF. Your Bot receives still photos, but not videos or GIFs. Reply to a text or photo post instead, or paste the link into the app.

The post doesn't pass internal moderation.

Grok Bot isn't linked to your Grok account, or your weekly usage is used up. Check Usage & Billing in Settings.

What @bot's reply means

A short line saying it sent your request to your Grok Bot: your main Bot has the task. Open Grok Bot to follow the work. The results stay in that Bot's conversation in the app, and @bot only posts the confirmation on X.

"Sign up for Grok Bot: https://x.ai/bot": no Grok account is connected to the X account you posted from. On grok.com, open Settings → Account and choose Connect next to 𝕏 Account, set up Grok Bot, then tag @bot again.

"Grok Bot isn't set up yet. Open https://x.ai/bot": your accounts are connected, but you don't have a Bot of your own yet. Open Grok Bot, create a Bot, and tag again. Bots someone shared with you can't take tagged requests.

The setup @bot needs

A Grok account with your X account connected (grok.com → Settings → Account → Connect next to 𝕏 Account).

Grok Bot access on that same Grok account. If your access comes from a SuperGrok subscription, link it: on desktop, Settings → Usage & Billing offers Get Access with Grok, and on iPhone and Android the access screen offers Link Grok Account.

At least one Bot of your own. Your main Bot is the one that receives tagged posts.

The X for Grok Bot plugin is optional. @bot forwards requests with or without it. Add it from Connect apps only if you want your Bot to read your timeline, mentions, bookmarks, or DMs.

The first time a tagged request goes through, X notifies you that tagged requests start work automatically and use your Grok Bot usage. Keep that in mind before tagging @bot on lots of posts.

If your Bot goes quiet inside the app

This is a different problem from @bot on X. The official troubleshooting page says to start with the least destructive step, because cloud work can keep going while the app is disconnected.

Look for something waiting on you first: a question, an approval card, a login, a CAPTCHA, or a secret request. Open the computer view to see whether the Bot is stuck on a page. Send a short redirect if it's on the wrong track, or "Stop now" to end the work.

If the computer can't be reached, try in order: Retry or reopen the chat, restart the app, choose Recover computer when it's offered, then Settings → Computer → Update Bot's Computer. Recover and Update keep your files and logins. Reset restores the last saved snapshot and can lose recent work, so use it last.

If you've hit your usage or an on-demand spending limit, the app shows a limit notice. Review it under Usage & Billing.

If a routine didn't run, check that it's enabled, the schedule and time zone are right, the owning Bot still exists, and its connected apps are still signed in. Then look at the run history.