How to Use the Tailscale Connector in Muse

1. The short answer

As of October 25, 2026, Tailscale is a live connector in Muse. It connects Muse to your private network, the set of your own machines linked by Tailscale, so Muse can reach your home computer, your server, or your work machine from a chat. That is the whole idea: Muse stops being limited to the public internet and starts being able to reach the machines you own.

Tailscale was live at launch on September 8, 2026, named by Alexandr Wang that day among the launch connectors, and it was still counted among the 54 connectors in the web app in the October 15 in app check. There has been no October announcement changing how it works. It is one of the strangest connectors on the list, and one of the most powerful for people who run their own machines, because it turns a chat into a remote control for your own network.

Here is the honest version. Most connectors plug Muse into a service someone else runs. Tailscale plugs Muse into your own stuff. Your home server. The computer in your office. The little machine running your home automation. You ask Muse to check on a machine, run something on it, or fetch a file from it, and Tailscale is the private road it travels on. The rest of this guide covers how to connect it, the setup that keeps your network safe, the uses that are actually worth your time, and the limits to know before you open the door.

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.
• A Tailscale account and a tailnet. A tailnet is your private network of machines. If you do not have one yet, set it up first and add at least one machine to it before you connect Muse.
• Tailscale installed on the machines you want Muse to reach. Every machine you want Muse to touch needs the Tailscale app installed, signed in, and online. A machine that is asleep or offline cannot answer.
• Approvals set to ask me. Before you connect anything, set approvals so nothing runs on your machines without your tap. This is the single most important step on this page, because this connector reaches into your own network.
• A clear list of what Muse may touch. Decide before you connect: which machines are in bounds, and which are not. Write it down. Vague access is how accidents happen.

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.

1. Set up your tailnet first. Create your Tailscale account, install Tailscale on the machines you want Muse to reach, and confirm they can see each other. If the machines cannot reach each other, Muse will not be able to reach them either.
2. Open Muse and go to Settings. The connectors list lives there. What is printed there is what your account has, because rollout is staged and two accounts can see different lists on the same day.
3. Find Tailscale in the connectors list and open it. If Tailscale is not listed, your account has not received it yet. There is nothing to install and nothing you broke. Check again in a few days.
4. Sign in to Tailscale. Use the Tailscale account that owns your tailnet. Remember this is the network the connector will use, so sign in with the right account the first time.
5. Grant the access Muse asks for. Muse needs permission to reach machines on your tailnet. Read the permission screen before you accept it. If a scope surprises you, stop and check what it covers before continuing.
6. Set approvals to ask me. In Muse settings, set approvals so that anything that runs on your machines always waits for you. This is what stops Muse from ever running a command you have not read.
7. Test with a read only request. Ask Muse to list the machines on your tailnet, or check whether one machine is online. Read the answer against what you know is true. If it matches, the connection is good. Do not ask it to run anything on the first day.

Copy this prompt

You are my network assistant. Use my Tailscale connector only.
Rules: you never run a command, change a setting, or delete a file on any of my machines without my explicit approval. You check, you report, you propose. I approve every action.
Machines you may look at: [list them by name]
Machines you must never touch: [list them by name]
First, do this in order.
1. List the machines on my tailnet and tell me which ones are online right now.
2. For each online machine, tell me what you can see about it.
3. End with anything that looks wrong, and what you would check next.
Do not run anything. Do not change anything.

4. What it actually does

The connector earns its place with four uses. Everything else is a variation on one of them. One honest note first: Meta has not published a detailed description of what the Tailscale connector can do inside Muse. What follows is built on the launch announcement, which names Tailscale among the launch connectors, and on independent connector lists, which describe it as managing a tailnet from chat and reaching devices on your private network. Where a capability is not confirmed, this guide says so.

See your machines from a chat

This is the simplest use and the one to start with. Ask Muse which machines on your tailnet are online, which ones have gone quiet, and when each was last seen. For anyone running a home server, a media machine, or a small office network, this turns a check you would do in a dashboard into a question you can ask from your phone. The value is not the list itself. The value is noticing the machine that dropped off the network before you needed it. A backup machine that has been offline for a week is a backup that does not exist, and a chat check once a day catches that.

Reach your own machines from anywhere

Without Tailscale, your home computer is reachable only when you are on the same network or after a fiddly remote setup. With the connector, Muse bridges that gap: you talk to Muse from anywhere, and Muse reaches the machine through your private network. Ask it to check whether a download finished, look for a file, or tell you how much disk space is left. The machine never has to be exposed to the public internet, because Tailscale keeps the traffic inside your private network. That privacy is the point. You are not opening a port to the world. You are giving your own agent a key to your own front door.

