How to Use Muse AI: Complete Your First Task Step by Step

Getting started with Muse AI begins with a clear task.

Muse is Meta’s personal AI agent. It can browse websites, work with information, and create documents and other outputs. Its official design overview also describes background tasks that can continue after the app is closed. Meta’s launch announcement, official design overview

In this tutorial, you will use Muse to turn rough meeting notes into three useful outputs:

• A short meeting summary.

• An action list with owners and deadlines.

• A list of questions that still need answers.

You will then check the result and request a revision. Once this workflow feels familiar, you can add memory, email connections, and ongoing Goals.

1. Sign In and Check What Is Available

Open the Muse website and follow the sign-in instructions. You can also use the mobile apps or Mac client through official download channels.

Meta’s launch announcement described an initial US rollout on iOS, Android, and the web, with free access and subscription options. Check your account for current availability, limits, and pricing. Meta’s launch announcement

For your first task, use whichever supported device you can access comfortably.

If you cannot sign in, read the specific message on the screen. Regional restrictions, account eligibility, and connection problems need different solutions.

You can follow the meeting-notes example below without connecting your email or giving Muse access to your computer.

2. Tell Muse How You Want to Work Together

Complete any initial setup, then explain your working preferences.

Here is a prompt you can adapt:

Please follow these preferences when working with me:

1. Reply in English.
2. Use [your time zone] when interpreting times.
3. Start working when the task is clear.
   Ask when missing information would materially affect the result.
4. Do not invent task owners, deadlines, decisions, or completion status.
5. When you finish, provide the output link first,
   followed by a brief explanation of what you created.
6. Before sending messages, updating shared systems,
   deleting information, or changing external content,
   explain the proposed action and wait for my confirmation.

Next, open Settings and review any existing connections.

Check which accounts are connected, what Muse can read, and whether it can also send or modify information. Chat instructions express your preferences; formal permissions and approvals are managed separately. Official safety overview

For now, locate the chat area, Settings, and the links used to open generated outputs.

Meta’s design overview also describes an activity log and approved permissions accessible through the agent’s avatar. Use these to see what it is doing; the exact layout may change between versions. Official design overview

3. Your First Task: Turn Meeting Notes Into an Action List

Start with a meeting you attended. You will be better able to spot a missing decision or an incorrectly assigned task.

For this walkthrough, we will use a fictional website launch meeting. Replace the example with your own notes when you are ready.

Example Meeting Notes

Meeting: Website Launch Check-In
Date: October 7, 2026

- The team is aiming to launch on October 16,
  subject to final approval.
- Maya will finish the homepage copy draft by October 9.
- Daniel will prepare two design options by October 12.
- Leo will check the mobile contact form.
  No deadline was agreed.
- Nina will request legal review of the final marketing claims.
  No deadline was recorded.
- Someone needs to update the project tracker.
  An owner was not assigned.
- Daniel suggested testing a shorter headline.
  The team did not make a decision.
- The next check-in is October 13 at 10:00.
  The time zone was not recorded.

These notes contain clear assignments, missing information, a tentative launch date, and a suggestion that has not been approved.

Send Muse the following task, followed by the notes:

Include three sections:

1. Meeting summary
   Briefly explain what was discussed.
   Separate confirmed decisions from suggestions and tentative plans.

2. Action items
   Create a table with:
   Task
   Owner
   Deadline
   Reported status
   Supporting text from the notes

3. Open questions
   List missing owners, missing deadlines,
   unresolved decisions, and unclear scheduling details.

Requirements:
- Use only the notes I provide.
- If an owner or deadline is missing, write “Not specified.”
- If completion status is missing, write “Not reported.”
- Do not turn suggestions into agreed decisions.
- Preserve conditions attached to dates or plans.
- Do not infer a time zone that is not recorded.

Only create the document.
Do not send emails, update calendars,
or change any project management system.

Provide a link to open the result.

If file creation is unavailable,
provide a complete, copyable version and explain why.

Meeting notes:
[paste the notes here]

This prompt gives Muse a clear source, a defined structure, and a concrete deliverable.

You can reuse the same approach for planning meetings, client calls, or internal handovers:

Task + source material + required fields + completion standard + deliverable.

When external actions are involved, add the boundaries for those actions.

4. Open the Result and Check the Details

When Muse reports that it has finished, open the actual output.

Check that the document loads and contains the summary, action table, and open questions.

If you receive only a short chat response, follow up:

Please provide the complete meeting summary and action table
in an accessible document.

If you cannot create a document,
give me the full, copyable version in this conversation.

Then compare several entries with the original notes.

For this example, check that:

• Maya’s copy deadline is October 9.

• Leo’s deadline remains “Not specified.”

• The October 16 launch date retains the condition about final approval.

• Daniel’s headline suggestion remains a suggestion.

• The tracker update has no assigned owner.

• The next meeting’s missing time zone appears as an open question.

A neatly formatted table can still contain an incorrect interpretation.

Pay particular attention to tentative language such as “aiming for,” “suggested,” and “subject to approval.”

If the notes themselves are unclear, keep the uncertainty visible. You can ask the relevant person for clarification and then supply that answer to Muse.

5. Request One Revision in the Same Conversation

The first version may be accurate but awkward to use.

For example, the action list may be too long to scan, or the open questions may need to be grouped by topic.

Continue in the same conversation:

