9 things to delegate to Meta Muse for work. Email, meetings, research, and coding — delegate the busywork to Meta Muse, each case with a copy-paste prompt.
The job: One summary at 8am: what arrived overnight, what needs you, what can wait.
Every weekday at 8am, summarize emails received since 6pm yesterday. Format: 🔴 needs a reply today (with a one-line draft I can approve), 🟡 FYI worth knowing, ⚪ everything else in one line each. Skip newsletters, promotions and notifications. Keep the whole digest under 300 words.
Why it works: a strict output format (and word cap) prevents the classic failure mode: an "executive summary" longer than the inbox itself.
The job: You bought something; the price drops a week later. Muse catches it and files the price-adjustment claim.
Track these recent purchases for 30 days: [item + order link]. If the price drops by more than [$20], check the retailer's price-adjustment policy and file a claim on my behalf. For anything under [$20], just log it in a monthly summary. Ask me before submitting any claim that requires agreeing to new terms.
The job: A musician handed Muse his Meta Ads: it organized a messy Ads Manager, optimized spend, and ran campaigns driving traffic to Spotify and YouTube from his Instagram videos — "two months of admin in one day."
I run Meta ads to drive traffic to my [Spotify artist page]. Audit my Ads Manager: consolidate the messy campaigns, pause anything under [target ROAS], and shift budget to the winners. Draft next week's creative rotation from my latest [5] Instagram videos. Show me every change for approval before you touch a live campaign.
Why it works: creative and media buying in one loop — Muse sees both the videos and the numbers. The approval gate on live campaigns is non-negotiable when real ad spend is involved.
The job: During an active job search: inbox organized, application updates monitored, two offers' benefits compared side by side, decline email drafted — plus concert tickets, a barber slot, and dinner reservations on the side.
I'm job hunting. Every morning: scan my email for application updates and summarize what's new. Keep a tracker: company, role, stage, next step, deadline. When I have competing offers, compare them in a table — salary, equity, PTO, health, remote policy. Draft acceptance and decline emails, but send nothing without my approval.
Why it works: a high-stakes bundle where the agent's memory (every application, every stage) beats your spreadsheet — and the draft-not-send rule protects the relationships.
The job: Overnight summaries across messaging apps, a daily briefing combining calendar + email, scam-detection alerts — plus Instagram analytics and Spotify history reviews on demand.
Every morning at 7:30: summarize what came in overnight across [WhatsApp, Messenger, email] — one line each, and flag anything where someone is waiting on me. Then brief my day: calendar events plus anything in email that affects them. Flag anything that smells like a scam or phishing. Keep the whole thing under 250 words.
Why it works: the agent reads five inboxes so you read one brief. The scam-flagging is a bonus only an always-on reader can provide.
The job: One user ran Muse side-by-side against another agent and reported a higher success rate — praising the working-state indicators, approvals UI, and memory. His caveat: CAPTCHAs and logins can still need manual takeover.
I want to stress-test you on a real task: [organize last week's inbox into action items]. Narrate what you're doing as you go, ask approval before anything irreversible, and at the end give me an honest report: what worked, what you couldn't do, and where you needed me. No sugar-coating.
Why it works: turn evaluation into a delegation — the "no sugar-coating" report tells you exactly where the agent's limits are before you trust it with bigger jobs.
The job: A fashion designer stopped asking Muse simple questions and started assigning real work. First job: analyze her posts and saved reels to learn her aesthetic, producing a taste profile matching her brand voice. Then she delegated two creative projects at once against that profile.
Study my last [50 Instagram posts and 30 saved reels]. Objective: write a 1-page taste profile of my aesthetic — colors, silhouettes, moods, what I avoid. Then, using that profile, plan [a teen fashion shoot]: propose [3 concepts], each with venue ideas, a shot list, and a prop list, all consistent with the profile. Do not contact any vendor or spend anything without asking me first — I approve concepts before you move to logistics.
Why it works: The hardest part of creative work is "getting the vibe right." Have the agent distill a taste profile from your own history once, and every future output is judged against the same yardstick.
The job: You think faster than you type. Muse Voice Transcribe (launched Sep 2026) turns speech into finished text anywhere — on Mac, press Fn and dictate. It cleans up filler words, keeps your tone, and structures the output.
Transcribe what I'm about to dictate and turn it into [a concise email to my team about the Q4 plan]. Remove filler words, keep my tone [direct but warm], and structure it with [3 bullet points]. Read the draft back to me for approval before sending — never send without my sign-off.
Why it works: speaking is roughly 3× faster than typing, and the model handles 70+ languages — dictate in one language, get a clean draft in another. The approval step keeps it safe for anything outbound.
Built on Muse Voice Transcribe, launched September 2026
The job: You have a repo, a bug list, and no patience for boilerplate. Muse Code (beta for macOS and Linux) runs persistent coding agents in separate worktrees — several tasks in flight at once, with a replay-exact event log of everything it did.
In [repo path]: fix [the flaky checkout test] and add [input validation to the signup form]. Work on each in a separate worktree, run the test suite after every change, and summarize the diff for my review. Do not push, merge, or deploy anything — changes stay local until I approve.
Why it works: separate worktrees mean parallel agents never step on each other's changes, and the event log lets you replay exactly what happened. You stop writing code and start reviewing it.