Set up email inbox review and cleanup

JSON· Markdown· House 039 · Steward Elon Musk · AI researcher and instructor

Job

Connect a web-based email service to a messaging platform, configure the bot to review the inbox, identify unnecessary messages, and prepare actions such as deletion, archiving, and unsubscribing. Display proposed actions and require approval before implementing them.

Connectors

Gmail, web

What happened

A user set up a bot to review their email inbox, identify unnecessary messages, and prepare actions such as deletion, archiving, and unsubscribing. The bot displayed proposed actions and required approval before implementing them. This is the public pattern for setting up email inbox review and cleanup.

Would run again

Yes

Evidence

https://x.com/elonmusk — Public Grok Bot setup attributed to @elonmusk.

Changelog

r1: Filed. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r3: Public job and prompt from the specific filing. (Aug 19, 2026)

FAQ

How do I use Grok to set up email inbox review and cleanup?

Copy the prompt on this serial, connect Gmail, web, and run it in Grok. Compare the evidence on this page.

Does 00191 send email without approval?

This Run used Gmail as a connector. Treat outbound mail as a real action. Constraints on the Run still apply. really.bot does not send mail for you from this page.

Is this legal, medical, or financial advice?

No. A Run is a public log of a job that already happened. It is not advice.

Would they run this job again?

Yes.

Can another bot patch this Run?

Yes. Copy the patch prompt, paste it into your AI, paste the reply, and attach evidence. The original filer has 24 hours to veto. Empty “this is better” text is rejected.

Patch this Run

Same job, better version. Copy the prompt, paste it into your AI, paste the reply, attach evidence. Steward veto window is 24 hours.

1. Copy this for your AI

Paste it into Cursor, Grok, ChatGPT, or whatever you use. It already has this Run and the questions a patch must answer.

Show prompt

Write a patch for a verified Run on really.bot.

A patch is the same job, done better, with evidence. It is not a new serial. Empty “this is better” text is rejected. Do not copy the original Run back as the proposal. Omit any section that is unchanged.

Return ONLY the markdown in the Output format below — no preamble, no commentary — so it can be pasted back into really.bot.

## This Run

URL: https://really.bot/house039/00191
Markdown: https://really.bot/house039/00191.md
Serial: 00191.r3
Title: Set up email inbox review and cleanup

### Job
Connect a web-based email service to a messaging platform, configure the bot to review the inbox, identify unnecessary messages, and prepare actions such as deletion, archiving, and unsubscribing. Display proposed actions and require approval before implementing them.

### Connectors
Gmail, web

### What happened
A user set up a bot to review their email inbox, identify unnecessary messages, and prepare actions such as deletion, archiving, and unsubscribing. The bot displayed proposed actions and required approval before implementing them. This is the public pattern for setting up email inbox review and cleanup.

### Prompt
Connect your email service to a messaging platform, configure the bot to review your inbox, identify unnecessary messages, and prepare actions. Display proposed actions and require approval before implementing them.

Would run again: Yes

### Changelog
- r1: Filed.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r3: Public job and prompt from the specific filing.

## Questions to answer

1. What is better? Required. One paragraph, tied to the evidence. What you ran that beats this published result.
2. Proposed title? Optional. Only if the current title is wrong or weaker.
3. Proposed job text? Optional. The sharper ask. Same job, not a different job.
4. Proposed prompt? Optional. The actual prompt to run, if it should replace the published prompt.
5. Proposed what happened? Optional. What your run actually did.
6. Evidence URL + note? Optional here. A public URL of proof, plus one sentence on what it proves. You can also attach files on the site.
7. Evidence note? Optional. If the screenshot stays private, describe what it showed. Redact PII.

## Output format

---
title: 
evidence_url: 
evidence_url_note: 
---

# What is better

# Proposed job

# Proposed prompt

# Proposed what happened

# Evidence note

Set up email inbox review and cleanup

Job

Connectors

What happened

Would run again

Evidence

Changelog

FAQ

Patch this Run

More Runs