7 Ways to Use AI While You Sleep

Using AI while you sleep means handing a job to something that runs with nobody in the room, then finding the result waiting in the morning. No metaphor involved. A real run, on a real clock, producing something you read at seven with a coffee.

Here's what most advice on this skips. Sitting in a chat window quietly caps every job at the length of your patience, which for most of us is somewhere between thirty seconds and two minutes. So you ask for a summary instead of a survey. Three options instead of thirty. The shape of an answer instead of the answer. Then you close the tab and the machine sits idle for eight hours while you're unconscious. That gap is the largest uninterrupted block of time you own, and almost nobody spends it.

Seven ideas below. None of them is a morning news digest, because that idea is already everywhere and this column has covered it. Each one ends with something you can start tonight.

1. Ask the Question That's Too Big for Your Patience

Long-running agent modes changed what a question can be. A run that reads forty sources, follows what it finds, notices its own contradiction, and goes back to check can take forty minutes and produce something no two-minute answer resembles. Nobody sits through a forty-minute run. Asleep, you don't have to.

The shift is small and it moves the whole game. Once your attention stops being the expensive resource, the expensive resource becomes the brief.

A one-line question gets a one-line-shaped answer no matter how long the machine chews on it. So write the brief instead: what you're deciding, what you already believe, what evidence would change your mind, and what the output should look like when it lands. Ten minutes of writing before bed buys you an hour of work you would never have sat through.

Start today: Take the question you've been half-asking yourself for a month and give it three headings: what I'm deciding, what I already believe, what would change my mind. Start a deep research or agent run on it before you close the laptop. If you want the same brief answered every week without rewriting it, that's a research run that repeats on a schedule.

2. Run the Same Job Three Ways and Read the Comparison Over Coffee

While you're awake you get one attempt at most things, because a second attempt costs another block of attention you'd rather spend elsewhere. Asleep, attempts are close to free.

So run the same brief three times with deliberately different framings. One argues for the thing. One argues against it. One assumes a constraint the others don't have: half the budget, nobody new hired, delivered in a week. Then, in the morning, hand all three outputs back and ask for a table of where they agree and where they split.

Read for the seam. Agreement across three hostile framings is a decent proxy for a claim that holds up. The places where they split are your reading list, and they're usually the two or three things you were quietly unsure about anyway.

Start today: Pick a decision you're stuck on and write one brief. Copy it into three tabs and add one line to each: "argue for this," "argue against this," "assume the budget is halved." Leave all three running. In the morning paste the outputs back in and ask for a table of agreements and contradictions.

3. Pay Half Price for Being Willing to Wait

Latency became a currency and almost nobody outside engineering noticed.

Every large provider now sells a slower lane. Submit a pile of requests as a file, accept that results come back inside 24 hours instead of instantly, and pay half. OpenAI's Batch API takes up to 50,000 requests in one submission at a 50% discount with a 24-hour turnaround. Anthropic's Message Batches does the same at up to 100,000 requests, also at half price on both input and output, with most batches finishing well inside an hour.

Fifty percent off reads like a procurement footnote. It changes what's worth doing at all. Classify every support ticket from the last three years. Tag every image in the archive. Score every inbound lead since January. Those are jobs you'd never approve at full price and obviously approve at half, and the only thing you traded away was watching it happen.

The honest catch: batching means writing your requests into a file rather than typing them one at a time, which is a genuine step up in effort. It's also the same step that turns a task you keep repeating into one you run once.

Start today: Count the biggest one-off job you've been avoiding in units rather than hours. Two thousand rows? Eight hundred emails? Anything over a few hundred belongs in a batch and not in a chat window. Price it out at the per-item cost, then halve it. The number is usually smaller than one hour of your time.

4. Put Something on the Overnight Watch

Marcus runs a two-van appliance repair business outside Fresno. His morning starts with the same four browser tabs: a distributor's parts availability page, two supplier price lists, and the county permit portal. Three of them haven't changed in weeks. He checks anyway, because the one morning something does change is the morning it costs him a job.

That's not a research problem. It's a watch problem, and it's the purest overnight job there is. Something changes without telling you, and you want to be told.

People are terrible at this and a scheduled agent is very good at it, for an unglamorous reason: the agent doesn't get bored on night four hundred. It reads the same page with the same attention it had on night one, compares it to what was there yesterday, and stays quiet unless the comparison turns up something.

One design rule keeps a watch useful instead of noisy. Report changes, never state. A watch that emails you every single morning becomes one more thing to skim and dies within a month. A watch that says nothing for eleven days and then tells you the part is back in stock, with the line that changed, is the one you'll still have running next year.

This is the item you hand off rather than keep doing yourself. Describe the page, describe what counts as a change, say where you want to hear about it, and you've got a standing check that runs every night and reports only what moved.

Start today: Open your browser history and find the URL you visit most often without ever doing anything there. That's your first watch. Write one sentence: "tell me when ___ on this page changes." That sentence is the whole specification.

5. Give the Pile That's Too Big for an Afternoon a Whole Night

