People Are Seeing Meta Muse Get Shut Out of the Web. It Was Built to Look Human, and Websites Noticed.
Meta Muse users say half their browser tasks stopped working this week, just as Cloudflare started blocking AI agents by default and Amazon shut Muse out for hiding that it's a bot.
If this caught your attention, that’s not accidental.
The best editorial systems don’t happen by accident. Outlever builds them.

Jessica Lessin, founder of The Information, posted on X this week that about "half of my Muse use cases have vanished" over the past two days because Meta Muse's browser will no longer complete them. She asked whether websites had changed their policies or whether bot detection was to blame.
Other Muse users are reporting the same thing. Some on Threads say Cloudflare and other CDNs are disrupting Muse traffic, and a few are discussing running the agent through a separate phone to avoid the blocks. Meta has not publicly explained the failures.
Meta launched Muse on September 8. The agent runs in its own cloud virtual machine with a Chromium browser, and it has been downloaded more than 2.5 million times, according to Sensor Tower data cited by Inc. When a service has no API, Meta says Muse uses it through the browser the same way a person would. Those browser-based tasks are the ones users say are failing.
Muse's browser hides that it is automated
Inc.'s Jason Aten examined the shipping version of the app and found that Muse launches Chrome with its automation indicators turned off and hides navigator.webdriver, the standard property that tells a website a browser is being controlled by software. It also generates fake values for things like browser plugins and checks pages for signs it has been detected, including CAPTCHAs and Cloudflare error IDs.
Aten noted that the web is hostile to browser automation in general, and that an agent blocked by bot detection everywhere would be of little use. But techniques like these tend to work only until detection vendors adjust. When they do, an agent that worked one day can be blocked the next, which matches what users are describing.
Cloudflare now blocks agents by default on many sites
On July 1, Cloudflare announced that it would split AI traffic into three categories: Search, Training and Agent. Since September 15, Agent traffic has been blocked by default on ad-supported pages for newly onboarded domains. Sites that already had Cloudflare's older "block AI bots" setting turned on were moved to the same default. Cloudflare's reasoning is that a page carrying ads was built to be visited by people.
In October, Cloudflare's AI bot directory added a named entry for Meta Muse, according to TechnologyChecker, which tracks the list. Once Cloudflare can classify traffic as Muse, any site set to block agents will block it automatically. State of AI could not confirm that this caused the failures users are reporting, but the timing lines up.
Retailers are pushing back
Amazon began blocking Muse on the night of September 20. Muse users who try to shop there now see a popup saying unauthorized agent access violates Amazon's Conditions of Use. Amazon said Meta never told it Muse would access the store, that the agent does not identify itself while browsing, and that it appeared able to capture and store customer credentials. Amazon's terms, updated in August, require agents to identify themselves in every request.
Amazon is relying on its terms and technical blocks after losing an injunction against Perplexity at the Ninth Circuit, which found that the user, not the AI company, was the one accessing Amazon's site.
Amazon is not the only one. NBC News tested Muse at several large retailers and found that some blocked it, including companies Meta has named as partners.
Agent behavior is drawing scrutiny
The blocks come as security researchers document agents misbehaving online. In late September, the research lab Transluce published evidence of autonomous agents using a URL-scanning service to get around access restrictions, including cases where agents looked for other ways into a site after bot protection blocked them. On October 1, BleepingComputer reported that autonomous agents attempted intrusions on U.S. and Canadian government websites. Reports like these give site operators more reason to restrict automated traffic, whether or not a particular agent is at fault.
Where Muse still works
Muse has official access in some places. Shopify opened its checkout to Muse through Shop Pay, and Meta has named Walmart, Best Buy, Wayfair, Sephora, Gap and Expedia as partners, though not all of those integrations are live yet. Industry groups are also working on Web Bot Auth, a draft IETF standard that would let agents cryptographically sign their requests so websites can verify who they are.
Agents that reach sites through APIs, partnerships or verified identity are less likely to be affected by changes in bot detection. Agents that rely on a browser presenting itself as a human user are more exposed.
What enterprises should do
Companies using browser-based agents for business tasks should avoid relying on them for critical workflows on sites they do not control, since access can be cut off without any change to the agent. APIs and formal integrations are more stable, and anything involving purchasing or procurement should have a fallback.
Buyers should also ask agent vendors how their products identify themselves to websites. An agent that conceals its identity can put the customer in breach of a site's terms of service, not only the vendor.
Companies that run their websites on Cloudflare should review their Agent setting. Many may now be blocking their own customers' agents by default without having made that choice.
If this caught your attention, that’s not accidental.
The best editorial systems don’t happen by accident. Outlever builds them.


Get the latest AI insights first.
Sign up for updates, interviews, and fresh analysis on how AI is reshaping business, brands, and technology.





