Muse sharing is paused

The short answer

Meta paused Muse chat and artifact sharing on October 20, 2026, after the security firm Claroc demonstrated that shared Muse chats could be discovered at scale through public DNS records. Claroc calls the research GhostShares. The share addresses Muse generated were built from conversation titles, and because DNS records are public, the researchers could list more than 6,800 shares without ever being sent a link. Anyone holding one of those addresses could open the chat or artifact it pointed to, with no sign in, because that is how share links are meant to work. Meta spokesperson Tracy Clayton told The Verge and Ars Technica on October 20 that the company had paused the sharing feature while it reviews how the links can be discovered. Claroc rechecked 40 previously open shares the same day, and none of them opened. As of October 21, sharing remains paused and Meta has announced no date for its return. This guide explains how the discovery worked, what was and was not exposed, and the steps worth taking if you ever shared a Muse chat.

What happened?

Sharing is how Muse users pass work around. Finish a chat, build an artifact, tap share, and Muse creates a web address you can send to anyone. The person opening it needs no Muse account and no sign in. The content simply loads. It is the same pattern as a shared document link, and until this week it was one of the ordinary ways people showed what Muse had made for them.

On October 18, 2026, Claroc, a security firm, published research it calls GhostShares. The firm reported that it had found more than 6,800 shared Muse chats and artifacts without receiving a single link from anyone. The trail was the address system itself, which the next section explains. The risk in the finding is plain: a share link opened the full conversation or artifact for whoever held it, and conversations can hold drafts, plans, documents and personal details.

On October 20, Meta acted. Spokesperson Tracy Clayton confirmed to The Verge and Ars Technica that Meta had paused the chat and artifact sharing functionality while the company reviews how the links can be discovered. The same day, Claroc rechecked 40 of the shares it had previously found open, and not one of them loaded. The pause, in other words, is real and total: at the time of writing, Muse users cannot create new shares, and addresses created earlier no longer open. Coverage followed the same day, and the story spread quickly for a simple reason: Muse is an agent that holds real work, so its sharing layer carries more than an ordinary chatbot window would.

How could strangers find shared chats?

The weak point was the shape of the addresses. When Muse created a share, the web address it generated was built from the title of the conversation. Titles are words, and words are guessable in a way that random strings are not. Worse, the addresses lived in public DNS records. DNS is the internet directory that turns names into destinations, and its records can be listed by anyone who knows how to ask. Claroc researchers worked through those records and assembled a directory of live Muse shares, more than 6,800 of them, without any access to Meta systems.

Two design choices combined into the hole. The first is that a share link is a key: whoever holds it gets in, with no account check behind it. That choice is common across the industry and is usually safe, because the second choice normally protects it: the link itself is a long random string nobody can guess or list. Muse share addresses failed the second test. A name built from a conversation title can be enumerated, and public DNS records did the enumerating. The standard fix for this class of problem is an address nobody can predict or list. Meta has said only that it is reviewing how the links can be discovered, and has given no detail of the change it will ship.

What was actually exposed?

Only what people shared. The research did not touch private, unshared conversations, and nothing in the Claroc findings or in Meta’s response describes messages, photos or files that stayed inside an account. If you never used the share button, this story does not reach your chats.

What a share exposed was the shared item itself, in full: the whole conversation or artifact the link pointed to. That is narrower than an account breach and wider than many sharers assumed. People share chats the way they share screenshots, quickly and socially, and a chat can carry far more than its title suggests: names, addresses, business plans, financial figures, health details, drafts of messages never sent. Whether any given share held anything sensitive depended entirely on what its owner had put in it. Claroc counted more than 6,800 discoverable shares. What fraction held sensitive material is not a number anyone has published.

What does a Muse share show?

A share is not a summary or a screenshot. It is the conversation itself, presented as a page: your messages and Muse replies in order, and any artifact the chat produced, such as a document, a plan, a page or a piece of code, in the form Muse made it. Whoever opens the address sees the exchange the way you saw it, including the parts you scrolled past and forgot were there.

