Put Muse on a Schedule: Routines That Run While You Sleep
The biggest unlock after your first tasks: jobs Muse runs on its own. How to set up a morning briefing, an inbox sweep, and a Friday review — and which jobs are safe unattended.
By Professor Muse9 min read
The first time you ask Muse to do something, you watch it work. The tenth time, you close the app and go make coffee. Somewhere around the twentieth, you realize the real question is what it can do without being asked at all.
That is what scheduled routines are. You describe a job and when it should run, and Muse does it on its own, in the background, whether or not you have the app open. I run three of them: a morning briefing every weekday, an inbox sweep twice a day, and a Friday expense review. They took about fifteen minutes total to set up, and they are the highest-value things I have ever delegated to an agent. This lesson shows you how to set up the same three, and how to think about what is safe to run while you sleep.
The short version
- A scheduled routine is a job description plus a time: “every weekday at 7am, build my morning briefing.”
- You create one by telling Muse in plain chat; it confirms the schedule and runs it until you cancel it.
- Write each routine with four parts: when it runs, what it may look at, exactly what it should deliver, and what it must never do unsupervised.
- Read-only jobs are safe to run unattended. Anything that sends, buys, books, or deletes should pause for your approval.
How scheduling actually works
There is no settings screen full of cron syntax. You schedule a routine the same way you ask Muse for anything else: in chat. Say “every weekday at 7am, send me a briefing on my day,” and Muse creates the recurring task and confirms the details back to you, including the exact time.
A few mechanics worth knowing:
- Routines run in the background whether or not you are in the conversation. You do not need the app open.
- When a routine fires, its result arrives as a message in your conversation with Muse, like any other reply.
- Times follow your time zone. If you ask for a time that has already passed, Muse flags it and suggests an alternative instead of silently scheduling something in the past.
- Recurring tasks keep running until you cancel them. To see everything scheduled, ask “what reminders do I have?” or tap your assistant icon and open the Upcoming tab. To change or kill one, just say so: “cancel my Friday review” or “move the briefing to 7:30.”
That is the whole interface. What makes or breaks a routine is the job description. A vague routine produces vague output on a schedule, which is worse than no routine at all because it trains you to ignore it.
The four-part routine brief
Every routine I run is written with the same four parts. It takes two extra minutes and it is the difference between a routine you trust and one you mute after a week.
- Cadence. When it runs, stated exactly: “every weekday at 7:00am,” not “in the mornings.”
- Sources. What it is allowed to look at: your calendar, your inbox, the weather, a website. Name them.
- Deliverable. Exactly what the output looks like, with a length cap. “Five bullets, under 200 words” beats “a summary.”
- Boundaries. What it must never do without you. This is the load-bearing part, and we will come back to it.
Think of it as a function signature: explicit inputs, explicit outputs, explicit side-effect permissions. Our task briefs lesson covers the same discipline for one-off tasks; routines just apply it to jobs that repeat.
Routine 1: The morning briefing
This is the canonical first routine, and for good reason: it has the highest value per minute of setup. Every weekday morning, before you have opened a single tab, Muse assembles what you need to know about the day.
Here is a prompt you can paste, then adjust to your life:
Every weekday at 7:00am, build my morning briefing from my Google Calendar, my Gmail, and the current weather. The briefing has four sections in this order: (1) today’s meetings with locations and travel time between them, (2) overnight email that needs my attention, one line each, (3) weather and whether it affects anything scheduled, (4) one tech headline relevant to my work. Keep the whole thing under 300 words. This is read-only: do not send messages, book, or buy anything.
Why this works: the order follows decision value (calendar first, because it drives the day), the word cap keeps it skimmable, and the boundary line at the end means it never acts on your behalf. Without the length cap, briefings sprawl. Without the boundary, a helpful agent might notice a flight conflict and rebook you before you have had coffee.
This routine needs two connectors to be useful: your calendar and your email. If you have not connected them yet, our connectors guide walks through it. The routine still works without them, but it becomes a weather-and-news digest, which your phone already does.
Routine 2: The inbox sweep
Email is where scheduled routines earn their keep, because the job is identical every day and nobody enjoys it. I run mine twice daily: once before lunch, once before I wrap up.
Paste and adjust:
Twice a day, at 11:30am and 4:30pm, scan my Gmail for messages that arrived since your last sweep. Sort each message into three buckets: needs a reply from me, worth knowing, or noise. For “needs a reply,” draft a response and hold it for my review. Do not send anything. For “worth knowing,” give me one line each. Ignore noise completely. Report back with the drafts first, then the one-liners, in under 250 words.
State the send boundary in every routine that touches email, even if you think it is obvious: “draft a response and hold it for my review. Do not send anything.” Our inbox triage lesson goes deeper on the triage technique itself; the routine just puts it on a schedule.
One design detail: the time-boxed scan window (“since your last sweep”) keeps the job fast and stops it from re-reading old mail. Without a window, a scheduled job can drift into reprocessing the same messages, and your sweep slowly becomes a history lesson.
Routine 3: The Friday expense review
Weekly routines catch what daily ones miss. Day to day, individual purchases feel handled; the Friday roll-up is where you notice the subscription you forgot or the charge you do not recognize.
Every Friday at 5:00pm, review my recent spending. Pull the last 7 days of transactions from my connected bank and card accounts. Flag anything that looks like a duplicate charge, a subscription I may have forgotten, or spending notably above my normal pattern. Present it as a short list with amounts, and end with one question: anything here you want me to look into? Read-only: do not dispute charges or contact merchants.
Note the boundary again: flagging is the job; acting on the flags is yours. A routine that disputes charges on its own is a routine you will regret.
A named setup: The 7AM Briefing
To make this concrete, here is my actual morning routine as a complete, named setup you can copy. I call it the 7AM Briefing.
The 7AM Briefing
- Cadence: Every weekday at 7:00am, America/Chicago.
- Connectors required: Google Calendar, Gmail.
- Prompt: the morning briefing prompt above, with one addition at the end of the deliverable section: “If I have no meetings today, say so in the first line instead of listing an empty calendar.”
- Boundaries: Read-only. No sending, booking, buying, or calendar changes.
- How I check it: I read it with coffee. If it ever arrives empty or wrong, I reply in the thread (“you missed my 9am standup”) and the correction sticks for future runs.
- Review rhythm: Once a month I ask “what reminders do I have?” and confirm the 7AM Briefing is still the only morning routine. Routines are easy to set and easy to forget; the monthly check keeps them honest.
A routine you never review is a routine that can quietly go stale, which brings us to the failure modes.
What is safe to run while you sleep
The rule I use: read-only jobs run unattended; anything that changes the world waits for you.
Safe on autopilot: briefings, summaries, sweeps, monitoring, research digests, draft preparation. These produce information. If one goes wrong, the cost is a bad message you can ignore.
Needs your approval: sending email, spending money, booking travel, deleting files, changing calendar events, contacting other people. These change things outside the conversation. Muse’s Sentinel permissions are the enforcement layer here: our Sentinel guide explains how to set how often Muse must ask before acting, and scheduled routines respect those same gates. A routine cannot quietly bypass a permission you set while awake. If a Friday expense review tries to dispute a charge, Sentinel stops it and waits for your tap, the same as if you had asked in chat.
What can go wrong
Here is the honest failure note, from experience. My morning briefing once went quietly stale for two weeks.
What happened: I changed the name of a recurring calendar event, and the briefing kept reporting the old title from a cached pattern instead of reading the calendar fresh. Nothing errored. Nothing looked broken. The briefing arrived every morning at 7:00, confident and slightly wrong.
The fix was simple once I noticed: I replied in the routine’s thread, told it the event name had changed, and asked it to always read the calendar directly rather than relying on what it remembered. The lesson: scheduled routines fail silently. Nobody is watching when they run, so a degrading routine does not get the “hey, that looks off” reaction a live conversation gets.
Two habits prevent this:
- Read the output. Actually read it, at least skim, for the first two weeks of any new routine. You are training your own trust as much as the routine.
- Audit monthly. Ask “what reminders do I have?” once a month, open the Upcoming tab, and confirm each routine still exists, still has the right schedule, and still produces output you would defend.
A routine that survives a month of your actual attention is a routine you can trust for a year.
Start with one
Do not set up all three routines today. Set up one: the morning briefing. Read it for a week. Notice what is missing (mine needed the “say so if I have no meetings” line; yours will need something else). Fix it in the thread. Then add the inbox sweep, and only then the Friday review.
The pattern is always the same: one routine, one week of attention, then the next. Six weeks from now you will have an assistant that starts working before you wake up, and you will wonder why you ever started your days with twenty open tabs.
