Grok Bot Email Address: Claim, Receive, Send and Limits

You claim an address at mail.grokbot.com, such as yourname@mail.grokbot.com, and your Bots can then receive, read, search and send email from it. There are two ways to claim it, and both end in the same place.

• Ask your Bot. Say 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.
• Use the Email app. On desktop, open Connect apps in the sidebar and choose Email. On the phone, open Settings > Connect apps > Email. Under Email address, type a name in Choose a name, then choose Create address.

After you claim it, the app shows the address with a button to copy it. If you use Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. through a Cursor team, a team admin has to turn on agent email first, which is covered at the end of this page.

The Email app works differently from other apps. Gmail and the rest connect an account you already have, whereas this one gives your Bots an address of their own. With an address, the help page lists five things a Bot can do:

• Signing up for services with the Bot's own address, and picking up the verification code or link with your OK.
• Collecting receipts, newsletters and reports, and summarizing them.
• Drafting digests, updates and replies.
• Forwarding an email from its inbox with the original formatting, images and attachments (needs Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. 0.75.2 or later).
• Running a routine when email arrives, optionally only from specific senders.

Pick the name slowly. You get one address, and you can't rename it or delete it.

• Lowercase letters, digits, dots, hyphens and underscores only.
• Start and end with a letter or digit.
• At most 64 characters.
• No reserved words such as support, admin, billing, security, help, info, team, cursor, grok and xai.

Every address is unique, and once someone claims one it is never given to anyone else, even after the account that claimed it is deleted. That permanence cuts both ways. Nobody can later pick up an address you used to sign up for services, but it also means a misspelled name stays with you. If you plan to use the address for sign-ups that other people will see, a plain name that reads well in a receipt or a reply is probably the safer choice.

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. They can't use it in Slack threads or in chats where someone else is talking to the Bot, and a Team Bot doesn't have a shared team address.

Anyone can send email to your address. Mail that fails the spam or virus scan is kept without its body or attachments, and it never starts a routine. Each incoming message can carry up to 10 attachments, up to 10 MB each and 25 MB in total, and attachments beyond those limits are skipped.

There's no inbox view in the apps and no notifications for new mail, which is easy to miss if you expect a mail client. To see your mail, ask the Bot, for example "What arrived in your inbox today?" or "Find the receipt from last week." Mail that arrived in the last minute may not show up in a search yet.

Set up a routine. New mail doesn't start a chat or wake a Bot on its own, so a Bot acts on incoming mail only through a routine you create. Ask for one in chat, for example "When an email arrives from billing@example.com, summarize it and tell me."

By default the routine only runs for mail from senders that pass standard email authentication checks. Routines can't filter by subject, so sender is the lever you have. A domain pattern is the broadest useful filter when one supplier sends from several addresses, and a single address is the tighter choice when only one mailbox matters. A routine can read the mail, summarize it and draft a reply, and any email it wants to send waits as a draft until you approve it. Building and scheduling routines in general is on the skills and routines page.

It depends on who asked. The split is between email you requested in chat and email that came out of anything else, and the help page is firm that there is no option for unattended sending.

So a routine that leaves a draft instead of sending is working as designed: open the draft and press Send. If you've also connected Gmail or Outlook, the Bot asks which account to send from when either could work. How approval cards and Auto-review behave in general is on the approvals page.

The same thinking covers content safety. Your Bot treats email from other people as information, not instructions. Each message it reads is marked as from you or from someone else, and a request inside an email doesn't make it send anything or take other actions on its own.

The outgoing limits are there partly to keep the address from being flagged as spam. Most people will never hit the first two, but the last two change how the Bot behaves without being asked.

• Up to 50 recipients per email, across To, Cc and Bcc.
• Up to 10 attachments, up to 10 MB each and 25 MB in total. Executable files can't be attached.
• Newsletters and first-contact emails go to one recipient per message and include 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. The help page doesn't give the number.

If you delete your Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. account, your mail and attachments are deleted, and the address is retired and never given to anyone else.

For Cursor teams, agent email is off by default. A team admin turns it on in the Cursor dashboard: on the Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. page, under Bot Capabilities, turn on Agent Email. Members can then claim an address. If an admin turns it off later, Bots lose their email tools and email routines stop running, but mail sent to existing addresses is still received and kept, and members keep their addresses.

When a claim fails, the message tells you which case you're in. The table pairs each one with the fix from the help page.

If none of these match, contact support with your Cursor account email and the exact message.