xAI Gives Grok Bot Dedicated Email Inboxes

The company rolled out native addresses on mail.grokbot.com, allowing autonomous agents to handle web signups and verification codes without touching personal accounts.

xAI started rolling out dedicated Grok Bot email inboxes under the @mail.grokbot.com domain. The feature was announced by the assistant’s official handle (@bot) on X and confirmed shortly after by Elon Musk. Instead of asking for broad OAuth access to a user’s personal Gmail or Outlook account, xAI now provides an isolated inbox where the agent can receive incoming messages, click activation links, and complete registrations independently.

Quick summary

Grok Bot can now provision dedicated inboxes ending in @mail.grokbot.com.
Users pick their username prefix in chat and confirm a setup card before the address goes live.
The agent reads incoming messages, captures verification codes, and subscribes to newsletters on its own.
On corporate and team accounts, the feature remains off by default and requires workspace admin approval.
xAI does not currently support custom company domains directly on the platform.

How Grok Bot email inboxes work

Setting up an address requires asking Grok Bot in a direct conversation or tagging the bot on X. The user suggests a username prefix, the system checks whether the handle is available, and an on-screen approval card prompts the user to finalize creation. The address does not activate until the user clicks to approve.

In hands-on testing by independent tracker @testingcatalog, the bot configured an address and signed up for a daily technology newsletter. It opened the confirmation email, clicked the verification link, and filed the welcome note without any human intervention. The inbox handles one-time passwords (OTPs), activation tokens, and digital receipts.

Security isolation and team controls

Most autonomous agents that handle email workflows have historically relied on direct inbox integrations. That model raised valid security alarms, because granting an AI agent access to an active personal or corporate mailbox exposes confidential threads, contact books, and years of correspondence.

Routing external mail through @mail.grokbot.com puts up a clean security boundary. The assistant manages signups in an isolated sandbox, separated from the user’s primary mailbox. To limit spam and unwanted bulk mail, outbound messages require single-recipient formatting and include mandatory one-click unsubscribe links. For team environments, including Cursor workspaces and xAI Enterprise, the feature ships disabled out of the box. Administrators must open the bot capabilities dashboard and manually enable “Agent Email.”

Current limitations

The initial release comes with clear boundaries. xAI has not added native support for custom company domains like @company.com. Organizations that want agent communications under their own brand still have to build external connectors using webhooks or the Model Context Protocol (MCP).

xAI has also not detailed inbox storage limits or explained whether standard users face different volume caps than SuperGrok Plus subscribers. Managing the address after setup remains another open question, with no public documentation yet on how to rename a handle or delete an inbox once confirmed.

What this changes

Giving an AI agent its own mailbox removes a persistent friction point in autonomous workflows. Automated tasks that once ground to a halt at “check your email for a verification code” can now run end-to-end without forcing a person to act as an authentication relay. It is an unglamorous infrastructure update, but it solves one of the messiest operational hurdles in running agents on the open web.