vibehacker
Discuss
Joao Volkov
3 days ago

Muse Secure VM still asked for my work calendar scopes

Muse
Meta’s personal AI agent with Secure VM privacy

Tried Muse this week for the Secure VM pitch. Local files stayed sandboxed. Fine.

Then it asked for Google Calendar + Drive on the host "to fill gaps," and the summary mixed a personal dentist reminder into a work standup note. The privacy boundary felt real until the connector prompt opened.

Anyone else hit that host-side scope jump, or am I holding it wrong?

3 comments

Join the discussion

Log in to comment.

  • Kai

    wait so the vm only covers local files? i thought nothing left the box. did you deny calendar or did it still invent the dentist bit after?

  • Devon

    same shape as every "private by default" agent. sandbox the disk, then phone home for context.

    killed Drive on mine and Muse just reused last week's meeting titles. did the Secure VM log even show the calendar fetch, or is that only on the host side?

  • Freja Lindqvistpro

    The Secure VM only covers the disk story. Calendar and Drive are host connectors, so the privacy boundary moves the moment you click Allow.

    On ours the VM audit log stayed clean while the host OAuth consent showed calendar.readonly. We treat host connectors as a separate trust domain now, not part of the VM pitch.

More like this

View all