How to Use Muse to Organize Your Inbox

Muse, Meta's personal AI agent, is designed to act on your connected services rather than just talk about them, so inbox cleanup — proposing a filing scheme, sorting old mail, flagging anything money-related — is within its remit once you connect the email account you use. Per TechCrunch's launch reporting, Muse connects to services like email and calendars with users opting in one service at a time, and where no app action exists it can fall back to working in its own browser. The sane workflow is staged: have Muse propose a system first, approve it, then let it apply changes in batches you can audit. That staging matters because cleanup involves moving and archiving your mail, and while Meta's confirmed sensitive-action list covers sending email and purchases, hand-approved batches plus the full audit trail are how you keep an agent from filing an important message into oblivion.

• Batch-by-batch approval is slower but essential: a misfiled client thread or tax receipt is expensive to unwind.
• Press and early users report agents sometimes stall or fail mid-task; check the audit trail after each batch rather than assuming completion.
• Deletion is the one cleanup action to keep entirely manual — archiving is reversible, deleting is not.

1. 1

   Connect email with the access level you intend

   If you only want a cleanup proposal, read-only suffices. Grant broader access only when you're ready for Muse to actually move mail, and remember you can dial access back anytime.

2. 2

   Describe how you work, not just what you have

   Folders that match your real workflow ('active clients, waiting-on-payment, vendors') beat generic labels. Tell Muse your roles and it can propose categories in your words.

3. 3

   Demand a plan before any action

   Ask for the proposed scheme with example emails per category. Approving ten examples per folder is the cheapest way to catch a bad sorting rule.

4. 4

   Protect the recent stuff

   Instruct Muse to leave the current week alone. Old mail is where sorting experiments belong; today's messages are where mistakes hurt.

5. 5

   Review the change log

   Muse shows a complete audit trail of what it has done. Reconcile it against your mail client after each batch — especially anything that touched money or legal threads.

A wedding photographer whose inbox mixes active client threads, second-shooter availability, album vendor spam, and deposit receipts.

Go through the last 90 days of my inbox and draft a simple filing plan. I want a small set of folders that match how I actually work: active weddings, past clients still waiting on albums, vendors, and everything else. Show me ten example emails per folder so I can sanity-check the scheme before you apply it. Money messages — deposits, invoices, refunds — get pulled onto a separate list so I can eyeball each one. Leave everything from this month untouched. Archive only, never delete. Apply the plan after I approve it, in batches of about 50, and give me a log of exactly what moved where.

• Your roles and recurring senders

  Cleanup that fits a freelancer's client threads won't fit a parent's school mail; Muse needs your context to propose categories that stick.

• The scale of the backlog

  Hundreds versus tens of thousands of messages changes the strategy and how small the review batches should be.

• Messages that must never be touched

  Tax records, legal notices, or an ongoing dispute thread should be named as off-limits up front.

• Archive versus delete policy

  Deciding now that nothing gets deleted removes the worst failure mode from the job.

• How much access you're granting

  Read-only for the proposal phase; broader only when you're ready to approve actual moves.

For this task, it is smart to make Muse check with you before it takes certain actions. Decide your rules up front and include them in the prompt.

• Approving the filing scheme before it's applied — The categories are the whole system — once a bad rule runs at scale, unwinding it takes longer than the cleanup saved.

• Green-lighting each batch of moves — Batch review means one wrong rule damages 50 messages, not your entire archive.

• Any unsubscribe or list-removal action — Muse may need its browser where no direct action exists; you want to see which lists it's leaving on your behalf.

• Anything that would delete rather than archive — Keep deletion manual and permanent decisions yours.

• ✓Start the experiment on mail older than six months — low stakes, high volume, perfect for learning how Muse sorts.
• ✓Ask for 'money-related messages listed separately' in every cleanup: invoices and refunds are where misfiling actually costs you.
• ✓Keep a 'waiting on reply' category in your scheme; it dovetails with asking Muse to track unanswered threads later.
• ✓If Muse's categories feel generic, feed it five example emails and ask it to name categories from those instead of from scratch.
• ✓Newsletters are best handled last, after the people-mail is filed — it keeps the first pass fast and reviewable.