In the everyday handling of digital tasks, identity and reach often determine whether an automated process can finish what it starts.
Confirmation codes arrive in one place, replies land in another, and the person or system coordinating the work must still bridge the gap by hand. Many AI systems that act on behalf of a user have relied on borrowed accounts or temporary forwarding for this reason, keeping the agent's activity nested inside an existing inbox.
Grok Bot is an AI agent system from SpaceXAI that presents itself as a set of persistent teammates rather than a single chat session. Each bot runs on its own cloud computer with a browser, file system, and terminal, so it can open websites, fill forms, edit files, and continue multi-step work even when the user's device is offline.
Users can assign different bots specific roles and context that accumulates over time, and the bots can pass work among themselves in shared threads. The service has been available on desktop and Apple devices and is included with certain plans such as Cursor Pro and SuperGrok.
Earlier versions already allowed bots to draft and send email through a connected Gmail or Outlook account, or through third-party mailbox plugins, but the activity remained tied to accounts the user already controlled.
This time, Grok Bot is getting an update.
It is announced that bots can now receive their own email addresses ending in @mail.grokbot.com.
According to the announcement, a bot can use the address to sign up for services, contact businesses, or schedule time with someone. A follow-up note in the same thread explained that the feature was rolling out to users that day and that an inbox can be claimed by asking the bot directly or by tagging @bot on X.
For team accounts, an administrator must first enable the capability.
Addresses use a user-chosen prefix followed by the fixed domain. When a user requests one, the bot checks availability and requests confirmation before claiming it, with a clear warning that each address is unique and is never reissued, even if the bot or the address is later deleted.
The dedicated inbox keeps the bot's correspondence separate from the user's personal or work email. Incoming confirmation links, vendor replies, or scheduling messages can land directly with the agent that initiated the thread, so the bot can read them and continue the task without requiring the user to forward mail or share full account credentials.
Users who have tested the feature report that the bot presents the address as its own when contacting external parties, making the source of the message identifiable. The announcement did not specify sending limits, retention periods, or additional charges for the inbox itself.
This change sits alongside earlier email functions that still route through user-connected accounts. Those remain available for cases where the bot should send from an established identity. The new addresses add an independent channel that can receive mail the bot itself generates, such as one-time codes from services it signs up for or replies to outreach it has started.
Because the address cannot be recovered after deletion, the choice of name becomes effectively permanent once claimed.
