Muse Beginner Tutorial: From Login to First Task

Muse is Meta's personal AI Agent, capable of browsing the web, generating files, and continuing some tasks even after the app is closed.

For your first use, try having it organize several links into a reference table: assign the task, open the file, verify sources, and then request a revision.

This isn't just a feature list. Follow these steps in order, and you'll have Muse complete a task within your visible control. Add connectors, memory, and long-term goals only when needed.

1. Where to Start? Log In and Check Availability

Open muse.ai and log in according to the page prompts.

You can also log in via the Muse desktop client or mobile app.

Before starting, know these basics:

• The official announcement on September 8 stated that the initial launch is for the US, supporting iOS, Android, and Web. Your account's current eligibility depends on the registration page.
• Official free usage and paid subscriptions are available; check your account for specific quotas and pricing. Try one task before deciding to subscribe.
• This tutorial uses the Muse desktop client as a demo. Choose one device and follow along.

If you can't access it, check the specific error message. Regional restrictions, ineligible accounts, and network failures require different solutions.

2. After Logging In, Define How You Collaborate

Complete initialization (like naming) as guided, then send this prompt in chat. Adjust timezone and habits as needed:

1I am a Chinese user, timezone Asia/Shanghai (UTC+8).
2Give conclusions first, then necessary explanations.
3Mark unconfirmed information and provide verifiable sources.
4
5For external sending, form submission, ordering, payment, or account modification,
6show specific content first and wait for my explicit approval before executing.

Next, open Settings to check permissions, approvals, and existing connections. Focus on: which account is connected, what it can read, and whether it can modify or send content on your behalf.

Collaboration rules in chat do not replace permission settings. The official platform provides an approval mechanism for critical actions; review authorization cards carefully before agreeing.

Don't memorize the entire interface on day one. Find the chat area and Settings; open them from the corresponding message after a reply is generated. Clicking the assistant avatar lets you see what it's doing, plus activity logs and approved permissions.

3. Practice: Organize Web Links into a Reference Table

Choose a familiar topic for your first task so you can judge accuracy and spot omissions.

Here, we'll use "Understanding Muse's Basic Features" as a practice example. Use the official announcement and design docs as sources; no need to connect email or cloud storage yet.

Send this directly to Muse:

1I'm preparing a beginner guide for Muse. Please help me organize materials first; do not write the article.
2
3Use only these two sources:
4https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/
5https://introducing.muse.ai/
6
7Create a Chinese reference table named "Muse Beginner Materials".
8Columns: Feature/Topic, Key Points from Source, Source Link, Items to Verify.
9
10Focus on: Web Browsing, File Generation, Background Tasks, Goals, Memory, and Action Approvals.
11Merge content mentioned in both sources but keep respective citations.
12Explain if a link fails; mark details not in the original text as "Not Specified"—do not guess.
13
14This task is for public material organization only: no account registration, contacting others, or payments.
15Upon completion, provide an openable table file and include the file entry in chat.
16If file generation is currently unavailable, provide a complete copyable table and explain the limitation.

This task clarifies: what to read, what to organize, where not to add info, and what to deliver.

For future work, reuse this structure:

Task + Material Scope + Completion Criteria + Delivery Format.

Add action boundaries when involving accounts or external operations.

For example, change "Check out these products" to "Based only on these three official sites, compare price, target audience, and main limitations; give me a sourced table." Specific requirements make it easier to judge result quality.

4. After Receiving Results, Open and Spot-Check

When you see "Completed," click the file first. Ensure content displays correctly, headers are present, and source links are clickable.

If there's only a chat reply, follow up with:

1I didn't see a file entry earlier. Please confirm if a file was generated, and give me the exact filename and location.

Then spot-check a few conclusions. For this practice task, focus on:

• Is the claim about "continuing work after closing the app" found in the official text?
• How are Goals described? Did the table turn goal management into a guarantee of timely completion?
• Are quotas, button locations, or functional limits not provided in the source marked as "Not Specified"?

Even with source links, verify if the linked content actually supports the conclusion.

If a link fails, paste the text you read yourself, noting the source; if content is temporarily unavailable, keep that item as "To Be Verified."

5. Request a Revision in the Same Conversation

It's normal for the first version to be insufficient. Telling it what to fix in the same thread is more convenient than starting over.

For instance, if the table exists but you need to distinguish "Officially Stated" from "Needs Further Confirmation" for writing, add:

1Please revise based on the previous table, keeping the original file, and save as "Muse Beginner Materials-v2".
2
31. Add a "Source Publication Date" column; write "Not Marked" if the exact date isn't found.
42. Cross-check feature descriptions against sources; don't frame capability intros as performance guarantees.
53. Move content without original support to "Items to Verify".
6
7Provide the new file entry upon completion and briefly list changes made.

Open the new version to see if the added column appears and issues are fixed. If it only replies "Modified" without a new file or actual changes, point out the missing parts and ask it to continue.

By now, you've completed the most common workflow: assigning a task, opening results, verifying content, and requesting revisions.

You can apply this sequence to organizing PDFs, comparing plans, or preparing itineraries later.

6. Add These Capabilities After Using It a Few Times

Memory and Soul: Use Normally First, Don't Rush to Edit

Muse gradually accumulates memory and adjusts collaboration style through interactions. Memory records info and preferences about you; Soul influences the assistant's expression and behavior style.

