Make Claude work while you sleep: the overnight setup

Most people use Claude for five minutes and close the tab. It can actually run for hours on its own, finishing real work while you sleep. Here are the four ways to set that up, all inside Claude Code (the free desktop app): what each one is, when to use it, where it falls short, and the one trick that makes any of them actually work. Anthropic's own docs are linked in each section if you want to go deeper.

Give it a goal 🎯

What it is: you type /goal and a finish line, and Claude keeps working and checking its own output until it hits that goal, instead of stopping at the first answer.

Use it when: you have a batch with a clear pass or fail, like "make ten carousels and don't stop until each one passes my checklist".

/goal make ten carousels and don't stop until each one passes my checklist

Go deeper: Keep Claude working toward a goal

Put it on a schedule ⏰

What it is: a routine that runs Claude on a timer (say 6am daily) on Anthropic's cloud, so your laptop can be shut.

Use it when: recurring online work, like a morning brief pulled from your Notion or inbox.

Set a routine to run every morning at 6am, do the job, and leave the result waiting for you.

Go deeper: Automate work with routines

Put it on a loop 🔁

What it is: /loop re-runs the same task on a time interval (say every hour) in an open session.

Use it when: you want Claude to keep checking for and clearing new work over a few hours.

/loop every hour, check for new work and clear it

Go deeper: Claude Code commands

Clone it into a team 👥

What it is: instead of one Claude, it spins up a team of sub-agents that work at the same time.

Use it when: a big batch you want done fast, or work that splits into parallel parts.

Spin up a team of sub-agents to tackle a big batch in parallel.

Go deeper: Orchestrate subagents with workflows

The trick that makes it all work: a progress file 📓

What it is: a simple notes file Claude updates as it goes and re-reads to stay on track.

Use it when: any long job. On a big run Claude's memory fills up and older details get summarized away, the progress file is the part it never loses.

Tell Claude: keep a progress file as you go, and re-read it before each step so you never lose your place.

How to get the most out of it 🎓

1. ☕ Keep your Mac awake for local runs. open a terminal and run caffeinate -i, then close it in the morning.
2. 🎯 Always give a measurable finish line so Claude can check its own work.
3. 🐣 Match it to your level. New to this? Start with a goal on a small job you can verify. Already comfortable? Combine a team plus a progress file for a big overnight batch.

The honest bit ✅