Meta Muse

A useful first task is comparing public opening hours or making a shortlist from public pages. You can verify the result directly and learn how the agent presents sources. Connecting email, calendars or payment services adds separate access decisions.

A task such as “organize my entire week” has many unstated constraints. Start smaller: name the dates, location, budget if relevant, and exactly which actions require your review. These are editorial task-design suggestions, not a claim that we have tested those workflows in Muse.

Availability and entry point

The launch announcement names iOS, Android and muse.ai for its US rollout. It describes broader or future surfaces separately. Use the official product link from that announcement and inspect what your account actually offers. We do not infer a worldwide release, a specific subscription price or account eligibility from the launch text.

Connect only the service you need

The Connector help page describes Settings → Connectors: choose a service, review its information, continue to authorize, then complete its login steps. Some connectors allow retrieval without write actions. Check the actual permission scope before accepting.

Meta says important actions often require approval by default, and approval settings can be changed. Do not assume another person’s settings match yours. Custom connectors also have their own trust implications; Meta says it does not review them.

Keep announced features separate

The September 8 announcement described Shop Pay and 1Password support as coming soon. We have not verified a subsequent general release, so they are not listed here as available integrations. Likewise, the announced Confidential VM was a future item, not the launch environment.

Editorial prompt, not an executed Muse test:

Compare the public opening hours of the two museums I name next.
Use their official visitor-information pages and include each source URL.
State the date the information applies to and any uncertainty.
Do not connect my accounts, book tickets, send messages or make purchases.
Return a concise comparison and stop for my review.

Give the two actual museum names and intended visit date. Open both cited pages, check holiday exceptions, and confirm the answer concerns the correct locations. A source link to a homepage alone may not support the hours stated.

If an account connection is requested for this public-information task, inspect why it is needed before proceeding. If a source cannot be read, the useful output is a clearly identified gap rather than invented hours.

Disconnecting in Settings → Connectors stops further connector data exchange, but previously used information can remain in memory or conversation history. Review the Connector controls for managing those separately.

The payment help page says Muse asks for approval before completing a purchase. Purchasing availability depends on location, merchant and checkout flow. It describes Link by Stripe and saved-card account flows; the merchant fulfills the order. Check the amount, merchant, delivery and refund terms on the merchant’s page before approval.

A payment method being described is not proof that it works for your particular order. We did not test checkout, purchase protection eligibility, fulfillment or refunds.

For a first evaluation, keep an explicit record of what you authorized and compare it with the returned action history. If the agent proposes a broader task, review that change rather than treating the original request as blanket permission.