The Nightly Audit: Let Muse Clean Up While You Sleep

Every computer accumulates the same four messes: a Downloads folder that only grows, receipts scattered through email, a bookmark bar nobody reads, and a phone camera roll full of screenshots of things you will never look up again. I have all four. I clean none of them by hand anymore. Each one has a nightly audit, and each morning I get a short report telling me what changed.

A nightly audit is a scheduled routine with one job: look at a recurring mess and report what it found. That is the whole pattern. It works because the messes that deserve an audit share three traits. They regenerate (there will always be more downloads), they are read-only friendly (looking costs nothing, acting needs you), and they are boring enough that you will never do them manually. Our scheduled routines lesson covers the mechanics of setting up recurring jobs; this lesson is the practitioner’s pattern for turning those jobs into a cleanup crew.

The four lines every audit needs

Vague audits produce vague reports you stop reading. Every audit I run is written with the same four lines, which are the scheduled-routine version of the four-part task brief from our task briefs lesson.

Scope names exactly what the audit looks at: a folder, an inbox label, a time window. Not “my files” — “files in ~/Downloads older than 30 days.” The tighter the scope, the shorter the report.

Rules are the sorting logic: what counts as clutter, what counts as worth flagging, what the audit must ignore. This is where you protect the things you keep on purpose. My downloads audit ignores installer files, because I keep three of them.

Report is the output contract: format, order, length cap. The length cap is the load-bearing line. An audit without one will eventually send you a 40-row table, and you will stop opening it. We will come back to this in the failure note.

Approval line states what the audit is never allowed to do unsupervised: no moving, no deleting, no unsubscribing, no archiving. Audits look. You act.

Here is how the pattern maps onto the four classic messes:

Three prompts you can paste tonight

These are the three I run. Copy one, adjust the paths and names to your life, and say it to Muse in plain chat to create the routine.

1. The Downloads Audit

Every night at 2:00am, audit my Downloads folder. List files older than 30 days with their sizes, largest first, capped at 15 items. Ignore anything with “setup” or “installer” in the name. Report back in the morning with just the list and a one-line total of how much space they take. Read-only: never move, rename, or delete anything.

2. The Expense Sweep

Every night at 2:00am, scan my Gmail for receipts and charges that arrived today. Log the merchant and amount in a running list. Flag anything over $100 that I have not been charged by before, and anything that looks like a duplicate. Read-only: flag only, never dispute charges or contact merchants.

3. The Bookmark Review

Every Sunday at 9:00pm, review my browser bookmarks. List bookmark folders I have not opened in the last 90 days, with the three most recent items in each. Read-only: list only, never delete a bookmark.

The first week, read each report carefully. You are checking the audit’s judgment: is it flagging the right things, ignoring the right things, and staying short? Reply in the routine’s thread to correct it (“keep ignoring installer files”) and the correction sticks. Once the corrections stop, the audit is trained. That is also the moment to teach a standing instruction if you find yourself repeating a correction; our memory lesson shows how.

A named setup: The 2AM Tidy-Up

Here is my complete named setup. The 2AM Tidy-Up is actually two routines that fire together, one mess each.

The 2AM Tidy-Up

• Cadence: Nightly at 2:00am, America/Chicago.
• Routines: The Downloads Audit and the Expense Sweep, same schedule, separate threads so each report stays readable.
• Connectors required: Gmail for the expense sweep. The downloads audit needs nothing except file access.
• Scope: Downloads folder, 30-day window, installers excluded; Gmail receipts, same-day window, $100 flag threshold.
• Report contract: One combined morning thread per audit, 15 items max, total space and total spend summarized in the last line.
• Approval line: Read-only on both. If the expense sweep flags a duplicate charge, it asks me what to do; it never acts.
• Review rhythm: First week I read every report. Monthly, I ask “what reminders do I have?” and confirm both are still running and still short.

Two details from experience. First, 2:00am is deliberate: nothing arrives while I am working, so the morning report is the first thing waiting, and a report that arrives mid-day gets buried. Second, the two audits share a schedule but not a thread. The first version combined them into one report, and the expense section got ignored because it sat below a long downloads list. So the threads stay separate, and each report gets full attention.

Academy Put Muse on a Schedule: Routines That Run While You Sleep

If you have not set up a scheduled routine before, start with the routines lesson above, which covers the exact mechanics: how to create one in chat, where results arrive, and how to see and cancel everything you have running.

The approval line is the whole safety story

An audit that only looks cannot hurt you. The approval line is what keeps it looking. State it in every audit prompt, even when it feels obvious: “read-only, never move or delete.” Sentinel enforces the same boundary at the system level; our Sentinel permissions guide explains how to set the gates so a routine cannot quietly escalate itself.

The line gets tested in one specific way: the audit finds something you obviously want gone, and nudges you. “Three duplicates found. Want me to dispute them?” That is the correct behavior. Let it draft the dispute or the unsubscribe and hold it for your tap, the same draft-then-human-send pattern our inbox triage lesson uses for email replies. An audit that deletes the duplicate charge itself is an audit that will eventually delete the charge you were expecting.

What can go wrong

Here is the honest failure note. My first downloads audit worked perfectly for three days, and then the report grew. It found more old files each night, the list hit 40 rows, and by Friday I was skimming past the whole thread. The audit had not malfunctioned. It had outgrown my attention.

The fix was two lines added to the prompt: “cap the list at 15 items” and “if nothing meets the criteria, reply with one line: nothing to report.” The second line matters as much as the first. A quiet night that says so in one line is proof the audit is alive and watching. A routine that goes silent for a week teaches you to stop checking it, which is how stale routines die unnoticed; our failure modes lesson calls this out as the quietest way scheduled jobs break.

Two habits keep audits honest. Read the reports for the first week, not just the first day; audits degrade gradually, and a day-one check misses it. And once a month, ask “what reminders do I have?” and kill any audit whose reports you have stopped opening. An audit you ignore is a mess with extra steps.

Start with the mess that bothers you most

Do not set up all three audits tonight. Pick the mess that annoys you most, probably the Downloads folder, and give it the nightly audit prompt. Read the report every morning for a week. Correct it in the thread when it flags something you keep on purpose. Add the cap when the list gets long.

Six weeks from now you will have a set of routines that start working before you wake up, and a morning report that takes ninety seconds to read. The mess will still regenerate. That is the point of the audit: the mess never ends, but neither does the cleanup.