Manage the tailnet itself

Independent connector lists describe this connector as managing a tailnet from chat. In practice that means the admin jobs around your network: seeing devices, checking who has access, and spotting the machine you forgot you added. If you share a tailnet with family or a small team, this is how you keep track of who can reach what without opening the admin console every time. Say plainly what you want done and check the result before you approve the next step, because network changes are the kind of change that locks you out if they go wrong.

Pair it with the tools on your machines

Tailscale is a road, not a destination. Its value grows when the machines at the end of the road run something useful. A home server with your files. A machine running a coding agent. A computer with a project on it. The connector lets Muse reach those machines, and what Muse can do there depends on what is running on them. Our complete connectors list shows the other connectors Muse can pair this with, and our Zapier connector guide covers the automation side for the many apps Tailscale does not reach. Think of Tailscale as the private half of your Muse setup, and the cloud connectors as the public half.

5. What it cannot do

The limits are honest and worth knowing before you lean on the connector.

• It cannot reach a machine that is off or asleep. A sleeping computer cannot answer, and a machine with Tailscale closed is not on your network. If you need Muse to reach a machine reliably, turn off sleep on that machine while you use this connector.
• It cannot fix a broken tailnet. If your machines cannot see each other in Tailscale itself, Muse cannot magically connect them. Fix the network first, in the Tailscale app, and only then ask Muse to use it.
• It cannot see machines outside your tailnet. Muse reaches what you connected, nothing more. A computer that was never added to your tailnet is invisible to it, and that is a feature, not a bug.
• It cannot guarantee a command is safe. A command Muse runs on your machine runs with real effect: files move, settings change, things get deleted. Read every command before you approve it, and never approve a command you do not understand on a machine that holds anything you care about.
• It cannot replace your own network security. The connector is only as safe as your tailnet. If anyone else can sign in to your Tailscale account, they can reach the same machines. Use a strong password, turn on two step sign in for Tailscale, and review who has access to your tailnet regularly.

6. What to watch for

As of October 25, 2026, Tailscale is a settled connector: live since September 8, still counted among the 54 connectors in the web app in the October 15 in app check, with no October update to how it works. The thing to watch is not the connector changing. It is the access you granted. A connector that can reach your own machines is the most powerful one you will connect, and the most dangerous one to set up carelessly.

Start read only and stay read only for the first week. Ask Muse to list machines, check status, and report what it sees. Do not ask it to run commands, change settings, or delete files until you have watched it report correctly for days. When you do start approving actions, approve one at a time, and read the exact command before you tap yes. A vague approval like do what you need to on my server is how a small job becomes a big mess.

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 about your machines. That switch controls whether Meta may use your chats to train future models. And remember that disconnecting is always an option: you can disconnect Tailscale at any time in Settings under Connectors, and Muse stops reaching your network the moment you do.

Finally, keep a list of what is on your tailnet and review it monthly. Old machines, ex colleagues, and forgotten test devices accumulate, and each one is a door into your network. If a machine no longer needs to be there, remove it from the tailnet. The safest network is the smallest one that still does the job.

Get started

Frequently asked questions

What does the Tailscale connector do in Muse?

It connects Muse to your private Tailscale network, so Muse can see and reach the machines on your tailnet from a chat. Independent connector lists describe it as managing a tailnet from chat and reaching devices on your private network.

Do my machines need to be on to use the Tailscale connector?

Yes. A machine that is off, asleep, or has Tailscale closed cannot answer. Turn off sleep on any machine you need Muse to reach reliably.

Can Muse run commands on my computer through Tailscale?

That is the use this connector is built for, but nothing runs without your approval when your approvals are set to ask me. Read every command before you approve it, and keep the connector read only for the first week.

Is my tailnet exposed to the public internet?

No. Tailscale keeps traffic inside your private network. Muse reaches your machines through your tailnet, not through a public port. Keep your Tailscale account locked down with a strong password and two step sign in.

Can I use the Tailscale connector outside the United States, Canada, and Japan?

Not yet. Muse itself has launched in the United States, Canada, and Japan only. Join the waitlist and we will send you a fresh code on launch day in your country.

What happens if I disconnect Tailscale?

Muse loses access to your tailnet at once. Your machines and your Tailscale setup stay exactly as they were, and nothing Muse saw is shared onward. You can reconnect the same account later.

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