What happened
Meta’s Chrome Web Store listing presents Muse from Meta as a personal AI agent for Chrome. It opens in the browser’s side panel, allowing users to continue conversations alongside the page they are viewing. The listing identifies version 2.0.65, updated November 12, 2026, and shows 90,000 users. The extension is offered by Meta and is 2.29 MiB in size.
The product description says users can hand Muse tasks that involve research, comparisons, follow-up and bookings. Examples include filling out forms, comparing prices, following up on refunds, scheduling around calendar conflicts, making reservations and setting reminders. For shopping, Meta says Muse can track price drops and alert users when an item goes on sale; it can buy on a user’s behalf with approval. These are descriptions of intended use, not measured performance claims.
The listing says users choose which apps Muse can access, naming email, calendar, Instagram, Facebook, health and fitness data, and finances. Meta says users approve actions before they happen, can inspect a full activity log and can revoke any connector at any time. For small businesses, the listing describes connections to Instagram Business Accounts, Facebook Pages and Meta ad accounts, with Muse using business information such as products, brand voice and recurring customer questions. It also describes personal finance and fitness use cases based on data users choose to share.
Meta’s own warning says Muse may be inaccurate or take unexpected actions, and users should check in and intervene as needed. The listing does not state a subscription price or provide a technical account of how the extension interacts with pages. Its privacy disclosure says the extension handles personally identifiable information, health information, financial and payment information, authentication information, personal communications, location, web history, user activity and website content. Meta declares that this data is not sold to third parties outside approved use cases and is not used or transferred for unrelated purposes or creditworthiness decisions.
What the archive adds
New Runtime’s earlier coverage described Muse for Small Business as a cross-service business assistant with an approval gate for consequential external actions (September 30, 2026). The Chrome extension listing is a new fact on the broader Muse story: it describes a browser side-panel surface and additional everyday personal tasks, rather than a restatement of the small-business launch.
Trend signal
This is consistent with the direction described in Agent-ready software exposes capabilities: products are being framed around discrete connected capabilities and permissioned actions. The listing’s revocable connectors and approval-before-action promise fit that pattern, although it does not show how those controls work in practice or how reliably they constrain the agent.
Why now
The listing was updated November 12, 2026, and positions the extension as an interface for bringing Muse into everyday Chrome browsing. The source does not explain why Meta released or updated the extension at this time.
Why it matters
Browser agents encounter the same pages and accounts people use for work, which can make them useful for tasks that cross websites, calendars, email and commerce. That convenience also expands the consequences of granting access: the listing’s disclosed data categories include communications, credentials, financial information, health information and browsing activity. For teams, the central evaluation question is therefore not only whether an agent can complete a workflow, but whether permissions are narrow, actions are reviewable and consequential steps reliably pause for approval.
Meta’s description supplies a useful baseline for that review: named connectors, a revocation mechanism, an activity log and user approval before actions. But those are company-described controls, not an independent security assessment. A team considering a browser agent should test it with low-risk accounts and tasks first, then verify its actual access and action behavior before connecting business-critical data or allowing purchases, bookings or account changes.
Limits and uncertainty
The Chrome Web Store listing is Meta’s product description, not an independent evaluation. It does not establish task success rates, error rates, latency, how approval prompts are triggered, or whether the activity log captures every relevant operation. It does not specify pricing, supported regions, account eligibility, connector-level permissions or technical details of browsing and data retention. The store page reports 90,000 users, but does not define that figure or explain how current it is. Meta explicitly warns that Muse may be inaccurate or take unexpected actions.
Skill to build now
Write a small permission-and-approval checklist for any browser agent your team evaluates: which accounts it can reach, which actions require confirmation, how to review its activity and how to revoke access. Test the checklist with a low-risk workflow before connecting sensitive accounts.
Reader takeaway
Muse’s Chrome listing turns the browser side panel into a proposed home for an agent that can work across connected personal and business services. Its approval, logging and revocation claims are useful evaluation criteria, but teams should verify those safeguards in practice before granting access to sensitive data or consequential actions.