How to Use Muse to Summarize Email

Muse, Meta's personal AI agent, connects to the email account you link it to, and Meta's launch material lists working with email among its core abilities — so compressing a 40-message thread or two weeks of unread mail into a digest is exactly the kind of work it is built for. You control the access level: for email you can grant read-only, which is all a summary task needs, and you can change or disconnect access whenever you want. Because Muse works asynchronously, you can request a catch-up digest and close the app while it reads. Two honest caveats: Meta staff have acknowledged the agent sometimes makes mistakes or fails to finish things, so verify names, dates, and amounts against the original thread before acting, and Muse can only summarize mail in the account and folders you actually connected.

• The product is days old — Reuters reports Meta's Vishal Shah admitting Muse will sometimes fail to finish things, so treat long summaries as a first pass.
• Muse can only read what you connected; mail in other accounts or local folders is invisible to it.
• Always double-check figures and dates in a summary before replying, paying, or committing.

1. 1

   Connect your email read-only

   In the Muse app you pick which services to connect and how much access each gets. Read-only is enough for summaries and means Muse physically cannot send or alter anything in the account.

2. 2

   Point it at a specific slice

   'Summarize my email' invites a shallow answer. Name the window and the place: 'the last 14 days in my inbox, including the standing thread with the HOA.'

3. 3

   Define the output shape

   Say who the summary is for and how long: a 300-word digest grouped by project, or a one-line-per-message list ranked by urgency.

4. 4

   State the guardrails in the same message

   Add 'do not mark anything as read, move, or archive anything' so a reading job stays a reading job even if your access settings allow more.

5. 5

   Verify before you act

   Skim the original threads behind anything consequential — a summary that flubs an amount or a deadline is worse than no summary.

A nurse back from a two-week holiday who wants the gist of roughly 300 unread messages before her first shift back.

Catch me up on the 12 days I was out. Read my inbox and summarize what I missed in three groups: things needing a reply today, things I only need to know, and pure noise I can safely ignore. For each important thread give me the sender, a one-line gist, and what the most recent message asked of me. Put anything with a deadline before Friday at the very top. Don't mark anything as read and don't move or archive a single message — just the summary, and keep it under 500 words.

• Which connected account and folders to read

  Muse only sees what you linked; naming the folders stops it from wandering or missing the point.

• The time window

  'While I was away' is ambiguous; 'September 1 to today' gets the exact slice you missed.

• What counts as important to you

  Deadlines, money, family, or a specific project — your definition changes what lands at the top.

• Desired length and format

  A 200-word digest and a full message-by-message log are different deliverables.

• Whether to include attachment contents

  Contracts and invoices often live in PDFs; reading inside them takes longer but catches the details that matter.

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.

• Marking messages as read or archiving anything — A summary should never disturb your mailbox; keep cleanup as a separate, reviewed job.

• Sending any reply Muse offers to draft — Meta says Muse checks before sensitive actions like sending email — keep it that way by reviewing every draft.

• Forwarding your digest to other people — The digest may quote private threads; you should choose what leaves the account.

• ✓Read-only access plus an explicit 'don't change anything' instruction is the safest combination for pure catch-up jobs.
• ✓Ask for thread-level summaries when a conversation is long, and mailbox-level digests when the problem is volume — they are different requests.
• ✓If a digest feels off, ask Muse to quote the exact sentences it based each point on rather than re-summarizing.
• ✓Recurring digests work well as a routine: same window, same format, every morning — but check the first few outputs before trusting them.
• ✓Summaries are one of the lower-risk tasks to hand Muse on day one precisely because nothing gets sent or changed.