That completeness is what made sharing useful, and it is what made this week’s finding sting. People share agent chats precisely because the agent holds context: the brief, the figures, the drafts, the reasoning. A screenshot crops that context away. A share carries all of it, which is why the rule from here on is simple: before you share a chat, read it the way a stranger would, top to bottom, and share only what survives that reading.

Was your Muse account hacked?

No, and the distinction matters. Nothing in the GhostShares research or in Meta’s statements points to accounts being broken into, passwords being taken, or sign in security failing. The researchers never entered anyone’s account. They read shares that were reachable by address, the way you would read a document whose link someone had posted. Your account credentials, your private chats and your connected apps were not the subject of this finding. The exposure sits one layer out: content a user chose to share was easier for strangers to find than anyone understood.

It is also why there is no recovery step to run. Breaches ask for password changes and account reviews because the attacker got inside. Here nobody got inside anything. The door that failed was a display window, and Meta has closed it while it rebuilds the frame.

What should you do now?

There is nothing to click and nothing to reset. The practical steps are about memory and habit, and they are short.

• Remember what you shared. Think back over the chats and artifacts you sent links to since you joined Muse. Anything in them should now be treated as content that may have been read by strangers during the window when the links could be discovered.
• Do not panic about the account itself. Your password and your private, unshared conversations were not part of this finding, and there is no password change or account step Meta has asked users to take.
• Plan an audit for the day sharing returns. When Meta switches sharing back on, check your shared items and delete any share whose contents you would not post in public. Until the company explains its fix, treat every new share address as findable.
• Never share a chat that holds credentials. Passwords, financial account details, home addresses, customer information and private documents do not belong in a shareable chat, in Muse or anywhere else. If Muse needs such details for a task, give them in a chat you will never share, and remove them when the job is done.
• For businesses, write the rule down. A share link is a publication. The business risk checklist on this site now carries this incident in its file, with the standing control: customer data stays out of shared chats, full stop.

If you shared something genuinely sensitive, work through the consequences service by service: a password that appeared in a shared chat should be changed at that service, a financial detail watched, a private plan treated as known. The window was short and the audience was whoever went looking, but the safe assumption is the one that costs least: shared meant readable.

When will Muse sharing come back?

Meta has not said. The company’s position, given on October 20, is that the feature stays paused while it reviews how share links can be discovered. Product pauses of this kind usually end quietly, with the feature returning under a new address system and no announcement beyond a line in release notes. Until it returns, the workarounds are the old ones: screenshots for single answers, copied text inside a message, and artifacts exported as files and sent directly. This guide will be updated when sharing returns or when Meta publishes what it changed. When the feature does return, expect the addresses to look different: long, random and impossible to list, which is the whole point of the repair.

Get started

Frequently asked questions

Is Muse sharing still paused?

Yes, as of October 21, 2026. Meta paused chat and artifact sharing on October 20 while it reviews how share links can be discovered, and it has announced no date for the feature to return. Links created before the pause no longer open.

Were private Muse chats exposed?

No. The GhostShares research covered only content users had shared through the share feature, more than 6,800 chats and artifacts. Conversations that were never shared were not part of the finding.

Was my Muse account hacked?

Nothing in the research or in Meta’s response points to accounts being broken into or passwords being taken. The researchers found share addresses through public DNS records and read what those addresses opened. Account security was not the subject of the finding.

Do my old Muse share links still work?

No. Claroc rechecked 40 previously open shares on October 20, 2026, the day Meta paused the feature, and none of them opened. Treat old links as dead, and treat anything they contained as content that may have been read while discovery was possible.

What should I do about chats I already shared?

Work back through what you shared and assume it could have been read. Change any password that appeared in a shared chat at the service it belongs to, and when sharing returns, delete shares whose contents you would not post in public.

Can I still use Muse normally?

Yes. The pause covers the sharing feature only: creating share links and opening them. Chatting with Muse, building artifacts and using connected apps are unaffected, and Meta has announced no other restriction connected to the GhostShares finding.

When will Muse sharing return?

Meta has given no date. The company says the pause lasts while it reviews how the links can be discovered. The standard fix for this problem is share addresses that are random and unlistable, and the feature is expected to return only once Meta is satisfied with its replacement.

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