Claude Schedule

It’s 6:47 AM and the competitive intel report is already waiting in your inbox. You didn’t write a prompt this morning. You didn’t even open your laptop yet. Claude ran the analysis at 5:00 AM, pulled the latest from your tracked competitors, compared it against last week’s snapshot, and delivered a summary to your inbox before your alarm went off.

That’s not a feature. That’s a fundamentally different relationship with AI.

Most people use Claude the same way they use Google — reactively. They have a problem, they open the app, they type something. Claude answers. Session ends. Claude forgets it happened. You come back tomorrow and start over. The model is sitting idle 23 hours a day, waiting for you to remember it exists.

Claude Schedule breaks that pattern. It turns Claude from a tool you pick up into a system that runs alongside your work — processing, monitoring, reporting — whether you’re in the room or not. Cowork has /schedule for recurring task cadences. Claude Code has /loop for tight operational cycles. Together they give you something most executives don’t think to build: a Claude that works the night shift.

Here’s how to set it up.

---

Step 1: Understand What Schedule Actually Is

Before you configure anything, get the mental model right, because the failure mode here is treating Schedule like a calendar reminder. It’s not.

A calendar reminder says “do this at 9 AM.” Schedule says “run this entire Claude workflow at 9 AM, with no human in the loop.” That’s a different thing. It means the prompt you write today will execute — unchanged — on Tuesday, next Tuesday, and the Tuesday after that. The output quality scales directly with the prompt quality. A lazy prompt produces lazy recurring output. A sharp prompt produces sharp recurring intelligence.

There are two implementations.

Claude Cowork /schedule is designed for business cadences — daily briefings, weekly reports, Monday morning pipeline summaries. You set a natural-language schedule (”every weekday at 7 AM”), attach a prompt or task, and Cowork runs it on that interval. Output lands wherever you’ve configured it: in the conversation thread, in a connected integration, in a document. Think of this as your recurring content and intelligence layer.

Claude Code /loop is designed for operational monitoring — tighter cycles, often measured in minutes rather than days. The syntax is direct: /loop 5m /check-deploy runs the /check-deploy command every five minutes until you stop it. This is your CI/CD babysitter, your deploy watcher, your PR queue monitor. It’s built for the terminal, not the boardroom.

Both share one critical constraint you need to internalize before you build anything on top of them: the computer has to stay awake and the app has to be running. These are not cloud-scheduled jobs. There’s no server executing your tasks while your MacBook is in a bag at 35,000 feet. If your machine sleeps, your schedule sleeps. If you quit the app, the loop dies.

This isn’t a bug you need to work around — it’s a design constraint you need to plan around. Set your energy settings to prevent sleep when these workflows matter. Or run them on a machine that stays on. The executives who get the most out of Schedule have a designated machine — an old MacBook, a Mac Mini, something that never closes — where Claude runs continuously. That’s the move.

---

Step 2: Set Up Your First Scheduled Task in Cowork

Open Claude Cowork and type /schedule in any conversation. Cowork will walk you through the configuration in natural language. You’ll set three things: the timing, the task, and the output.

Timing. Cowork accepts plain English. “Every weekday at 7 AM.” “Every Monday at 9 AM.” “Daily at 6:30 AM.” Don’t overthink the syntax — it’s genuinely conversational. If it misreads your intent, it’ll confirm before saving.

The task. This is your prompt. Write it like you’re writing for a future version of yourself who forgot everything about this project. Include the context you’d normally carry in your head. If you want competitive intel, don’t just say “check on competitors” — tell it which competitors, what signals matter, how you want the output framed. A good scheduled prompt is more explicit than a live prompt, because there’s no back-and-forth to course-correct.

Output. Where does the result go? By default it surfaces in the conversation thread. If you’ve connected integrations, you can route output to email, Slack, or a document.

For Claude Code /loop, the setup is in the terminal. Navigate to your project directory, make sure you have a /check-deploy skill (or whatever command you want to loop) defined, and run:

/loop 5m /check-deploy

That’s it. Claude Code will execute /check-deploy every five minutes, print the result, and run again. Hit Ctrl+C to stop. You can loop any skill, any slash command, or any plain prompt.

The key discipline with /loop: keep the looped command tight and stateless. It should be designed to run in isolation, give you a clear status in a few lines, and complete cleanly. Don’t loop long analytical tasks — that’s what /schedule is for. Loop status checks, monitors, and watchers.

---

Step 3: Build a Daily Morning Briefing

This is the first scheduled workflow worth building, because you’ll feel the value immediately and it trains you on what good scheduled prompts look like.

Here’s the prompt structure that works. In Cowork, schedule this for every weekday at 6:30 AM (or whenever you actually look at your phone before your first meeting):

Good morning. Give me a daily briefing covering:

1. What's on my calendar today (if calendar is connected) — key meetings and prep I need to do
2. Any open threads or unresolved questions from our recent conversations
3. One thing I should be thinking about that I probably haven't looked at in the last 48 hours

Keep it under 200 words. Be direct. If there's nothing notable, say so.

Adjust the three bullets to match your actual priorities. The point is specificity. “Daily briefing” without structure produces a vague summary. “These three specific things” produces something you can act on in 90 seconds.

After it runs for a week, you’ll start to notice what’s missing and what’s noise. That’s the signal to edit the prompt. Scheduled prompts are living documents — refine them the same way you’d refine any process that runs repeatedly.

What changes when this is working: you stop starting your day in reactive mode. You come into the morning with a frame already built, which means the first hour of work produces more than the next three would have without it.

---