How to use Meta Muse effectively

Get one useful job finished with Meta's Muse: research a purchase, prepare a document, or turn a messy week into a workable plan. Start with a small task, give it clear limits, and check the result before adding more responsibility.

Your first result: a three-option buying shortlist with source links, a recommendation, and a clear explanation of what still needs checking. The worked example below uses a fictional shopper looking for a work headset under $120. Replace those details with a task you actually need done.

1. Join Muse and redeem Nic's code

Use Join Muse above to open muse.ai/join. Choose the web or app option offered for your device, create your account, and check the access requirements shown during signup.

Nic's referral invite: “Check out Muse, your personal AI agent. Redeem my code in Settings within 48 hours of joining and we'll both get 1 billion Muse tokens.”

Referral code: WA1RM4

Copy the code below into Muse's referral redemption field in Settings, within 48 hours of joining. This code goes in Settings, not into a conversation.

WA1RM4

This is Nic's referral code, and Nic also receives tokens for a qualifying redemption. The offer above comes from Nic's invite; check the current offer and eligibility in Muse before redeeming. This guide has not independently verified the code's remaining availability or the promotion's full terms. Confirm the reward in your account after redemption.

You can download this complete guide and every prompt using Download guide + prompts (.txt) above. Save it before you start so you can reuse the briefs later.

2. Set up for one small win

Meta describes Muse as a personal agent that can use a browser and connected apps, create files, and continue working on tasks in the background. What it can actually complete depends on your access, permissions, and the services involved. Ask it to state any limitation rather than quietly replacing real work with guesses.

For your first session, choose public research with a clear finish line. You do not need to connect your inbox to compare products. Open Muse and start with a short task brief. If a needed connection is unavailable, supply the relevant text or links and keep the final action manual.

Before connecting an account, review what Muse is asking to access. Use Muse's sign-in and permission flow when a task needs it. Check the privacy and model-training choices in Settings and choose the options you want. A written prompt sets your intent; use the actual permission controls as well.

Good first tasks: compare three products, turn supplied notes into a checklist, draft a weekly plan, or prepare a document from material you provide. Pick one deliverable you can inspect in a few minutes.

3. Give Muse a complete brief

A useful brief answers six questions: What should be finished? What context matters? What may it use? What are the limits? What should the result look like? When should it stop?

Copy this into Muse and replace every bracket. Name the actual document, date, budget, and timezone when they matter. Ask only for access that the job needs.

Help me complete this task: [specific finished result].
Context: [who this is for, why it matters, and relevant background].
Inputs: [paste notes, links, or name the files I supplied].
Use: [public websites, supplied material, or named connected apps].
Limits: [budget and currency, date range, location, must-haves, and exclusions].
Deliverable: [a shortlist, checklist, document, spreadsheet, or draft], including [required fields].

Ask up to three questions only if the missing answers would materially change the result. Otherwise state reasonable assumptions and begin. Tell me if you cannot access an input or perform a requested action.

Start with a brief plan. Research and prepare the deliverable, but ask before sending messages, purchasing, booking, publishing, deleting, or changing my accounts. Stop when the deliverable is ready for review. Include source links where relevant, unresolved questions, and a summary of what you actually did.

Read the plan before extending access. If the brief asks for five products and the plan proposes a month of price monitoring, narrow it back to the original job.

4. Run a complete example

Fictional starting brief: you need a new headset for laptop calls in a shared home office. Your limit is $120 USD including shipping and tax. Comfort, a clear microphone, and a USB connection matter more than gaming features.

Paste this into Muse. Replace the location and computer details before running it. The product results must come from current research; the example does not assume any specific headset is in stock.

Find three new headsets for work calls that are likely to fit a $120 USD total budget, including shipping and tax.
My location: [country and ZIP/postal code].
My computer and ports: [operating system and available USB ports].
Use case: two hours of video calls daily in a shared home office.
Must-haves: a boom microphone, comfortable over-ear fit, and compatibility with my computer. Wired USB is fine. Exclude refurbished products.

Use current manufacturer specifications and retailer listings. For each option, give the exact model, connection type, compatibility evidence, listed price, shipping if visible, whether tax is included or still unknown, return-policy link, and product links. Separate manufacturer claims from independently checked evidence. Do not infer microphone quality from marketing language alone.

Recommend one option and explain the main tradeoff. If the full delivered cost cannot be verified, label it provisional. Stop after three viable options, or explain why fewer qualify. Do not sign in, add to a cart, contact a seller, or purchase anything. Return a compact comparison and your recommendation.

What a usable result contains: three identifiable models, working links, evidence for the required connection and compatibility, a price breakdown, and an honest note about unknown tax or shipping. A polished paragraph without those details is unfinished.

Open the recommended product link yourself. Confirm the model and variant match, the price is current, and the return policy applies to your location. If a $109 headset has unverified shipping and tax, it is still provisional against a $120 total limit.

Improve the result with one precise correction

Keep the good research and change the part that missed your needs. If the shortlist has Bluetooth-only options, specify the correction instead of restarting the whole task.

Revise the headset shortlist you just made. Keep every option that meets my original requirements. Remove Bluetooth-only options because I need a direct USB connection. Replace only the removed options, using current source links. Recheck the total-cost uncertainty against my $120 USD cap. Show what changed and why. Keep the task research-only and stop after the updated shortlist.

Turn research into something reusable

Once the facts are checked, ask for a file you can keep. Muse's documentation describes creating documents, PDFs, web pages, and other artifacts. Request the format you need and verify that the returned file actually opens.

