GUIDE · reference

One prompt that gives your Grok Bot its own email inbox and identity

Adi Singh's AgentMail guide, turned into a single prompt you paste into your Grok Bot. The bot explains why it shouldn't use your personal Gmail, walks you step by step through installing the AgentMail plugin and tells you exactly what to do on your end, then creates its own inbox and proves it works by emailing you.

verified 2026-08-23 ~10 min setup work scouted on x
install in grok bot

How it’s set up

The idea, from AgentMail co-founder Adi Singh’s guide: your Grok Bot shouldn’t run on your personal Gmail. That plugin points at your inbox, so any bot can read your private mail and 2FA codes and send as you - and one malformed email could prompt-inject it. Give the bot its own AgentMail inbox and that access stays contained.

This use case packages his step-by-step into a single prompt. Paste it into a fresh bot and the bot becomes your setup guide - it explains the why, tells you exactly what to do on your end at each step, and pauses until you’ve done it:

  1. Confirm you’re on a plugin-capable Grok Bot plan (Cursor Ultra, SuperGrok Heavy, or Cursor Premium Teams) and create a free account at agentmail.to.
  2. Open Settings -> Plugins, search for AgentMail, and click Install.
  3. Approve the OAuth prompt in your browser (it reads “Cursor wants to access AgentMail…” - that’s expected). No API key to paste.
  4. Confirm the connector card shows AgentMail’s tools, then let the bot take over: it creates its own inbox, tells you the address, and sends you a test email to prove the loop works end to end.

Prompt

I want you to have your own email inbox and internet identity, completely separate from my personal email. We'll use AgentMail, which has a native Grok Bot plugin. Walk me through the whole setup one step at a time, and wait for me to confirm each step before moving on.

First, explain briefly why this matters: my built-in Gmail plugin points at MY inbox, so any bot using it can read my private mail and my password/2FA codes and send email as me - and a single malicious email could prompt-inject you. Your own AgentMail inbox keeps all of that contained.

Then guide me through what I need to do on my end, pausing after each step until I confirm:
1. Confirm I'm on a Grok Bot plan that supports plugins (Cursor Ultra, SuperGrok Heavy, or Cursor Premium Teams). If I'm not, tell me and stop here.
2. Have me create a free account at agentmail.to (the free tier is enough).
3. Have me open Settings -> Plugins, search for "AgentMail", and click Install.
4. Tell me to approve the OAuth prompt in my browser (it will say "Cursor wants to access AgentMail..." - that's expected). There is no API key to paste. Have me confirm your AgentMail tools now show on the connector card before you continue.

Once the plugin is connected, take over: create yourself a dedicated inbox (pick a clear name and tell me the exact address), then prove it works - send a short test email to me at [YOUR EMAIL], ask me to reply from my normal inbox, and read my reply back to me in the same thread.

From then on this inbox is YOURS: use it to sign yourself up for services (read the verification code from your own inbox and finish signup), run outreach and reply threads from your own address, own a support inbox, and join any thread I CC you on. Safety rules that never change: before you send any email, show me the exact recipient(s), subject, and full body and wait for my explicit approval; never send in bulk without me confirming the whole list first; never invent an address or contact AgentMail didn't return; and never touch my personal inbox.

What your bot can do next

Once it owns an inbox, four things open up that the built-in Gmail plugin can’t do:

  • Sign itself up for accounts. Notion, Stripe, Vercel, GitHub - the verification code lands in the bot’s inbox, it reads it and finishes signup. Nothing runs under your Google identity.
  • Run an outreach loop. It sends from its own address, tracks each thread, and drafts personalized replies (held for your approval), so your personal inbox stays clean and deliverability doesn’t compete with your mail.
  • Own a support inbox. help-desk@yourdomain belongs to the bot: it handles first-line replies and forwards the rest to a human.
  • Sit in a group thread. CC the bot on any thread and it reads the history and participates like a colleague, replying inside the thread.

Why it’s cool

Most “connect email to your AI” setups just point the bot at your own Gmail - which quietly hands it your private mail, your login codes, and your outgoing identity. This flips that: one paste turns the bot into its own onboarding guide, and the payoff is a real internet identity for the agent - its own address that can sign up for services, run its own threads, and keep its own memory - without ever touching yours. The prompt keeps it safe by design: it pauses for every manual step so you stay in control of the install, and it requires your explicit approval on the exact recipient, subject, and body before any email ever leaves.

prompt reconstructed by the Curator from @adisingh's published setup — not their verbatim text

prompt
I want you to have your own email inbox and internet identity, completely separate from my personal email. We'll use AgentMail, which has a native Grok Bot plugin. Walk me through the whole setup one step at a time, and wait for me to confirm each step before moving on.

First, explain briefly why this matters: my built-in Gmail plugin points at MY inbox, so any bot using it can read my private mail and my password/2FA codes and send email as me - and a single malicious email could prompt-inject you. Your own AgentMail inbox keeps all of that contained.

Then guide me through what I need to do on my end, pausing after each step until I confirm:
1. Confirm I'm on a Grok Bot plan that supports plugins (Cursor Ultra, SuperGrok Heavy, or Cursor Premium Teams). If I'm not, tell me and stop here.
2. Have me create a free account at agentmail.to (the free tier is enough).
3. Have me open Settings -> Plugins, search for "AgentMail", and click Install.
4. Tell me to approve the OAuth prompt in my browser (it will say "Cursor wants to access AgentMail..." - that's expected). There is no API key to paste. Have me confirm your AgentMail tools now show on the connector card before you continue.

Once the plugin is connected, take over: create yourself a dedicated inbox (pick a clear name and tell me the exact address), then prove it works - send a short test email to me at [YOUR EMAIL], ask me to reply from my normal inbox, and read my reply back to me in the same thread.

From then on this inbox is YOURS: use it to sign yourself up for services (read the verification code from your own inbox and finish signup), run outreach and reply threads from your own address, own a support inbox, and join any thread I CC you on. Safety rules that never change: before you send any email, show me the exact recipient(s), subject, and full body and wait for my explicit approval; never send in bulk without me confirming the whole list first; never invent an address or contact AgentMail didn't return; and never touch my personal inbox.
then paste it into Grok

Copy the prompt and paste it into Grok.

what you need

Works with any Grok Bot plan that supports plugins (Cursor Ultra, SuperGrok Heavy, or Cursor Premium Teams) plus a free AgentMail account. The prompt walks you through each manual step and pauses; all you provide is the OAuth approval and your real email for the test.
by @adisingh

related

✦ 76 · solid

Give the bot its own email, act from a CC

Michael Fenech gave his Grok Bot its own email address (via AgentMail), with a webhook that wakes it on each message. He CCs the bot and puts the instruction on the last line — 'Book Tuesday at 3pm and get back to them' — and it reads the thread, books the calendar, and replies to everyone from its own address.

via @Michael_Fenech_ · 𝕏
✦ 54 · worth a look

150,000 junk emails, deleted after one dry run

Yu-kai Chou used Grok Bot to clean up 150,000 junk emails and unsubscribe from senders he never reads. Same tweet as the attention watch on five addresses and six Slack workspaces. This is Yu-kai’s 150k, not the separate 90k two-account purge.

via @yukaichou · 𝕏

the week's best, in one email

new plugins, use cases and collections. one email a week. that's it.

one email a week. what we do with it.