Verdict first: install it only after you decide which logged-in sites Muse may use. Meta's help page says Muse can use any site you are already logged into, and tells you to log out of the accounts you want kept out before you connect the extension. That one rule, not the 200,000-user count, is the decision in this post. Start with a low-cost public page, check that the approval prompt appears, and read the activity log after. This site rechecks the two open items below, a general region list and an independent safety test, on November 27, 2026.
What we checked / What we could not verify
A standing box for this launch, placed here so the dated record sits next to the headline. Last updated November 20, 2026, from the sources listed at the end of this post.
- Confirmed, read in full on November 20, 2026: the Chrome Web Store listing for Muse from Meta. It shows 200,000 users, 4.6 stars, 237 ratings, version 2.1.9, updated November 19, 2026, size 2.37 MiB, offered by Meta Platforms, Inc., in 42 languages. No general region or country list appears on the listing. The only region wording on it is for one paid feature set, covered below.
- Confirmed, read in full on November 20, 2026: a Meta Help Center page titled How your Muse agent browses the web. It has a Chrome Extension section with the cannot-see list, the logged-in site rule, the ads warning, and the take-control steps used in this post. The page shows only Updated: a week ago. No exact publication date appears on it.
- Timeline, from a full read of Digital Trends on November 19, 2026: TestingCatalog first spotted the Web Store listing on November 13, before Meta said anything in public. Alexandr Wang announced the extension in an X post dated November 20, and Digital Trends reports that he called the announcement belated and said the extension was available now. This site did not read Wang's post directly. X returned a 403 error on November 20, so the post is used here only as Digital Trends reported it, not as a direct quote.
- Corroboration, from a full read of The Next Web on November 20, 2026: TNW repeats Wang's November 20 announcement, the 200,000-user figure, the own-tab-group scope, the cannot-see list, and the unexpected-actions and Google-account warnings. TNW gives no tested safety verdict of its own, and cites no Meta blog or press post for the launch. The corroboration strengthens the launch record. It does not close the independent-test gap below.
- Not found on November 20, 2026: an announcement on about.fb.com or ai.meta.com about the extension, and a CNET or Verge article dated November 19 or 20 giving a safety verdict on it. DuckDuckGo searches for both came back with older, general Muse coverage and a Verge hub page last updated November 18 with no extension entry.
- Still open, recheck dated November 27, 2026: a general region list for the extension, and an independent safety verdict from a named outlet that tested it. Neither exists in the record checked on November 20.
How the extension works, on Meta's own pages
Open Muse in Chrome's side panel without leaving the page you are on. The listing gives two ways in: press Alt+Shift+C, or click the Muse icon in the toolbar. The extension requires Chrome 137 or later, and the listing says browser use in Chrome works best with a Muse account.
Ask Muse to do the browsing and it takes action in your personal Chrome, not in a separate browser of its own. That sentence is the whole design, and it cuts both ways. Muse opens its own tabs in a group, so you can watch it work, and Meta's help page says Muse can take actions only in those tabs. Work outside that group is outside its reach, on Meta's account. Work inside that group runs with your Chrome, your sessions, and your logged-in state.
The listing's own task list is ordinary busywork: filling out forms, comparing prices, following up on refunds, booking trips. One line carries the only region statement in the record. For paid subscribers in the U.S., Muse can also handle shopping, travel bookings, and phone calls. Read that line at its exact width. It assigns the shopping, booking, and calling work to paid subscribers in the United States. It does not say the extension itself is United States only, and no source checked on November 20 says that either.
What Muse can use in your browser
The widest fact in this record is one sentence on Meta's help page. Muse can use any website that you are already logged into, without asking for your login details again.
That is the feature. It is also the exposure. A bank tab, a work inbox, a medical portal, and a shopping account are all the same kind of object to this rule: a site where your browser is already signed in. Meta's help page gives the matching instruction in plain terms. To keep Muse out of accounts you do not want it to use, log out of them before you connect the extension. The logout has to happen first, on the user's side. No setting in the sources checked offers a per-site block list instead.
Meta's help page adds two smaller mechanics. Credentials sit in a Secure Credentials Store, and Muse can use them without the AI model seeing information like passwords. Muse may also accept essential cookies on third-party websites while it browses. Both points come from the help page. Neither appears in the Web Store overview, and no source checked explains which sites trigger the cookie point.
The Web Store privacy page and the Web Store overview do not say the same thing in the same words, and a careful reader should hold both. The overview says Muse cannot access your saved passwords, browser history, or Chrome settings. The privacy page, read in full on November 20, lists the data the extension handles, and that list includes web history and authentication information among its nine categories: personally identifiable information, health information, financial and payment information, authentication information, personal communications, location, web history, user activity, and website content. A Chrome Web Store privacy disclosure is a broad handling declaration, not a claim that Muse reads your history file. Still, the two pages sit side by side on the same listing, and Meta has not, in any source checked, explained how the cannot-access line and the handles-web-history line fit together. That gap is printed here as a gap, not smoothed over.
What Muse cannot see, as Meta states it
Three items, stated the same way on the listing and on the help page: your saved passwords, your browsing history, and your Chrome settings. A fourth protection covers the page in front of Muse. Passwords on a webpage are removed from the text before Muse reads it, per the help page.
Those are Meta's statements about its own product. No independent test of the cannot-see list was found on November 20. CNET and The Verge, the two outlets this site checked first for a tested verdict, had published no extension safety article dated November 19 or 20 in the searches run that day. Digital Trends, read in full, describes the launch and repeats Meta's warnings. It gives no tested verdict of its own. Until an outside test exists, the cannot-see list stands in this record as a vendor claim, clearly labelled, not as a checked fact about every site and every version.
The controls, and how to take the browser back
The listing groups its controls under two headings, and the wording is specific enough to check against your own install.
Approve before action. The listing says you can approve actions before they happen, review what Muse sends and spends, and step in at any time. If Muse is using a service on your behalf, it will ask you before it does anything that may cost you money. The help page adds where the default lives: approval defaults are managed by the Web access default setting, in Permissions under Settings.
Activity log and revocation. The listing says Muse keeps a full activity log so you can review every action it takes, and that you can revoke any connector at any time.
Taking control back takes one of three moves, per the help page: click on the page, press Esc, or move the tab out of the Muse group of tabs. Moving the tab is the most final of the three, because the group is the boundary Meta itself states. A tab outside the group is a tab Muse cannot act in.
Meta warns, as Digital Trends reported it on November 19, that Muse may take unexpected actions in the browser. The help page adds a second cost that is easier to miss. Muse's activity may show up in your Google account and browsing history, and may affect the ads, recommendations, and content you see on and off Meta Company Products. A price comparison Muse runs for you on Tuesday can shape the ads served to you on Friday, on Meta's own statement. Readers who install the extension for one private task should weigh that sentence before the task, not after.
The privacy declarations on the listing
Chrome requires developers to declare how they handle data, and Meta's declarations on this listing are three negatives. User data is not sold to third parties outside the approved use cases. It is not used or transferred for purposes unrelated to the item's core functionality. It is not used or transferred to determine creditworthiness or for lending purposes.
Declarations are not audits. They are the developer's own statements, filed on the store page, and Chrome's listing presents them as such. They belong in the record because a reader deciding whether to install is reading exactly this page. They do not answer the web history question raised in the field note above, and this post does not use them to close it.
What a first session should look like
Start with a site where a mistake costs little. A price comparison on a public store page uses the tab group, the browsing, and the reporting back, and it touches no account you care about. Watch whether the approval prompt appears before Muse acts, and read the activity log afterward while the session is still fresh in your mind. The log is only useful as a control if you learn its shape on a task you already understand.
Log out of the accounts you do not want touched before that first session, not after. Meta's own instruction puts the logout before connecting the extension. Then, if the work goes well, sign back into one account at a time as a task needs it. That order is slower. It is also the only order the help page describes.
Records this post does not change
Three standing records sit near this launch and none of them moves. Consumer Muse pricing is still free, with Power at $20 a month and Maximum at $100 a month. The paid subscriber line on the extension listing fits inside that record and adds no new tier or price. Spaces sharing is still not live: Meta described it on November 6 as exploring ways to share, and Digital Trends noting that custom Spaces can be built in the Muse app is a building fact, not a sharing launch. Try On, announced November 18, still has no Meta detail post on region, price, platform, or steps. An extension launch answers none of those rows.
One separate feature was confirmed on November 20 and belongs in the dated record, not in the Chrome record. Meta's Help Center page titled About Muse email addresses confirms that Muse can have its own @muse.ai address, set up in the Muse app, separate from your personal email, with approval asked before Muse sends. The page was read in full on November 20. Its stated update time is about a week earlier, so November 20 is when the coverage surfaced, not a proven launch date, and no rollout scope is confirmed in that read. The email confirmation changes no permission, price, or control stated for the Chrome extension.
The question for readers
If you have installed the extension, which logged-in site did you let Muse use first, and did the approve-before-action prompt appear before it acted? Answers that name the site type and say whether the prompt appeared will be published as the follow-up to this post, with the November 27, 2026 recheck as the latest date for the first batch.
Quick answers
What is the Muse Chrome extension?
An extension called Muse from Meta on the Chrome Web Store. It puts Muse in Chrome's side panel, and Muse browses in your personal Chrome, opening its own tabs in a group and acting only inside those tabs, per Meta's help page.
When did it launch?
TestingCatalog spotted the Web Store listing on November 13, 2026, per Digital Trends. Alexandr Wang announced it on November 20, 2026, in a post Digital Trends describes as belated. The listing itself was last updated November 19, 2026, to version 2.1.9.
How many people use it already?
The Web Store listing showed 200,000 users on November 20, 2026, with a 4.6 star rating from 237 ratings. Wang's announcement used the same 200,000 figure, as Digital Trends reported it.
What can Muse not see in Chrome?
Saved passwords, browsing history, and Chrome settings, per both the Web Store listing and Meta's help page. Passwords on a webpage are removed from the text before Muse reads the page, per the help page. No independent test of this list was found on November 20, 2026.
Which sites can Muse use?
Any website you are already logged into, without asking for your login details again, per Meta's help page. To keep Muse out of an account, log out of it before connecting the extension.
Where is the extension available?
No general region list is stated on the Web Store listing or in any source checked on November 20, 2026. The only region wording in the record is that paid subscribers in the U.S. can have Muse handle shopping, travel bookings, and phone calls.
Frequently Asked Questions
Q: How do I open Muse in Chrome?
A: Press Alt+Shift+C, or click the Muse icon in the toolbar, per the Web Store listing. The extension requires Chrome 137 or later. Meta's help page gives the setup route as asking Muse in Chat to download the Chrome Extension, then signing in to your Muse account.
Q: How do I stop Muse while it is browsing?
A: Click on the page, press Esc, or move the tab out of the Muse group of tabs, per Meta's help page. Moving the tab out is the strongest of the three, because Meta states Muse can act only inside its own tab group.
Q: Does Muse ask before it spends money?
A: The Web Store listing says Muse will ask you before it does anything that may cost you money when it is using a service on your behalf, and that you can approve actions before they happen and review what Muse sends and spends. Approval defaults are managed by the Web access default setting in Permissions under Settings, per the help page.
Q: Can I see what Muse did in my browser?
A: The listing says Muse keeps a full activity log so you can review every action it takes, and that you can revoke any connector at any time. The help page also warns that Muse's activity may show up in your Google account and browsing history.
Q: Will using the extension change the ads I see?
A: It can, on Meta's own statement. The help page says Muse's activity may affect the ads, recommendations, and content you see on and off Meta Company Products.
Q: Has an independent outlet tested whether the extension is safe?
A: No tested safety verdict was found on November 20, 2026. DuckDuckGo searches found no CNET or Verge article on the extension's safety dated November 19 or 20, and the Verge Muse hub read that day was last updated November 18 with no extension entry. Digital Trends covered the launch in full on November 19 and gave no tested verdict. This site rechecks on November 27, 2026.
Sources
- Chrome Web Store, listing for Muse from Meta, offered by Meta Platforms, Inc. Read in full on November 20, 2026, including the expanded overview and the privacy page. Basis for: 200,000 users, 4.6 stars, 237 ratings, version 2.1.9 updated November 19, 2026, 2.37 MiB, 42 languages, the side panel and Alt+Shift+C wording, Chrome 137 or later, forms, price comparison, and refund follow-ups, the paid subscribers in the U.S. line for shopping, travel bookings, and phone calls, the cannot-access line for saved passwords, browser history, and Chrome settings, the approve before action and activity log and revoke wording, the nine data categories on the privacy page, and the three developer declarations on sale, unrelated use, and creditworthiness or lending. No general region statement appears on the listing.
- Meta Help Center, How your Muse agent browses the web. Read in full on November 20, 2026. The page shows Updated: a week ago and no exact publication date. Basis for: the Chrome Extension section, Muse browsing in your personal Chrome in its own tab group and acting only in those tabs, the setup route through Muse in Chat, the cannot-see list, webpage passwords removed before Muse reads a page, use of any site you are logged into without asking for login details again, the logout-before-connecting instruction, the Google account and browsing history and ads and recommendations warning, the click, Esc, and move-the-tab take-control steps, the Secure Credentials Store point, essential cookies, and the Web access default setting in Permissions under Settings.
- Digital Trends, Anvinraj Valiyathara, Meta is putting Muse in a Chrome sidebar, and the official announcement just arrived, November 19, 2026, 9:49 PM. Read in full on November 20, 2026. Basis for: TestingCatalog spotting the listing on November 13, Wang's November 20 announcement described as belated and as saying the extension was available now with 200,000 users, and corroboration of the side panel, personal Chrome, tab group, cannot-see list, logged-in sites, approval, activity log, revocation, take-control steps, unexpected actions warning, and ads warning. No safety verdict appears in the article.
- Alexandr Wang, X post on the Chrome extension, dated November 20, 2026 as embedded by Digital Trends. Not read directly by this site: X returned a 403 error on November 20, 2026, and a mirror and search snippet carrying the same text are snippet and mirror level only. Used here only through the Digital Trends report above. No direct quotation from the post is printed in this post.
- DuckDuckGo checks, November 20, 2026. Searches covered a Meta announcement on about.fb.com and ai.meta.com, CNET and Verge extension safety coverage dated November 19 and 20, and the Wang post. Results: no Meta announcement post on the extension found, only the Help Center page above; no CNET or Verge safety article in that window found; the Verge Muse hub, read in full, was last updated November 18, 2026 with no extension entry. A tbreak.com snippet claiming version 2.1.9 was updated November 20 conflicts with the Web Store listing read in full, which says November 19, and the snippet is not used.
- The Next Web, Ana Maria Constantin, November 20, 2026. Read in full on November 20, 2026. Basis for: corroboration of Wang's November 20 announcement, the 200,000-user figure, the own-tab-group scope, the cannot-see list, and the unexpected-actions and Google-account warnings. No tested safety verdict and no Meta blog or press primary appears in the article.
- Meta Help Center, About Muse email addresses. Read in full on November 20, 2026. The page states it was updated about a week ago. Basis for the records paragraph only: Muse can have its own @muse.ai address, set up in the Muse app and separate from the user's personal email, users can forward selected emails to it, Muse asks approval before sending, an external email the user owns can be verified, sending limits apply, the address is for individual communication and not bulk, and deleting the address, resetting, or deleting the account loses access. No rollout scope is stated in the read used here.
- This site's standing records, unchanged by this launch: consumer pricing free, Power at $20 a month, Maximum at $100 a month; Spaces sharing still not live; Try On announced November 18, 2026 with no Meta detail post on region, price, platform, or steps. The September 2026 baseline research this site works from predates the extension and contains no record of it.
Comments