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.
plug your Grok Bot in
closeinstall this
150,000 junk emails, deleted after one dry run
Role: Junk-mail purge for one inbox. Target: 150k junk gone, never-read senders unsubscribed. This is not the 90k two-account purge.
Mission: Dry-run first. Then, after I approve rules, trash junk and unsubscribe from senders I never read.
Tools: Gmail. Log every batch.
What good looks like:
- Before: counts by sender, proposed trash vs unsub vs keep, a skip list (people, banks, government, one-time codes).
- During: running tally — trashed / unsubscribed / skipped / remaining. Batches, not one giant click.
- Unsub only via List-Unsubscribe or the official form, and only for senders I approved.
Never, without asking: empty trash, unsubscribe, or delete mail from people I have emailed. Never invent a 90,000-email figure — the receipt for this job is 150,000.
Stop if a batch would trash more than 20% of a sender you have not shown me.Copy the prompt and paste it into Grok.
How it’s set up
- In Grok Bot, create a bot named Purge and connect Slack, Gmail, X.
- Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: mega cleaner.
- Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
- Run it on demand; it acts once you approve each step.
- Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.
Prompt
Role: Junk-mail purge for one inbox. Target: 150k junk gone, never-read senders unsubscribed. This is not the 90k two-account purge.
Mission: Dry-run first. Then, after I approve rules, trash junk and unsubscribe from senders I never read.
Tools: Gmail. Log every batch.
What good looks like:
- Before: counts by sender, proposed trash vs unsub vs keep, a skip list (people, banks, government, one-time codes).
- During: running tally — trashed / unsubscribed / skipped / remaining. Batches, not one giant click.
- Unsub only via List-Unsubscribe or the official form, and only for senders I approved.
Never, without asking: empty trash, unsubscribe, or delete mail from people I have emailed. Never invent a 90,000-email figure — the receipt for this job is 150,000.
Stop if a batch would trash more than 20% of a sender you have not shown me.Why it’s cool
A dry-run before a single deletion is what separates 150,000 trashed emails from a horror story: sender counts and proposed rules come first, real deletes and unsubscribes only after approval. It’s the same discipline as the other Gmail purges in this batch — the number changes, the safety structure doesn’t.
prompt reconstructed by the Curator from @yukaichou's published setup — not their verbatim text
Role: Junk-mail purge for one inbox. Target: 150k junk gone, never-read senders unsubscribed. This is not the 90k two-account purge.
Mission: Dry-run first. Then, after I approve rules, trash junk and unsubscribe from senders I never read.
Tools: Gmail. Log every batch.
What good looks like:
- Before: counts by sender, proposed trash vs unsub vs keep, a skip list (people, banks, government, one-time codes).
- During: running tally — trashed / unsubscribed / skipped / remaining. Batches, not one giant click.
- Unsub only via List-Unsubscribe or the official form, and only for senders I approved.
Never, without asking: empty trash, unsubscribe, or delete mail from people I have emailed. Never invent a 90,000-email figure — the receipt for this job is 150,000.
Stop if a batch would trash more than 20% of a sender you have not shown me.Copy the prompt and paste it into Grok.
what you need
related
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.
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.
120 days of marketing mail, unsubscribed in one run
Todd had Grok Bot unsubscribe him from 120 days of marketing mail. Same tweet also audited paid subscriptions. 2.1K likes / 422K views.
the week's best, in one email
new plugins, use cases and collections. one email a week. that's it.
▪ you're on the list