Beginners don't need to manually edit these files initially. Just assign tasks and give feedback normally: tell it what replies you like or where it misunderstood, letting it refine step by step.

For example:

1From now on, give short conclusions first, expanding only when necessary.

If you want a short reply just this once, say "Keep it brief this time" to avoid turning temporary requests into long-term preferences.

You can view and modify these sections too. To see what it remembers, or if you find inaccurate info or unsuitable expressions, enter Identity via the assistant avatar to view/edit Memory / Soul as needed (entry points may vary by version).

Account access and operation approvals are still managed in permission settings.

Materials in Email? Connect Email Before Organizing

When you need to organize info from emails, open the connector/service connection entry in Settings, choose a supported email service, and authorize.

Before authorizing, clearly see which account is connected and whether it can read, send, or delete emails. For the first time, if read-only is supported, choose read-only. Enter passwords and verification codes in the email service's login/authorization interface.

After connecting, test with a familiar email subject:

1In the recently connected mailbox, search for emails related to [Project Name] from the last 7 days.
2Organize into a list including: Sender, Subject, Date, Main Matters,
3and explicitly mentioned To-Dos and Deadlines in the emails.
4Mark items without clear deadlines as "Not Specified"—do not guess.
5Include original email entries for my verification.
6
7Only read and organize; do not send or reply to emails,
8delete, move, or modify labels.

Replace [Project Name] with a real subject you've received. After getting results, open a few original emails to verify senders, matters, and deadlines, ensuring no key info is missed or misunderstood.

You can disconnect the email link in settings after use; content already entered in chats or memory needs separate checking and management.

Task Spanning Days? Put It in Goals

One-time organization works fine in chat. For multi-step, ongoing tasks, create a Goal.

Reusing the previous material organization task:

1Please create a Goal: By [Specific Date],
2complete the material checklist for the Muse beginner article.
3
4Based on the previous table, list missing info and next steps to fill gaps.
5The deliverable is a sourced table with items to verify.
6If I need to provide screenshots or supplementary materials from my account, please specify exactly what's missing.

Change the date to your actual deadline before using.

After creation, open Goals to check if it's saved, if the deliverable is clear, and what the next step is.

If you want daily updates at a fixed time, further confirm the scheduling and next run time. Setting a goal and scheduling updates are separate checks.

7. Enable These Entries When You Need More Capabilities

Custom Connectors: Integrate Services Not Listed

Where to start: First check the connector list in Settings.

If the service isn't listed, ask Muse for a configuration plan in chat.

1I want to connect [Service Name] to read [Specified Materials].
2First check if there's an official connector.
3If custom configuration is needed, explain:
4Where to set it up, required permissions, if read-only is possible,
5where to securely enter credentials, and how to revoke authorization.
6Give steps first, wait for my confirmation before proceeding.

What to do first: Confirm account and authorization scope. After connecting, read one familiar test record and verify returned content.

What NOT to do: Don't paste API Keys, passwords, or verification codes into regular chat; don't test modifications/deletions with important data immediately.

Connect to Computer: List a Test Folder First

Where to start: Mac users get the client from the official entry and configure computer operation permissions per current version prompts. For other devices or remote connections, ask Muse to confirm support first, then provide setup steps.

1My system is [OS and Version].
2I want you to access a test folder.
3First explain supported connection methods, enablement location, required permissions,
4if access can be restricted to specified directories, and where to disable it.
5Give configuration steps first, wait for my confirmation before proceeding.

After configuration, test with this prompt:

1Please list filenames in [Full Folder Path].
2Do not read unrelated directories, modify, delete, move files, or install software.
3Stop after listing and wait for my check.

What to do first: Put copies of non-sensitive files inside, verify listed paths and filenames, then consider creating new files.

What NOT to do: Don't batch-modify files initially. Prompts don't automatically restrict directory access; if you can limit scope in authorization settings, do it there; revoke unnecessary permissions after use.

8. Troubleshooting When Stuck

It keeps explaining but doesn't deliver. Add clear output requirements: filename, table fields, format, and open entry. If file generation is unavailable, request a complete copyable version.

Can't find the generated file. Go back to the corresponding task message to find the entry, ask it to report the filename. Also check the resource library.

Waited long, unsure of progress. Click the assistant avatar to view activity logs. Or ask directly: "What's done? Where is it stuck? What do I need to supplement?"

Preferences saved but not followed. Point out specific non-compliance in the original conversation and ask it to correct; if the issue recurs, check memory content and fix errors/conflicts as needed.

Prepared action doesn't match expectations. Reject the corresponding approval and stop the task, check activity logs and authorization scope, disconnect relevant services if necessary.

Finally, Check If You Completed This Round

• [ ] Logged in, know where to view permissions and task activities.
• [ ] Issued a task with clear material scope and delivery requirements.
• [ ] Opened results, spot-checked sources and content.
• [ ] Requested revisions in the original conversation and opened the new version to confirm changes.

After completing this round, switch to your own articles, plans, or meeting notes. Get a usable result first; enable capabilities only as needed.

References:

• Meta: Muse Announcement, for verifying product positioning, launch scope, platforms, free/subscription details.
• How We Designed Muse, for verifying background tasks, activity logs, Goals, Memory, approvals, and file delivery design.
• Meta: Connectors & Approval Guide, for verifying connectors, authorization, and custom config.
• Meta: Personalization & Data Management, for verifying memory, settings, and data management.
• Meta Connect 2026, for verifying Mac-side computer operation capabilities.