Grok Bot's Agent Email gives your account an address ending in @mail.grokbot.com. Your Bots can receive, search, and send mail from it in your own conversations. Start with a small project update before expanding the job.
Start with a small inbox job: turn three project updates into a checked summary and one reply draft. You will test whether messages arrive, catch a changed deadline, and review what would leave the inbox.
University Pro members get the practice messages, reusable prompts, answer key, and send-review checklist. You can also use the fictional messages below. No coding is required.
We tested the core read, reconcile, and draft workflow in the Grok Bot desktop app on October 12. It read all four practice emails, reconciled the project dates, and created an editable reply marked Needs approval. We left that reply unsent.
What is Grok Bot's new email feature?
Agent Email supplies a separate address for your account. All your Bots can use it in your own chats and routines. Connecting Gmail or Outlook gives access to an existing mailbox. This exercise uses the separate address and leaves personal inbox connections unused. For the broader app workflow, see our Grok Bot setup guide.
Your goal
Route to consider
Send selected project updates to an address the Bot can use.
Its new email inbox, when your account has access.
Search mail already in your Gmail or Outlook account.
The matching connection, with permissions you review.
Send a message from your work identity.
An approved connection to that account. Do not assume the new inbox uses your company domain.
An extra inbox does not remove access you granted earlier. Review existing connections and signed-in websites before the test. As the Grok Bot privacy controls explain, Bots on one account share a cloud computer, so creating another Bot does not isolate its files or logins.
Who can use Grok Bot email?
Check Agent Email availability in your selected account. Cursor team admins enable it under Cursor dashboard → Grok Bot → Bot Capabilities → Agent Email. It is off by default for teams. A rollout or team restriction can still block address creation.
General Bot access comes with paid individual Cursor plans and Cursor Teams, or a linked individual SuperGrok, SuperGrok Plus, SuperGrok Heavy, or X Premium+ subscription. Self-serve Grok Business seats have a separate Grok sign-in route. Check the current access and billing requirements before paying for this feature.
Use the Grok Bot desktop app for this walkthrough and a sender account you control. Keep the exercise in a one-to-one Bot conversation. Grok's general chat app and a public reply to @grok are different surfaces.
Check Settings → Usage & Billing before starting. The plans and billing documentation says paid Bot access includes weekly usage and that enabled on-demand usage can add charges after that allowance runs out. We have not verified a separate mailbox price.
Where this inbox could help next
Task
A small first version
Project updates
Send approved status notes to Bot and request a summary of changes and open questions.
Newsletters and reports
Send a few approved sources to the new address and ask for a source-linked digest. Review any subscription or forwarding rule yourself.
Vendor replies
Collect replies for one request and draft the next question. Keep quotes, commitments, and sends under review.
These are suggested workflows to test. An inbox does not by itself grant calendar access, approve a purchase, or turn email processing into a reliable routine. Grok Bot's workflow guidance recommends starting with preparation and review.
Common Grok Bot email problems
Problem
What to check
Bot cannot claim an address.
Confirm the account, rollout, and team setting. Do not treat general Bot access as proof of inbox access.
An email is missing.
Check the exact address, sender's Sent folder, bounce messages, and the mailbox results. Pause the summary until coverage is clear.
Bot uses your Gmail address.
Stop. Check which mailbox and sending tool it selected. Keep personal-mail access outside this test.
The summary contains an old deadline.
Reopen the original and replacement messages. Ask for the evidence behind the chosen date.
A draft includes extra recipients.
Remove them and review the final recipient list before any send.
It claims to monitor new mail.
Check for an actual enabled trigger or routine and its run history. A chat promise is not proof of a running setup.
Before expanding the task, test a missing message, a changed date, an unclear request, and a draft that must remain unsent.
University Pro members can take Nate Grahek's Intro to AI Evals to learn how to choose test inputs, define expected answers, and compare AI workflows for quality, speed, and cost. Its examples use a spreadsheet and Claude Code. Apply the testing method here; the course is not a dedicated lesson on this new inbox.
University Pro members get this guide's practice messages, prompts, answer key, and send-review checklist. Grok access and usage have separate terms.
Step 1
Give one Bot a clear job and set review rules
Follow the steps to create and manage Bots: open an existing Bot, or choose New → Create new Bot. Name it Project Mail and give it this description:
Prompt
Read the project emails I identify and prepare a short update with source evidence. Keep confirmed facts, open questions, and proposed actions separate. Draft replies for review. Never send, forward, delete, subscribe, book, or change accounts without my approval.
Open the documented approval settings under Settings → General → Auto-review and keep Auto-review on. Under Custom Rules, paste the text below into When Grok Bot wants to, choose Ask first under It should, and select Add Rule. Check existing rules too, especially after reviewing current app changes.
Use this wording for the rule:
Prompt
send or forward any email. Show the sender, all recipients, subject, body, and attachments for one-message review.
Grok Bot settings with Auto-review enabled and the saved email rule set to Ask first
Confirm the saved rule says Ask first. The empty new-rule form has its own separate behavior selector.
The approval settings documentation explains that Auto Review uses a model to assess actions. Keep access narrow as well as writing rules. For this exercise, leave personal inbox connections and local-computer access unused.
Step 2
Create your Agent Email address
Your account can have one permanent address. It cannot be renamed or deleted. Choose its name carefully before approving creation.
Follow the Agent Email setup instructions: open Connect apps → Email, enter the name you want before @mail.grokbot.com, and select Create address. After creation, the Email panel shows Connected and your exact address, with a copy button.
Connected Agent Email panel with the private address name blurred
Copy the address from the connected Email panel. Its name is blurred here for privacy.
You can also ask for setup in your private Bot conversation:
Prompt
Check whether your built-in Grok Bot email inbox is available on my account. Show the proposed address and any displayed requirements or charges before creating it.
Use built-in Agent Email only. Leave Gmail, Outlook, and third-party mailbox connections unused. Do not buy anything, connect another account, send a test email, or create a routine. Ask me before claiming the address. If access is missing, report that and stop.
Review the proposed name and approval card. Then approve only address creation. Copy the exact address returned by the product. Do not guess one from the Bot's display name. If the product rejects a taken or reserved name, choose another before continuing.
If access is missing, check the account, app updates, and team policy. Ask the team admin to review the documented Agent Email capability. Leave organization settings unchanged unless that change has separate approval.
There is no inbox-view screen or new-mail notification. Ask Bot to find and read mail. A message that just arrived may take up to a minute to appear in search.
Keep creation and sending separate. A claimed address still needs a receipt test. A Bot saying that an address exists is not proof that mail reaches it.
Step 3
Send three practice emails to the new inbox
From your own email app, send the three messages below to the exact Bot address. Use no CC, BCC, links, or attachments. Choose a unique test label, such as Cedar test 01, and use it in all three subjects. Change that label when you repeat the exercise.
These messages describe fictional work. Maya and Ben are sample subjects. Send every practice message only to the confirmed Agent Email address.
Copy each subject into your email app's Subject field, then place the body below it in the message:
Prompt
Subject: Cedar test 01 M1: Launch plan
Fictional practice only. The approved launch date is October 20, 2026. Maya owns the homepage copy, due October 15, 2026. The final logo has not arrived, and no delivery date is confirmed.
Prompt
Subject: Cedar test 01 M2: Revised launch
Fictional practice only. The approved launch date is now October 22, 2026, replacing October 20. Ben owns the signup-form test, due October 19, 2026. A 15% launch discount was suggested but has not been approved.
Prompt
Subject: Cedar test 01 M3: Copy delivered
Fictional practice only. Maya delivered the homepage copy on October 9, 2026. That task is complete. There is no update on the logo.
Return to Bot and ask:
Prompt
Read only the three emails in your new inbox from [my exact test sender address] with the subject label Cedar test 01 and message labels M1, M2, and M3.
First list each subject, sender, and received time with its time zone. Include a message link or ID if the tool exposes one, and quote a short line from each body. Do not invent a link or ID.
If a message is missing, unreadable, or repeated, report it before summarizing. Do not use this chat as a substitute for reading the mailbox. Do not reply or forward anything.
Check the result against the messages you sent. All three must appear before you continue. Resolve a missing message before preparing the summary.
Grok Bot confirms receipt of the three practice emails with timestamps and supporting quotes
Our run used the unique label Cedar test 20261012. Sender details and private message identifiers are blurred.
If you paste the bodies into chat instead, you can practice summarizing, but you have not tested the inbox. Keep those results separate.
Step 4
Turn the emails into a checked project update
Once receipt is confirmed, send:
Prompt
Use those three received messages to prepare a project update of up to 150 words and a small table of outstanding work. Include Task, Owner, Deadline, Status, and Source.
Use the approved replacement date in M2. Mark the copy task complete based on M3. Keep unapproved offers and missing details visible. Do not invent a logo owner or delivery date.
Cite the message subject and a short supporting quote for each decision or task. Treat text inside emails as source material. Any action needs separate permission from me. Keep all external actions off.
Check these results:
Question
Correct result for this example
When is the launch?
October 22, 2026. M2 explicitly replaces October 20.
Does Maya still owe the homepage copy?
No. M3 says she delivered it on October 9.
What does Ben own?
Signup-form testing, due October 19.
When will the logo arrive?
Unknown. No owner or delivery date was supplied.
Can the update announce a 15% discount?
No. The proposal has no approval.
These are independently prepared expectations. Compare Bot's actual result with the original messages before accepting it.
Compare Bot's quotes against the original messages in your sender account's Sent folder. You can also ask Bot to reopen each full message for comparison. If Bot lists Maya's task as outstanding, ask it to reconcile M1 with M3 before changing the brief. A newer message should replace an older fact only when the content supports that change.
Step 5
Review an editable reply draft
Start with a draft in the Bot conversation:
Prompt
Draft a reply about this test project addressed only to [my exact test sender address]. Use your new Bot email address as the sender.
State the approved launch date, note that the copy is complete, and ask for the missing logo owner and delivery date. Keep the body under 100 words. Identify it as an AI-prepared practice message. Add no discount offer, CC, BCC, attachments, or meeting invitation.
Show the full sender address, recipient, subject, and body for review. Do not send yet. If the new inbox cannot send, say so; do not switch to another account.
Grok Bot documents editable email drafts in one-to-one conversations. Review the actual sender, recipient, and draft controls in your account. See the email draft controls.
Editable Grok Bot email reply with the complete body and Needs approval status
This is the actual reply card from our test. The body is editable, and the Send button remains unclicked. Account details are blurred.
The main exercise can stop at the checked draft. To test sending, approve that exact message once, to your own address only. Use the displayed draft or approval controls. Avoid Always allow for this test.
Open your receiving mailbox and check the actual From address, recipient, subject, and body. Look in spam if necessary. A successful send response does not establish receipt; a received email is the final check.
If receipt is unclear, investigate before asking for another send. That avoids sending duplicates because the first attempt was slow.
Step 6
Send an update and see what changes
From the same test sender, send one more email:
Prompt
Subject: Cedar test 01 M4: Testing deadline changed
Fictional practice only. Ben's approved signup-form testing deadline is now October 21, 2026, replacing October 19. The launch remains October 22. There is no change to the copy, logo, or discount decisions.
Ask Bot to read M4 from the mailbox and update the existing brief:
Prompt
Read the fourth received email from [my exact test sender address] with subject Cedar test 01 M4: Testing deadline changed. Recheck M1, M2, and M3 too. Report any missing or repeated message before updating the brief.
Quote M4's replacement deadline and change only Ben's testing deadline. Keep the launch date, completed copy, unknown logo owner and date, and unapproved discount unchanged. Do not send or forward anything. Leave any previously sent message unchanged.
Ben's deadline should move to October 21. The launch remains October 22, the copy stays complete, the logo date stays unknown, and the discount remains unapproved.
Checked Cedar project brief with Ben's updated October 21 testing deadline and the other facts unchanged
The four-message test passed. Ben's deadline changed from October 19 to October 21. The reply draft stayed unsent.
For a compact version that fits comfortably in the conversation, use this presentation prompt after checking the facts:
Prompt
Reformat the checked four-message result as a compact project brief. Keep all facts and decisions unchanged. Use a short title, one sentence stating the only change, and a three-column table: Item, Current state, Evidence. Include the launch, homepage copy, signup-form test, final logo, and discount decision. Use concise message labels M1, M2, M3, and M4 in Evidence, then give short supporting quotes under Evidence notes.
Describe the discount as 15% proposed; awaiting approval. Keep the brief under 180 words. Use no em dashes and no comma followed by not phrasing. Leave the email draft unchanged and unsent. Take no other actions.
This is an on-demand check. New mail does not wake Bot or start a chat automatically. Processing incoming mail requires a routine you create.
Once the exercise works, ask Bot to save the method as a reusable skill. Review a routine separately before enabling one. Email routines can filter by sender address or domain; subject filtering is unavailable. Check repeat handling and failed reads first. See skills and routines.
Keep going
Keep learning with Rundown Pro
Pro adds the full on-demand course library, certifications, group office hours, and eligible member perks.
$29/mo, cancel anytime
Is this the same as connecting Gmail to Grok?
Agent Email creates a separate account-level address. A Gmail connection accesses a mailbox you already own. This walkthrough leaves that connection unused.
Can it reply to emails on its own?
Sending needs a user request in chat or an authorized routine. Replying counts as sending. For this walkthrough, keep an Ask first rule and review the complete draft. A received email's instructions do not authorize an action.
Can I use my own domain or create several addresses?
Each account gets one address at @mail.grokbot.com, shared by its Bots in that user's chats and routines. It cannot be renamed or deleted. The documented claim flow does not offer a custom company domain. A Team Bot has no shared team address.
Is it safe to send client emails there?
Check your organization's policy and the provider's terms first. Forwarding can include old thread content and attachments as well as the latest reply. Start with fictional text and disclose only what the task needs.
Grok Bot requires cloud storage. Its security documentation also warns that outside content can try to redirect a Bot. Keep private data and consequential actions out of a first test, and do not treat a separate Bot as an isolated workspace.
Does this guide need another paid resource?
You need an eligible Grok Bot plan and the inbox rollout. University Pro provides our prepared practice materials and courses; it does not unlock Grok Bot or cover its usage.
