How to Use the Android SMS Connector in Muse

1. The short answer

As of October 25, 2026, Android SMS is a live connector in Muse. It has been live since launch day, September 8, 2026, and it is one of the phone only connectors: it lives on your Android phone, and its access is managed in your device settings, not in the connector list on the web. That is why you will not find it in the October counts of the web app, which found 54 connectors on September 30, October 7, and October 15, 2026. Add the phone only connectors and the live total is closer to 58 to 60, with 18 more announced but not yet live. Our Muse connectors list keeps the dated count, including which connectors are phone only and which are announced but not live.

Connect it and Muse can read and send text messages on your Android phone. Ask what arrived, who needs a reply, and what a thread actually says, and get a draft ready to send. It is the texting half of the phone: the messages that arrive as SMS, handled in plain words instead of a crowded inbox.

Here is the honest version, and the limit of what we can verify. Meta's help centre names Android SMS as a connector whose access you manage in your device settings, and independent connector lists describe it as sending and reading text messages. Meta has not published whether RCS messages are included, how group threads are handled, or exactly what the send flow looks like. This guide treats it as SMS, flags the rest as unverified, and tells you to test with a read only request before you let it send anything.

Muse is invite only right now. Need an invite code? Click here to grab one free from the community pool. Waiting on a launch in your country? Join the waitlist and we will send you a fresh code on launch day. Muse is available in the United States, Canada, and Japan.

2. What you need

• Muse access. You need an account with access first, in the United States, Canada, or Japan, where Muse has launched.
• An Android phone with text messaging. Android SMS is Android only. There is no iPhone version of this connector, and no web version. If you use an iPhone, the messaging connectors to look at are the Meta apps and Telegram instead.
• Your default SMS app working. Muse reads the texts your phone already receives. If your messages arrive in your normal SMS app, you are ready. If you use a third party texting app, check that its messages still land in the phone's SMS store, or Muse may not see them.
• Approvals set to ask me. Before you connect anything that can send messages in your name, set approvals so nothing is sent without your tap. This is the single most important step on this page.
• Gmail, optional but useful. Texts plus email is the pairing that catches everything: the short messages on your phone and the long ones in your inbox. Our Gmail connector guide covers that half.
• Google Calendar, optional. Texts often carry plans, and the calendar is where plans live. With both connected, Muse can read a text about Friday and check whether Friday is actually free.

3. How to connect it, step by step

The connection itself takes a few minutes. The setup around it matters more, so run the steps in order and do not skip the approvals step at the end. One honest note first: Meta has not published a step by step connection flow for this connector, so the steps below follow the standard connector flow and the device settings note in the help centre. If a step looks different on your phone, your app version is newer than this guide, and the device settings screen is the place to check.

1. Open Muse on your Android phone. This connector does not exist on the web app, so do this on the phone that holds your texts. If you open Muse on the web and search the connector list, you will not find it there, and that is expected.
2. Go to Settings, then Connectors. Find Android SMS in the list. If you do not see it, check that your Muse app is current, then check again. The connector has been live since September 8, 2026, so an up to date app should show it.
3. Start the connection and grant SMS access in device settings. Android SMS access is granted through your phone settings, not through a web login. Your phone will ask Muse to read and send texts. Grant it, and know what you granted: read access lets Muse catch you up, send access lets it reply, and you want both only with approvals on.
4. Set approvals to ask me. Do this before your first text question. A text sent in your name is a message from you, with your number on it, and it cannot be unsent. Keep approvals on while you learn what the connector does, and keep them on after.
5. Ask a small read only question first. Try something easy to check, like what texts arrived today, or what the latest message from one contact says. Open your SMS app, compare, and confirm it matches. A small verified read builds more trust than a big unverified one.
6. Send one test reply with approval. Pick a low stakes thread, ask Muse to draft a reply, read the draft yourself, and approve it. Watch it land in the thread. Once you have seen the full loop work once, you know what to expect every time after.

4. What it actually does

The value of this connector is not that Muse can read a text. Your SMS app already shows you that. The value is that Muse can triage your texts the way it triages email: what arrived, who needs a reply, and what the thread actually says, without you opening every conversation one by one.

The catch up is the use most people will actually keep. Ask what texts arrived today, or what you missed while you were away from your phone, and Muse gives you the short version: who wrote, what they wanted, and which ones need an answer. It turns a pile of unread badges into a list you can work through in order.

Drafting replies is the second solid use. Tell Muse what you want to say, in your own rough words, and it drafts the text in your voice. You read the draft, you fix anything that sounds off, and you approve it. The draft is the work Muse does. The send is the decision you keep. That split is the whole point of the approvals setting.

