Get your Grok Bot its own email address
Claim one address at mail.grokbot.com, see who can write to it, and set a routine so a Bot only acts on the mail you want.
@bot announced on Oct 9, 2026 that Grok Bot now has its own email, and that a Bot can use it to sign up for services, contact businesses for you, or schedule time with someone. Cursor's help page is Give your Bot an email address. @bot said it is rolling out to users starting Oct 9, 2026, so it may not be on your account yet. The Oct 11, 2026 changelog (v0.70.2) added Bot email addresses. docs.x.ai has no dedicated email page as of Oct 19, 2026; its Teams page covers only the admin switch. More Grok Bot jobs live on the Grok Bot hub under X, plugins and connectors.
Claim the address
You can have one address. You cannot rename it or delete it. Addresses are never reissued. Even if the account that claimed it is deleted, the name is never given out again. The address belongs to you, not to one Bot. All of your Bots can use it in your own chats with them, and in routines you set up. Bots cannot use your address in Slack threads or in chats where someone else is talking to the Bot. A Team Bot does not have a shared team address.
- In chat, ask something like “Get yourself an email address.” The Bot asks what name you want, checks that it's free, and shows an approval card. Nothing is claimed until you approve.
- Or use the Email app. On desktop, open Connect apps in the sidebar and choose Email. On the phone, Cursor's email help says Settings > Connect apps > Email, while Cursor's Connect apps help says to tap your avatar at the top left and select Connect apps. Under Email address, type a name in Choose a name, then choose Create address. The app then shows your address with a copy button.
- Or tag @bot in a post on X and ask it to claim one. @bot passes the request to your main Bot. Tagging needs a Grok account with your X account connected and a Bot of your own, and doesn't work for X accounts based in Australia, the UK, the EU, Iceland, Liechtenstein or Norway. If X lists only a broader region for your account, or no country, tagging isn't available either. See When tagging @bot on X does not reach your Grok Bot.
Name rules: use lowercase letters, digits, dots, hyphens, and underscores. Start and end with a letter or digit. Use at most 64 characters. Reserved words include support, admin, billing, security, help, info, team, cursor, grok, and xai. Help lists those as examples (“such as”), so other reserved names may exist too.
If claiming fails, match the message you see:
| What you see | What to do |
|---|---|
| Agent email is not enabled for this account. | Agent email isn't available on your account yet. |
| Your team admin has turned off Grok Bot agent email, so this account cannot claim or use an agent email address. | Ask your team admin to turn on Agent Email (Cursor dashboard → Grok Bot page → Bot Capabilities). On Cursor teams it is off by default. |
| That address is taken, and addresses are never reissued, so retrying it cannot succeed. Choose a different name. | Choose a different name. |
| A message about allowed characters, length, or a reserved word | Pick a name that follows the name rules. |
| You can have one agent email address. | You already have an address. Ask your Bot what it is, or open the Email app. |
| Couldn't create your email address. Try again. (phone) | Check the name rules, or try on desktop, which shows the exact reason. |
| Too many email addresses checked in the last minute. | Wait a minute, then try again. |
Those two first rows are different problems. Not enabled for this account means the rollout has not reached you yet. The team-admin sentence means the Agent Email switch is off. Do not treat one as the other.
Since Grok Bot 0.70.2 (Oct 11, 2026), when agent email is off for your team or account the Bot says so instead of calling it a temporary problem. To see the exact reason, use the Email app on desktop. If none of these match, contact support with your Cursor account email and the exact message.
What mail can do
There is no inbox view in the apps, and you do not get notifications for new mail. Ask the Bot instead. Mail from the last minute may not show up in a search yet.
Anyone can send mail to the address, and there's no sender blocklist. Mail that fails the spam or virus scan is kept without its body or attachments and never starts a routine. Your Bot treats mail from other people as information, not instructions. Each message it reads is marked as from you or from someone else. A request inside an email does not make it send anything or take other actions on its own. Instructions inside an email the Bot received never count as your permission to send.
New mail doesn't start a chat or wake a Bot on its own. A Bot acts on incoming mail only through a routine you create. A routine can read the mail, summarize it, and draft a reply. Any email it wants to send waits as a draft until you approve it. A routine can watch mail from anyone, specific addresses, or a whole domain such as *@example.com. By default the routine runs only for senders that pass standard email authentication. Routines cannot filter by subject. Ask in chat, for example “When an email arrives from billing@example.com, summarize it and tell me.” Official routine notes live on Routines. Saving the method as a skill first is Save a Grok Bot skill and schedule a routine.
On launch day, users reported the Bot couldn't save an email-triggered routine (“Not a valid trigger”). Cursor staff (kevinn) said on the forum (Oct 9, 2026) that the Bot was leaving the inbox address out of the trigger when it saved, that this wasn't caused by the user's setup, and that a scheduled routine that checks the inbox was the workaround for now. A later staff reply (mohitjain, Oct 12, 2026) said scheduled routine runs don't currently get the Bot's inbox tools, only its main chat does, so that stopgap may not be able to read the inbox. Staff suggested having the routine hand the email to the Bot's main chat, which asks you to approve the send. Neither reply is an official fix. Scheduled checks aren't instant: schedules must be at least five minutes apart, mail from the last minute may not appear in a search yet, and every run spends usage.
Your Bot needs your approval for every email it sends. It shows you the full draft, and nothing sends until you press Send, including routines and replies. Asking in chat, or putting the instruction in a routine, doesn't skip that step, and there's no option for unattended sending. A routine that wants to send leaves a draft for you. A send can go to up to 50 recipients across To, Cc, and Bcc, and can carry 10 attachments (10 MB each, 25 MB total). Executable files can't be attached. First-contact mail and newsletters go to one recipient with a one-click unsubscribe link. If a message bounces, or someone unsubscribes or marks it as spam, the Bot stops emailing that address and tells you who it skipped. There are also limits on how many new people a Bot can email. If Gmail or Outlook is also connected, the Bot asks which account to send from when either could work, then tells you the address it sent from.
Inbound attachments follow the same size cap: up to 10 attachments, up to 10 MB each and 25 MB in total. Attachments beyond those limits are skipped.
If an admin turns agent email off later, Bots lose their email tools and email routines stop, but mail still arrives and members keep their addresses. Mail sent to existing addresses is still received and kept. Deleting your Grok Bot account deletes your mail and attachments. The address itself is retired and never given to anyone else.
For files you attach in chat rather than through this address, see Attach files and links in Grok Bot. For installing the app itself, see Connect an app to Grok Bot.
Pitfalls
- Expecting a second address, a rename, or a delete. You get one address, permanently.
- Looking for an inbox or a mail badge. Ask the Bot; the apps do not show incoming mail.
- Writing a routine that filters on subject. That filter is not available.
- Assuming a Team Bot shares one team inbox. It does not.
- Assuming it's on for you already. It's rolling out (@bot, Oct 9, 2026), and Cursor teams start with it off.
- Retrying a taken name; it can never be reissued.
- Expecting mail to wake the Bot. Only a routine acts on new mail.
- Expecting a way to block senders. Anyone can email the address.
- Expecting texts, calls or WhatsApp. The address is email only.
- Expecting a routine to send mail on its own. Every send waits for you to press Send.
- Combining several Cursor accounts under The X Subscription. The Bot email address and inbox stay on the non-primary account; they don't move to your primary account.
- Looking for a sender display-name setting. No official page documents one.