Delia has photographed weddings for eleven years. Her archive runs to 240 folders with names like "FINAL_v3_use_this" and "oct backup." She has tried to fix it four times. Every attempt died somewhere around folder nineteen, because the job isn't hard, it's just longer than any afternoon she can spare.

Overnight jobs get measured in items, not minutes. That's the reframe. The pile that defeats you is rarely difficult. It's numerous.

So point a run at it: read each file, generate a real name from what's inside, propose a folder, write the entire plan to a spreadsheet, and change nothing. That last clause carries most of the weight. A run that renames 240 folders while you're asleep is a nightmare with a small chance of being a gift. A run that hands you a proposed mapping to approve over coffee is neither risky nor slow.

Propose, don't perform. The same shape works on a decade of receipts, a folder of untitled PDFs, six years of meeting recordings, a photo library with no captions. Turning files you already own into something searchable is one of the few jobs where the overnight window is the only window that fits.

Start today: Don't start with all 240. Take fifty. Run the propose-a-mapping job on those tonight and check in the morning how many of the proposed names you'd keep. If it's most of them, run the rest tomorrow night.

6. Build In a Way to Find Out It Failed at 1am

Unattended work fails quietly. A run starts at 1:40am, hits a login that expired on Tuesday, writes an error into a file nobody opens, and stops. You find out at nine, having planned your morning around an output that doesn't exist. At that point the run has cost you more time than it ever saved.

Every overnight setup you trust answers three questions: did it run, did it finish, and did it produce anything. Those are three different failures, and they need three different signals.

The move operations people use is a dead man's switch. Rather than asking to be alerted when something breaks, you arrange to be alerted when a heartbeat stops. Healthchecks.io does this on a free tier: your job pings a URL when it finishes, and if that ping doesn't arrive by the time you specified, you hear about it. Silence becomes the alarm instead of the default.

Then the smaller discipline, which costs one line. Make "ran and found nothing" look different from "didn't run." A watch that stays quiet on an uneventful night is indistinguishable from a watch that died in July.

Start today: For whatever you set running tonight, decide right now what proof of life looks like in the morning. A file with a timestamp. A one-line log. A message that says "checked, nothing changed." If you can't name the proof, you don't have an overnight job yet. You have a hope.

7. The Best Thing to Run Tonight Might Not Use AI at All

Worth saying plainly, because this list would be dishonest without it. A good share of the value in the overnight window has nothing to do with AI.

The full export from a system you're leaving. The backup you keep deferring. Eight hours of video that needs transcoding. Four hundred gigabytes syncing to another drive with rclone, which is free, unexciting, and has been doing this reliably since long before any of the current wave. Your computer already ships with a scheduler for all of it: Task Scheduler on Windows, launchd or a cron entry on a Mac. No account, no model, no tokens.

Here's a rule that sorts the two cleanly. If the job needs a judgment call about content, it wants a model. If it only needs time and a copy of the file, it wants a scheduler and nothing else.

This belongs in the list because people burn weeks building an intelligent version of a job that a five-line scheduled script has handled dependably for twenty years. Check for the boring answer first.

Start today: Write down the three things you want done by tomorrow morning. Mark each one M if it requires judgment about content and T if it only requires time. Run the T list tonight with your operating system's scheduler. Save your effort for the M list.

Pick One

Seven ideas, and attempting all of them tonight is the reliable way to have done none of them by Thursday. Take the one that made you sit up. If nothing did, take number four, because a watch you describe once keeps paying every morning for years and takes about ten minutes to set up.

One thing worth knowing before you start. None of this requires your laptop to be open. These jobs run on somebody else's machine, and the difference between a clever idea and a habit is usually whether it survives you closing the lid. Sunday's roundup reports what changed, Wednesday's Loop builds one workflow end to end, and this column hands you the ideas in between. To see what other people have put on the night shift, the workflow directory is the fastest browse on the site.

Frequently Asked Questions

• Does my computer have to stay on all night for this to work?+
  No, and that difference is what turns an overnight idea into an overnight habit. Batch jobs, scheduled agents, and hosted runs all execute on the provider's machines, so your laptop can be shut and in a bag. The exception is anything running on your own hardware, like a model you installed yourself or a large local file sync. Those need the machine awake and plugged in. If you want the run to be independent of your laptop entirely, the cloud runtimes that run an agent for you covers what that setup looks like.
• Is it risky to let AI do things when nobody is watching?+
  It carries real risk when the run performs changes. It carries almost none when the run proposes them. Most of the ideas here are built as propose-then-approve for that reason: the overnight job writes a plan, a mapping, a draft, or a list of differences, and you spend four minutes approving it over coffee. Save the perform-it-automatically pattern for jobs that are reversible and cheap to undo.
• How is an overnight run different from setting a reminder?+
  A reminder moves the work to a later version of you. An overnight run means the work is finished when you wake up. A reminder to check the supplier page still costs you five minutes every morning. A watch on the supplier page costs you nothing on the days when nothing changed.
• Do I need to pay for anything to try this?+
  No. Scheduled runs, file syncs, and heartbeat monitoring all have free options. Batch pricing is a discount on usage you were already going to pay for rather than a subscription you add. If cost is the constraint, the free-tier edition of this column covers what is possible with no paid plan at all.