Turn the checked headset shortlist from this conversation into a one-page buying brief. Include my requirements, the recommended exact model, the comparison, source links, prices with the date checked, and unresolved costs or compatibility questions. Preserve uncertainty and do not add new factual claims. Create a downloadable PDF if available; otherwise return a clean document I can copy and save. Stop when it is ready. Do not purchase or schedule anything.

The finished result is a brief you can open, understand, and use to make your own purchase decision. This is a suggested workflow checked against documentation, not a report of a purchase tested by Nic.Buildz.

5. Use the same structure for everyday work

These three prompts are starting points. Replace the brackets, inspect the first result, and then decide whether a connection or recurring task would help.

Turn a task list into a realistic week

Paste your tasks and existing commitments into Muse. The first pass can work from supplied text. Only connect a calendar if you want Muse to read it and you have reviewed that access.

Build a practical plan for the week starting [date] in [timezone].
Tasks with deadlines: [list].
Existing commitments: [list].
Available work hours: [hours by day].
My top priority: [priority].

Choose three outcomes, estimate the time each needs, and place work into the available gaps with buffer time. Flag conflicts and tasks that will not fit. Return a day-by-day proposal. If you cannot read my calendar, use only the commitments supplied here and say so. Do not create or move calendar events. Stop with the proposed plan for me to review.

Check deadlines and available hours before accepting the plan. If it assumes six free hours on a day with two, correct that input first.

Prepare replies without losing the important details

Provide the relevant message text, or use a connected inbox you have deliberately approved. Check that Muse distinguishes a requested action from an action already completed.

Help me process [the messages pasted below / this specific connected inbox folder] for [date range].
My priorities: [priorities].

Return the five most important items with sender, subject, requested action, deadline if explicitly stated, and a short draft reply when needed. Mark inferred deadlines as guesses. Use only the messages you can access; explain any access limit. Do not open unrelated folders, send, forward, archive, delete, unsubscribe, or change labels. Stop with drafts for my review.
[Paste messages here if using supplied text.]

Check the recipient, dates, attachments mentioned, and commitments in each draft before you send it.

Build a research-backed content brief

Give Muse a specific audience and question. The result should make your next writing session easier, with evidence you can open.

Prepare one content brief about [specific question] for [audience] on [platform].
My angle or experience: [notes].
Use current primary sources where available and my supplied notes. Return: a one-sentence takeaway, three possible hooks, an outline, three factual claims with direct source links and dates, and any uncertainty. Separate my experience, sourced facts, and your suggestions. Do not invent quotes, statistics, endorsements, or performance predictions. Stop after the brief; do not publish or contact anyone.

Open each source before writing. Remove a claim if the linked page does not support it.

6. Add background work after the first result works

Muse's design documentation describes scheduled work, background tasks, a Goals tab, and an activity log. Use those to inspect ongoing jobs. Confirm the schedule and task state in your app; asking for a reminder is not evidence that one has been created.

For the headset example, a sensible next step is a short price watch on one exact model. Define where to check, what qualifies, and when the task ends. Start with a proposed schedule so you can inspect it before activating anything.

Propose a seven-day price watch for [exact headset model and approved product URLs]. Check once daily at [time and timezone], ending [date]. Notify me only if the verified delivered total is at or below $120 USD, the product becomes unavailable, the check fails, or you need my input. Label unknown tax or shipping; do not report an unverified total as meeting the cap.

Show the schedule, sources, trigger, and end date first. Do not activate it until I confirm. After confirmation, tell me whether it was actually created and where I can inspect or stop it. If scheduling is unavailable, say so and give me a manual checking checklist. Never purchase, sign in, or contact a seller.

After activation, review Goals and activity for the task and its next run. Stop the watch when you buy or change your mind. Check that it is no longer active. Keep the number of ongoing tasks small enough that you can still explain what each one is doing.

7. Spend tokens on progress

Check your account's displayed usage and plan limits. Token allowances and referral rewards can change; a token balance is not a guarantee of a fixed number of finished jobs.

• Bound the search: ask for three viable options from named sources, with a stop condition.
• Approve the direction early: inspect an outline or sample before requesting a large final artifact.
• Revise the weak part: preserve useful work instead of regenerating the whole result.
• Supply focused inputs: relevant messages and notes are easier to work with than an unexplained file dump.
• Limit recurring jobs: set a frequency, meaningful notification trigger, and end date.
• Stop loops: after two unsuccessful approaches, ask what is blocked and choose a manual next step.

For an unexpectedly long task, ask: “Pause and show what is complete, what is blocked, and the smallest next step that would finish the deliverable.”

8. Fix common problems

• Muse gives advice instead of the deliverable: name the output. Say “Create the three-option comparison now using the sources available; list any blocker.”
• It asks too many questions: supply the three facts that change the decision, then permit reasonable stated assumptions for everything else.
• It cannot access a site or account: inspect the access request. If access is unavailable, paste the relevant text or complete that step yourself. Do not let it invent what was behind the login.
• It says something is done: open the file or check the destination, timestamp, and activity record. Ask it to separate completed actions from plans and attempts.
• It keeps working after the result is ready: tell it to stop that specific task and associated monitoring; check the task state in Goals or activity.
• The referral field or reward is missing: confirm you are in Muse at the supplied join link, check when you joined, and look for the current redemption instructions in Settings. If needed, use Muse's help options. Repeated chat prompts will not redeem a Settings code.

Your completion check

• You have one finished result you can open and use.
• The result respects your requirements and identifies anything unverified.
• You checked the key source links, dates, numbers, and names yourself.
• You know what Muse actually did and which accounts it used.
• Any ongoing task has a schedule, stop date, and a way to inspect it.
• You saved the brief that worked, so the next task starts with better context.

Begin with one bounded job. Once you can reliably check its result, reuse the brief for the next task and expand from there.