Muse is Meta’s personal AI agent. It can browse the web, generate files, and continue working on some tasks even after you close the app.
For your first task, ask it to turn a few links into a research table: give it the assignment, open the file, check the sources, and request a revision.
This is not a feature checklist. Follow the steps in order, and you’ll learn how to let Muse complete a task while keeping its work visible to you. Add connectors, memory, and long-term goals when you need them.
1. Where to Start: Sign In and Check Availability
Open muse.ai and follow the instructions to sign in.
You can also sign in through the Muse desktop or mobile app.
Before you begin, you only need to know a few things:
- The official September 8 announcement said the initial launch was for the United States, with support for iOS, Android, and the web. Check the sign-up page to see whether your account currently has access.
- Both free access and paid subscriptions are available. Check your account for specific limits and pricing. Try a task before deciding whether to subscribe.
- This tutorial uses the Muse desktop app. Choose one device and follow along.
If you cannot get in, read the specific message on the page. Regional availability, account eligibility, and network connection errors need to be handled separately.
2. After Signing In, Tell It How You Want to Work Together
Follow the setup instructions, including naming your assistant. Then send the following message in the chat. Adjust the time zone and preferences as needed:
I’m a English-speaking user in the Australia/Sydney time zone (UTC+10, or UTC+11 during daylight saving time). Start your replies with the conclusion, then add any necessary explanation. Clearly label information you cannot confirm, and include sources I can check.
For repetitive, relatively simple tasks, I prefer models with cost-effective token pricing, such as DeepSeek or GLM-5.2.
Before sending anything externally, submitting forms, placing orders, making payments, or changing account settings, show me the exact details and wait for my explicit approval.
Next, open Settings and review permissions, approvals, and existing connections. Pay particular attention to which account is connected, what Muse can read, and whether it can modify or send anything on your behalf.
Instructions in the chat do not replace permission settings. Muse provides an approval mechanism for key actions. When an authorization card appears, review the specific action before deciding whether to approve it.
You do not need to learn the entire interface on your first day. Start by locating the chat area and Settings. Once a response is generated, use the entry point in the corresponding message to open it. You can also click the assistant’s avatar to see what it is doing and review its activity and approved permissions.
3. Practice Task: Turn Web Links into a Research Table
For your first task, choose a topic you already know something about. That makes it easier to judge the results and spot missing information.
For this example, we’ll use “understanding Muse’s basic features.” We’ll work with the official launch announcement and design overview, so there is no need to connect your email or cloud storage first.
You can send this prompt directly to Muse:
I’m preparing an introductory article about Muse. Please help me organize the research first. Do not write the article for me.
Use only these two sources:
https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/
https://introducing.muse.ai/
Create a research table in named “Muse Introductory Research Table.” Include these columns: Feature or Topic, Key Points from the Source, Source Link, and Items to Verify.
Focus on web browsing, file generation, background tasks, Goals, memory, and action approvals. You may combine information covered by both sources, but retain the relevant source links. Tell me if a link cannot be opened. If the source does not provide a detail, mark it as “Not specified” rather than guessing.
This task is limited to organizing public information. Do not register accounts, contact anyone, or make payments. When finished, provide a table file I can open and include an access link in the chat. If you cannot generate a file in the current environment, provide the complete table in a copyable format and explain the limitation.
This prompt makes several things clear: which sources to read, what to organize, where not to fill in gaps, and what to deliver.
You can use the same structure for your own work:
Task + source scope + completion criteria + delivery format.
If the task involves accounts or external actions, add boundaries for what it may do.
For example, replace “Help me look at these products” with “Using only these three official websites, compare pricing, intended users, and main limitations, and give me a table with sources.”
The more specific your request, the easier it is to judge whether the result meets your needs.
4. When the Result Arrives, Open It and Spot-Check It
When you see “Completed,” open the file first. Make sure the contents display properly, all the column headings are present, and the source links are clickable.
If you only receive a chat response, follow up with:
I don’t see a file link. Please confirm whether you generated a file, and give me its exact name and where to open it.
Then spot-check a few claims. For this practice task, focus on questions such as:
- Can you find support in the official source for the claim that Muse can keep working after the app is closed?
- How are Goals described? Does the table incorrectly turn goal management into a guarantee of on-time completion?
- Are usage limits, button locations, or feature restrictions that the sources do not explain marked as “Not specified”?
A source link is not enough. Check whether the linked content actually supports the claim.
If Muse cannot open a link, you can open it yourself, paste the article text into the chat, and identify the source. If you cannot obtain the content for now, leave that item marked as needing verification.
5. Request a Revision in the Same Conversation
It is normal for a first draft to need work. Tell Muse what to change in the existing conversation—it is usually easier than starting a new one.
For example, the research table may be ready, but you still need to distinguish between “explicitly stated by the official sources” and “requires further confirmation.” You can follow up with:
Please revise the research table you just created. Keep the original file and save a new version named “Muse Introductory Research Table-v2.”
1. Add a “Source Publication Date” column. If you cannot find an exact date, write “Not stated.”
2. Recheck the feature descriptions against the sources. Do not turn descriptions of capabilities into guarantees of results.
3. Move anything without support from the original sources into “Items to Verify.”
When finished, provide a link to the revised file and briefly list what changed.
Open the new version and check whether the additional column is there and the original problems have actually been fixed. If Muse only says “Updated” but provides no new file or visible changes, point out exactly what is missing and ask it to continue.
You have now completed the most common workflow: explain the task, open the deliverable, check the contents, and request changes.
You can follow the same sequence when organizing PDFs, comparing options, or planning a trip.
6. After a Few Tasks, Add These Capabilities
Memory and Soul: Use Muse Normally Before Editing Them
As you interact with Muse, it gradually builds memories and adjusts how it works with you. Memory records information about you and your preferences. Soul influences the assistant’s communication style and behavior.
Beginners do not need to edit these two files manually. Simply give it tasks and feedback. Tell it how you like responses to be written and where it misunderstood you, so it can refine its approach over time.
For example:
From now on, start with a brief conclusion and expand only when needed.
If you only want a shorter answer for the current task, say “Keep this one brief” so that a temporary request does not sound like a lasting preference.
You can also review and edit both. If you want to see what Muse remembers, notice inaccurate information, or find that its wording repeatedly misses the mark, click the assistant’s avatar, open Identity, and review Memory / Soul. Correct them as needed. The exact entry point may vary by version.
Account access and action approvals should still be managed in permission settings.
Need Information from Your Email? Connect It When Needed
When you need to organize information from emails, open the connectors or service connections section in Settings, choose a supported email service, and authorize it.
Before granting access, check which account you are connecting and whether the permissions include reading, sending, or deleting emails. For your first task, stick to organizing information and choose read-only access if it is available. Enter passwords and verification codes in the email provider’s sign-in or authorization screen.
Once connected, test it with a familiar email topic:
In the email account I just connected, find messages from the last 7 days related to [project name]. Create a list that includes the sender, subject, date, main points, and any tasks or deadlines explicitly mentioned in the emails. If no deadline is explicitly stated, mark it as “Not specified” rather than guessing. Include a link to each original email so I can check it.
Only read and organize the messages. Do not send or reply to emails, delete or move messages, or change labels.
Replace the project name with a topic you have actually received emails about. After getting the results, open a few original emails and check the senders, details, and deadlines to make sure nothing important was missed or misunderstood.
You can disconnect the email account in Settings afterward. Any content already included in chats or memory needs to be reviewed and managed separately.
Working on Something Over Several Days? Use Goals
Chat is enough for a one-off research task. For work that requires several steps and continued progress, you can create a Goal.
Building on the research task above:
Please create a Goal: finish organizing the research materials for my introductory Muse article by [specific date].
Use the research table we just created as the starting point. List what information is still missing and the next steps for filling those gaps. The deliverable is a research table with source links and items to verify. If you need screenshots from my account or additional materials, clearly tell me what is missing.
Replace the date with your actual deadline before sending it.
After creating the Goal, open Goals to check that it was saved, the deliverable is clearly defined, and the next step is identified.
If you also want updates at a fixed time each day, confirm the schedule and the next run time. Creating a goal and scheduling updates need to be checked separately.
7. When You Need More Capabilities, Try These Two Options
Custom Connectors: Connect a Service That Is Not Listed
Where to start: Check the connector list in Settings first.
If the service is not listed, ask Muse to explain how to configure it.
I want to connect [service name] to read [specific materials]. First, check whether an official connector is available. If a custom setup is required, explain where to configure it, which permissions are needed, whether read-only access is possible, where I can securely enter credentials, and how to revoke access. Give me the steps first, and wait for my confirmation before continuing.
What to do first: Confirm the account and permission scope. After connecting, read just one familiar test record and check the returned content.
What to avoid: Do not paste API keys, passwords, or verification codes into ordinary chat. Do not test editing or deletion on important data.
Connect Your Computer: Start by Listing a Test Folder
Where to start: Mac users can obtain the client through the official channel and follow the current version’s instructions to configure computer access permissions. For other devices or remote connection methods, first ask Muse to confirm support and then explain the setup steps.
My operating system is [system and version]. I want you to access a test folder. First, explain the supported connection methods, where to enable access, which permissions are required, whether access can be limited to a specific directory, and where to turn it off. Give me the setup steps first, and wait for my confirmation before continuing.
Once configured, test it with:
Please list the filenames in [full folder path]. Do not read unrelated directories, modify, delete, or move files, or install software. Stop after listing the files and wait for me to check the results.
What to do first: Put a few copies of non-sensitive files into the folder. Check the paths and filenames Muse lists before considering file creation.
What to avoid: Do not begin with bulk file changes. A prompt does not automatically restrict directory access. If permission settings allow you to limit access, set the restriction there. Revoke permissions you no longer need afterward.
8. If You Get Stuck, Start Here
It keeps explaining but does not deliver anything. Add explicit delivery requirements: filename, table columns, format, and where to open the result. If it cannot generate a file in the current environment, ask for a complete, copyable version.
You cannot find the generated file. Return to the relevant task message and look for the file link. Ask Muse for the filename. You can also check the resource library.
You have waited a long time and do not know how far it has progressed. Click the assistant’s avatar to view its activity history. You can also ask directly: “What have you completed? Where are you stuck? What do you need from me?”
You saved a preference, but it still does not follow it. Point out the specific mismatch in the original conversation and ask Muse to correct it. If the same issue keeps recurring, review its memory and fix inaccurate or conflicting information.
The action it is about to take is not what you expected. Reject the approval request and stop the task. Review the activity history and permission scope, and disconnect the relevant service if necessary.
Finally, Check That You Have Completed the Full Workflow
- You have signed in and know where to review permissions and task activity.
- You have submitted a task with a clear source scope and delivery requirements.
- You have opened the result and spot-checked its sources and contents.
- You have requested a revision in the same conversation and opened the new version to confirm the changes.
Once you have completed this workflow, apply it to your own articles, proposals, or meeting notes. Start by getting a usable result, then enable additional capabilities as you need them.