Verification codes are a quiet but real use. A code that arrives by text is a text Muse can read when you ask, so you can ask what the latest code from a service is instead of switching apps to find it. Do not ask Muse to read codes out loud in a shared room, and do not forward codes to anyone, but for your own sign in, on your own phone, it saves a round trip.

It also pairs well with the calendar. Texts often carry plans: a time, a place, a change of plan. With Google Calendar connected, Muse can read a text about Friday and check whether Friday is actually free, then draft the reply with the real answer instead of a guess. That pairing is where the connector stops being a text reader and starts being an assistant.

5. What it cannot do

It cannot read messages in apps it is not connected to. WhatsApp, Telegram, Signal, and Messenger are separate connectors with separate permissions. A text in WhatsApp is not a text in SMS, and Muse will not find it through this connector. If a conversation lives in another app, connect that app, or ask about the thread where it actually lives.

It cannot tell you whether a message arrived as RCS. Meta has not published whether RCS is included in this connector, so this guide treats it as SMS and says so plainly. If most of your texting happens over RCS, test it: ask Muse about a recent RCS thread and see whether it can read it. Do not assume coverage you have not verified.

It cannot unsend a text. Once Muse sends a message with your approval, it goes out under your number, and there is no recall. That is why the approvals setting matters more here than on a read only connector. The failure mode you want is a draft waiting for you, not a message already sent to the wrong person.

It cannot fix a wrong number. If you tell Muse to text the wrong contact, or a contact has two numbers and Muse picks the old one, the message goes to the wrong place. Check the recipient in the draft before you approve, every time, especially for contacts you have not texted in a while.

It cannot make texting free. Carrier charges still apply to every text Muse sends for you, the same as texts you send yourself. If you are on a plan with limited texts, or roaming, the cost is yours. Muse does not warn you about that, so check your plan before you start sending in bulk.

6. What to watch for

Check the recipient before every send. This is the single habit that prevents the worst failure of this connector: a personal message to a work contact, or a reply to the wrong thread. The draft screen is your last checkpoint. Use it. Read the name, read the message, then approve.

Keep approvals strict for sending, and keep them strict after the novelty wears off. The temptation, once the connector works well, is to loosen approvals so Muse can reply on its own. Do not. A text is a message from you, in your voice, under your number. The moment you stop reading drafts is the moment a bad draft becomes your words.

Be careful with sensitive texts. Bank alerts, verification codes, medical messages, and anything with a password or a code deserves a human read before any reply goes out, even a drafted one. Set a rule for yourself: Muse drafts, you read, you send. And never ask Muse to forward a verification code to anyone else. A code is yours alone.

Check your data controls. In Muse settings, open Data controls and look at the switch for helping improve the models. If you do not want your chats used for training, turn it off before you start asking Muse to read your texts. That switch controls whether Meta may use your chats to train future models, and private messages are the last chats you want feeding a training set.

Remember this is a phone connector, not a web connector. Disconnecting on the web does nothing, because the access lives in your Android settings. To remove it, manage it on the device that granted it. If you switch phones, expect to grant access again on the new one. And Muse itself is available in the United States, Canada, and Japan only. Outside those three countries, the waitlist is the way in, and this connector waits with everything else until launch day in your country.

Get started

Frequently asked questions

Can Muse send text messages on its own?

It can send texts from the Android SMS account you connect, but nothing is sent without your approval when your approvals are set to ask me. Every send waits for your tap, and you should keep it that way.

Does Android SMS work on iPhone?

No. Android SMS is Android only, and its access is managed in your Android settings. On iPhone, the messaging connectors to look at are the Meta apps and Telegram, and Apple Health is the iPhone device connector.

Can Muse read my WhatsApp messages through this connector?

No. WhatsApp is a separate app with separate permissions, and this connector only covers SMS texts on Android. A message in WhatsApp will not show up through Android SMS.

Can Muse read verification codes from my texts?

Yes, in the sense that a code that arrives by text is a text Muse can read when you ask. Do not ask Muse to forward a code to anyone else, and do not read codes out loud in a shared room. A code is yours alone.

Why can I not find Android SMS in the web app connector list?

Because it is a phone only connector. Its access is managed in your device settings, so it does not appear in the web app count of 54 connectors. That count covers the web app only, and the live total including phone only connectors is closer to 58 to 60.

What happens if I disconnect Android SMS?

Muse loses access to your texts. Your messages stay in your SMS app, and nothing Muse drafted is sent after you disconnect. Manage the connection in your Android settings, where the access was granted.

Built with Muse is an independent community project. Not affiliated with or endorsed by Meta.