Please revise the document you just created.

Keep v1 and save the revised version as
“Website Launch Meeting Summary-v2.”

Make these changes:

1. Put the action table before the meeting summary.
2. Group action items by owner.
   Put unassigned tasks in a separate group.
3. Add a “Needs confirmation” column.
4. Separate confirmed decisions,
   tentative plans, and suggestions in the summary.
5. Keep missing information visible.
   Do not fill it in without additional evidence.
6. Check each action item against the original notes.

Provide the revised output link
and briefly list what changed.

Open v2 and verify the changes.

If Muse says the document was updated but the expected change is missing, point it out precisely:

The revised document still lists the tracker update
under Maya, although the notes do not assign an owner.

Move it to the unassigned group
and check the actual document before reporting completion.

You have now completed the main workflow: assign a task, open the result, check the source material, and request a correction.

The same sequence works for interview notes, project handovers, and client feedback.

6. Add More Capabilities When the Work Requires Them

Memory and Working Preferences

After a few meetings, you may notice that you repeatedly request the same format.

You can express that as a lasting preference:

Please remember my preferred meeting-summary format:

Start with action items.
Include owners and deadlines.
Keep unresolved questions in a separate section.
Use a short summary after the action table.

If the instruction applies only once, say so:

For this meeting only,
keep the summary under five bullet points.

Meta’s documentation describes memory that users can inspect and edit. Review it when a preference is wrong, outdated, or no longer useful, using the controls available in your current version. Official safety overview

Account permissions still need to be managed through the relevant authorization controls.

Connect Email When Follow-Ups Are in Your Inbox

Some meeting decisions are clarified later by email.

If you need those messages, connect a supported email service through Settings. Confirm the account and permissions before authorizing it. Where separate read and write permissions are supported, you can begin with read access. Official safety overview

Try a familiar project first:

Please find emails from the past seven days
related to the “Website Launch” project.

Create a follow-up list containing:
Sender
Subject
Date
Explicitly stated task or decision
Owner, if specified
Deadline, if specified
Original email link

Compare the information with our meeting summary.

Flag any changed deadlines or conflicting instructions.
Do not silently replace the original information.

Only read and organize the emails.
Do not reply, forward, delete, move messages,
or change labels.

Replace the project name with a real topic in your inbox.

Open a few original messages to check the assignments and dates. If an email changes a deadline, the revised summary should make the change traceable.

You can disconnect the service when it is no longer needed. Review separately any information already copied into documents, conversations, or memory.

Use Goals for a Project That Continues After the Meeting

A meeting summary is a one-time output. Preparing for a launch may require several rounds of follow-up.

You can create a Goal for that continuing work:

Please create a Goal:

Prepare the website launch readiness summary
by October 16, 2026.

Use our meeting summary and any follow-up information
I explicitly provide or authorize you to read.

Maintain:
An action list
Reported progress
Missing information
Questions requiring my input

Final deliverable:
A launch readiness summary with supporting sources
and clearly marked unresolved items.

Do not assume a task is complete unless there is evidence.
Do not send reminders, update shared systems,
or change calendar events without my confirmation.

Change the deadline to match your project.

Open Goals and check that the objective, deliverable, and next steps are recorded. Meta describes Goals as a way to track ongoing tasks and their plans. Official design overview

If you want scheduled updates, confirm the schedule and next run separately.

7. Explore Custom Connectors and Computer Access

Connect a Project Tool That Is Missing From the List

If your team uses a project management service, first check whether it already has a supported connector.

If it does not, ask Muse to assess the options:

I want to read task information from
[project management service].

First, check whether an existing connector is available.

If custom integration is required, explain:
The available access method
Required permissions
Whether read-only access is supported
Where credentials should be entered securely
How to test the connection
How to revoke access

Provide the plan first
and wait for my confirmation before configuration.

Meta’s safety documentation describes custom connectors for services with APIs or CLIs. Whether a particular integration is possible depends on the service. Official safety overview

After setup, read one familiar task and verify its title, owner, and deadline before expanding the scope.

Start Computer Access With a Test Folder

If meeting notes are stored locally, computer access may help with later tasks.

Meta announced computer-use capabilities for Muse on Mac at Connect 2026, subject to user permission. Meta Connect 2026 announcement

Before configuring access, explain your device and intended scope:

I use [operating system and version].

I want you to access a test folder called Meeting-Test.

Explain:
The supported access method
Required permissions
Whether access can be limited to that folder
How to disable access

Provide setup steps first
and wait for my confirmation.

Place a few non-sensitive file copies in the folder, then test:

Please list the filenames in
[full path to the Meeting-Test folder].

Only list filenames.

Do not read file contents,
modify, delete, or move files,
access unrelated folders,
or install software.

Stop after listing the filenames
and wait for my review.

Verify the path and filenames before asking Muse to process documents.

The prompt defines the task scope. Where permission controls support restricting folder access, configure those controls too.

8. Troubleshoot When the Result Falls Short

Before moving on, check that you have completed the full workflow:

• Signed in and located permissions and task activity.

• Submitted notes with clear output requirements.

• Opened the generated summary and action list.

• Checked owners, deadlines, and decisions against the notes.

• Requested a revision and verified the updated document.

For your next meeting, use your own notes and adapt the fields to your team’s needs. Keep the same habit: open the result, check the details, and resolve missing information before sharing it.