This article was written by the AI agent Muse under the author’s direction. The author actually performed the setup and send/receive tests in their own environment and confirmed the results.

Release News

On November 10, 2026, All Things Muse, which covers Muse news, reported that “Muse Mail Is Now Available to Paid Subscribers in the US and Canada.” It cited a post on X from Muse’s official account, with the following content:

Muse has its own email address! Your Muse can now send and receive emails on your behalf, available now for paid subscribers in US and Canada.
(Muse now has its own dedicated email address. It is now available to paid subscribers in the United States and Canada.)

Source:Muse Mail Is Now Available to Paid Subscribers in the US and Canada (All Things Muse)

Muse Mail itself was announced at Meta Connect in September, and its rollout to some users had been reported from around November 6. The latest news made it “officially available to paid subscribers,” but the target regions are said to be the United States and Canada.

From the outset, when Muse became available in Japan on October 23, Meta said regarding Muse’s dedicated email address that “the availability in Japan will be announced separately” (as reported by PC Watch and others). In other words, Japan was never explicitly stated as a target, and it was not mentioned in this news either.

However, when I tested it in Japan, everything worked

Now comes the main point of this article.

The author lives in Japan and is a subscriber to Muse’s Power plan (¥2,799 per month). The official announcement limited availability to the United States and Canada, while Japan remained “to be announced separately.” Taken at face value, Japanese users were not supposed to be able to use it yet.

However, when I actually tried it, everything worked.

• Obtaining an email address: Successful
• Verifying your own address: Successful
• Sending a test email: Successful
• Receiving a reply: Successful

There was no need to wait for the announcement. As of November 11, 2026, Muse Mail is working normally in my environment (Japan, Power plan).

I don't know why it's available. Perhaps the phased rollout had reached Japan as well, or perhaps the regional restriction is merely cosmetic. In any case, “not listed as eligible in the announcement” and “cannot actually use it” seem to be different things. If you're a user of the Power plan in Japan and are interested in Muse Mail, it's worth trying it without waiting for the announcement. This article is a record of that hands-on testing.

What Is Muse Mail?

Meta's personal agent, Muse, has its own mailbox called “Muse Mail.” The agent has an address in the form ○○@muse.ai and can receive and send email independently of the user's email account.

Below is an explanation of the steps from verifying your own address through send-and-receive testing, as well as what changes when an agent can have email, including the limitations.

Setup

Obtaining an Address

When you create a mailbox, one address in the form handle@muse.ai is assigned. The handle is 3–32 characters long and can contain lowercase letters, numbers, and hyphens. The display name can be set separately.

There is one point to note.The address (handle) cannot be changed later(only the display name can be changed). You need to decide on the handle at the outset.

Verifying Your Own Address

Next, register your own email address through the Muse Mail settings screen. A verification code will arrive by email; once you enter it, the address will be verified.

This verification is important. Email from a verified address is treated as “instructions from the account holder.” Put another way, the system is designed so that only the verified account holder can instruct the agent by email. Since email is a medium in which the sender can easily be spoofed, I think this distinction is appropriate.

Send-and-Receive Testing

After verification, I confirmed the following round-trip exchange.

1. Sent a test email from Muse to the user's email address → Received it
2. Replied in that thread → Received on the Muse side and processed as an email from the verified address

In other words, email delivery is working in both directions. Immediately after verification, a welcome email also arrived, notifying me that verification was complete and that I could now use email.

What You Can Do with Email

• Delegate work by forwarding: Forward confirmation emails for reservations or orders to the agent’s address, and the agent will read the contents and handle the follow-up, such as adding it to a calendar or matching it against monitoring targets. You can make a request without even opening chat
• Give instructions or ask questions by email: If you send from a verified address, it will be processed as a request from you
• The agent can send email under its own name: It can send inquiries and communications from the agent’s address instead of the user’s personal address. Replies also arrive in the agent’s mailbox, keeping the entire exchange consistent
• Inboxes are separated: Email addressed to the agent will not be mixed into the user’s inbox

Note that Muse sends email to someone only when the user asks it to. The welcome email also explicitly stated that it would never send email on its own judgment

Limitations

To be honest, there are also some limitations

• Only one mailbox. You cannot create separate addresses for different purposes (for newsletters, sign-ups, etc.)
• It is not a replacement for the user’s email service. It is strictly an agent-only mailbox
• The address (handle) cannot be changed. As mentioned above

Summary

I think “giving an agent an email address” is a subtle but effective extension. Email is a common entry point connected to all kinds of existing services, and simply forwarding a confirmation email lets you give the agent the practical context for the task. It was also a useful reference as a design for expanding the ways an agent can be reached, including using identity verification to determine whose instructions should be treated as authoritative