Meta has given Muse a soft, cheerful mascot named Jolly, making its personal AI agent look more like a companion than a piece of enterprise software. That design can make an unfamiliar product easier to approach, but it can also soften the moment when users decide how much personal information to share.
The concern is illustrated in Victoria Song’s account of testing Muse. She found herself more willing to continue sharing health context after her personalized agent transformed into a cute cat-shaped character, even though the first workout advice had not impressed her.
Song also saw Jolly used throughout Meta Connect, including demonstrations that paired Muse with smart glasses. The mascot’s job is clear: turn a complex agent that can read, remember and act into something friendly enough to invite into everyday life.
Don’t miss the best of The Mac Observer
Set us as a preferred source and our Apple reporting ranks higher in your Google Search results and Discover feed — one tap, no account changes.
Friendly design does not reduce permissions
Meta says Muse users control which services they connect, can review an audit trail and must approve sensitive actions such as sending an email or making a purchase. It also says people can opt out of having their interactions used to train Meta’s AI models.
Those controls matter more than the character on screen. A mascot cannot verify an answer, narrow an account permission or explain every consequence of connecting email, calendars, health goals and shopping services. Users should evaluate each request as if it came from any other cloud service.
This does not make a friendly design inherently deceptive. It does mean warmth and competence are separate qualities. MacObserver’s Muse launch coverage outlines the agent’s access model, while the newer Muse hardware report shows how Meta wants the assistant to follow users across more devices.
Jolly may make Muse easier to understand and enjoy. It should not make the permission screen easier to ignore. The safest habit is to grant only the access needed for the specific task and remove it afterward when practical.
Discussion