Meta’s AI agent Muse is mixing up conversations and could be exposing private data, report says
- ID
- 48374
- Status
- summarized
- Published
- 20 Nov 2026, 1:38 AM
- Fetched
- 20 Nov 2026, 4:26 AM
- Provider
- TechCrunch
- Category
- technology
- Original URL
- https://techcrunch.com/2026/11/19/metas-ai-agent-muse-is-mixing-up-conversations-and-exposing-private-data-report-says/
- Source URL
- https://techcrunch.com/feed/
Summary
- Score
- 7.5
- Created
- 20 Nov 2026, 4:27 AM
- Tags
- Audience
- developersai_agent_usersai_ml_learnersfounders
What happened
A Reuters report citing internal Meta posts says Meta's AI agent Muse has been mixing conversations across accounts and surfacing data that didn't belong to the user — including one chat about weather and tides that suddenly appended "two bank updates, your Capital One balance is $2722.58, your Charles Schwab balance is $5899.57." Other employees reported Muse surfacing childcare requests, career advice, and product orders they never made, and one said the agent on her personal phone reminded her to reply to a Signal message from her sister despite her never granting access to other apps. Muse launched in September and has more than 10 million downloads; Meta did not respond to TechCrunch's request for comment.
Why it matters
If you're building an agent with persistent memory or cross-app tool access, this is the two-failure-mode checklist: (1) memory must be namespaced per account so retrieval can't cross user boundaries, and (2) every outbound data source — messaging apps, banking, calendars — needs an explicit, revocable grant the user can see. The report gives no technical root cause, so treat it as a design review prompt, not a diagnosis: go check whether your agent's memory store keys on user ID or on session/device, and whether your permission model is 'asked once at onboarding' or 're-consented per integration.'
Discussion angle
What's your agent's memory keyed on — user ID, device, or session? Walk through what a cross-account leak would look like in your own stack, and whether any of your integrations could fire without an explicit user grant.