Muse Explained An independent publication

10 Things to Try First in Muse

Skip the feature tour. These ten starter tasks — each with a brief you can copy — will teach you what an AI agent is actually good for in about a week.

Last checked: September 19, 2026. Assumes the app plus at least email connected.

The fastest way to learn Muse isn't reading about it — it's delegating ten small, real jobs and watching what happens. Each task below includes an example brief: the outcome, the boundaries, and the check-in. Copy them, adapt them, and review the first run of each one closely. That's the whole curriculum.

Work through them roughly in order. The early ones teach you how Muse reasons; the later ones teach you how to trust it.

1. The morning brief

The classic first delegation. Connect your email and calendar, then ask for a prioritized start-of-day summary. It's bounded, you can instantly judge quality, and it shows you how Muse handles your life rather than a demo.

Try this brief

"Every weekday at 7am, go through my unread email and today's calendar. Give me: (1) anything needing a reply from me today, (2) anything time-sensitive I might have missed, (3) the rest grouped by topic. Don't send, delete, or archive anything. Show me the brief before doing anything else with it."

2. Inbox triage, supervised

Once the morning brief works, let Muse act on the inbox — filing newsletters, archiving receipts, drafting replies for your review. Keep "don't send anything" in the brief until you've watched a week of drafts. (Full playbook: Tame Your Inbox.)

Try this brief

"File promotional email and newsletters into a 'Reading' folder, archive order confirmations and receipts after noting the totals, and draft replies to anything that clearly needs one — but send nothing. Show me every draft before you file it."

3. A price watch

Your first background goal. Pick something you were going to buy anyway — a flight, a gadget, a hotel for a trip — and have Muse watch the price. This teaches you the Goals tab, background execution, and what "it comes back when something changes" feels like.

Try this brief

"Watch the price of [specific flight/product, with dates and details]. Check daily. Tell me immediately if it drops below $[your threshold], and give me a short weekly summary of the trend every Friday. Don't purchase anything."

4. Research with a deliverable

Ask for research that ends in something concrete — a comparison table, a shortlist with pros and cons, a one-page summary. The deliverable forces quality you can judge, unlike open-ended "research this."

Try this brief

"I'm choosing between [3 options]. Research all three and give me a comparison table: price, key differences, and who each is best for. End with your recommendation and one paragraph on why. Cite where each fact came from."

5. The weekly review

The goal that compounds. Every Friday, Muse summarizes what happened in your projects, inbox, and calendar that week. After a month, you'll have a written record of your own life — and you'll start noticing patterns you'd never have caught.

Try this brief

"Every Friday at 4pm, summarize my week: key emails and decisions, calendar highlights, and any open loops you can see (things mentioned but never resolved). Keep it to one page. Flag anything that looks like it slipped through the cracks."

Field note

The weekly review is the task that converted me from "interesting app" to "can't give this up." Week three's summary surfaced two commitments I'd made in passing and completely forgotten — one to a client. That single catch paid for the entire experiment.

6. Bill and subscription triage

Have Muse scan for bills, renewals, and subscriptions across your email. Most people find at least one subscription they've been paying for and not using — the task often pays for itself on the first run.

Try this brief

"Scan my email from the last 90 days for bills, renewals, and recurring subscriptions. List each with the amount, frequency, and next charge date. Flag anything that increased in price versus the previous cycle. Take no action — report only."

7. An errand from WhatsApp

Message Muse in WhatsApp like you'd text an assistant: "find me a plumber with good reviews near me and get me three options with availability this week." This is the surface where Muse feels least like software and most like staff — try it once to understand the appeal.

Try this brief

"I need [a plumber / a restaurant reservation / a gift for a 10-year-old]. Find three good options near [location/zip], with reviews and availability or ordering details. Don't book or buy anything — bring me the shortlist."

8. Meeting prep

Before an important call, have Muse pull together everything: the attendee's background, your last interaction, open items between you. Fifteen minutes of prep that used to take an hour of digging.

Try this brief

"I have a meeting with [name] on [date] about [topic]. Pull together: who they are, our last few email exchanges summarized, and any open items between us. One page, bullet points."

9. A tracker or artifact it builds for you

Ask Muse to build something persistent — a budget tracker, a project dashboard, a packing checklist, a document you keep updating. Artifacts are where Muse stops being a chat window and starts being infrastructure.

Try this brief

"Build me a simple tracker for [habit / project / budget]: what to record each day, a weekly summary view, and a monthly trend. Make it something I can update by just telling you what happened."

10. Your first real delegation

By now you've watched Muse reason about your inbox, your money, your calendar, and your errands. Pick the recurring task you hate most — the one you procrastinate on — and hand it over as a standing goal with a weekly check-in. This is the moment the app earns its place.

Try this brief

"Take over [the recurring task]: here's what done looks like, here are the boundaries, and here's what you always check with me about first. Run it on [schedule]. After the first two runs, we'll review together and adjust."

Caution

Don't make anything recurring until the one-off version has worked at least twice. A background task with a bad brief doesn't fail once — it fails on a schedule. The review habit from tasks 1–9 is what makes task 10 safe.

What these ten teach you

The pattern across all ten: briefs beat prompts. Outcome, boundaries, check-in — every time. Vague asks get vague work; precise briefs get surprisingly good work. By task ten you'll write briefs instinctively, and that's the actual skill this app rewards.

Where to go next: the inbox playbook for the deepest single workflow, the complete guide for the full operating picture, or Muse vs. Claude if you're deciding where each tool belongs in your week.

Quick answers

What should I do first in Muse?

A morning brief from your inbox and calendar — bounded, easy to judge, and it teaches you how Muse reasons about your actual life. Full starter list above.

Do I need to connect services for these?

Email unlocks most of the list; calendar adds the brief and meeting prep. Connect one at a time, only when a task needs it — that's the discipline that keeps the agent trustworthy.

How long until I'm comfortable delegating?

About a week of daily use. The first few tasks teach you the briefing pattern; by the end of the ten, writing a good brief feels natural.