Issue #9: Set It And Forget It

New here? If this landed in spam or promotions, drag it to your inbox and mark it "not junk" so you don't miss next week. Takes five seconds and it genuinely helps.

First, an apology. It's been a couple of weeks since I last landed in your inbox. I was traveling, life got loud, and this had to wait. Thank you for still being here.

Being away got me looking back at how far we've come, so let me take one beat before we add the next piece. We started with the only thing that mattered: you are not behind. From there we taught Claude to go deep on what you care about, to remember you, and to run the errands you used to do by hand. We drew the map of chat, co-work, and code. We built real apps with no code. We gave it hands into your calendar and inbox. Last week we taught it a recipe it keeps. A lot of you had never done one of those things a couple of months ago, and now they are just things you do.

Here's the honest truth under all of it: this is genuinely easy once you spend a little time with it. That is the whole secret, reps, not talent. You can do all of it right in your browser, download the desktop app when you want more, or even run it from your phone through the browser, from a chair by the pool. The part that still gets me is that it can do real work for you while you are off doing something else entirely. That is exactly where we're going today.

One quick ask before we dive in: I would love your feedback. Hit reply and tell me what's landing, what's still fuzzy, and what you want more of. I read every single one, and it genuinely shapes where this goes.

So here's today. Last time you taught Claude your recipe. This week we put that recipe on a timer, so it runs without you. Let me name the ache first, because it's the real one.

There's a tax nobody talks about, and it isn't the doing. It's the remembering to do. You're the one who remembers it's picture day. You're the one who remembers the field trip form, the oil change, the thing you meant to check every Monday and keep forgetting until Wednesday. Your brain is running twenty background tabs of "don't forget," and every one of them is quietly draining you before you've done a single actual thing.

That's the load. Not the task itself, but the holding of it.

I lived in that for years. I had a recipe I trusted, and I still had to remember to run it. So the recipe sat there, perfect and useless, waiting on me to remember it existed. I was the bottleneck in my own system.

Then one day it just showed up done. I didn't open anything. I didn't remember anything. It was sitting there waiting, like somebody had done it overnight, because somebody had.

Read that again. Up until now, every good thing we've built still needed you to be there, hand on the wheel, to make it happen. A schedule is where that stops. You set it once, and it happens on its own, on the rhythm you picked, whether or not you remember it exists.

Here's the whole idea in one line: last time you taught it the recipe, this week you set it and forget it.

Use case: Turning the recipe you built last time into a recurring version that shows up done, on the day and time you pick

Heads up on the setup: this one needs a paid plan, because that's where scheduling lives. You set it up either in the Claude desktop app or on the web, wherever you already work. If you're on the free version, skip down to the Beginner Move and do the free version this week. It builds the exact same habit.

Take the skill you wrote last week. Then say this:

That "run it once first" line is the whole safety net. You get to see exactly what will show up tomorrow morning before you commit to it showing up every morning. If it's off, you fix the recipe once, and every future run inherits the fix.

One honest note on where it lands. When the scheduled task runs, the finished thing is sitting there waiting for you inside Claude. You go open it and read it. It doesn't get texted or emailed to you. You come to it, and it's already done.

Here's the deeper idea, and it's the thing that turns a neat trick into a real change.

You already taught Claude a skill last week. A schedule is what you chain onto that skill so it runs itself. Recipe plus timer. That's it. The recipe is what to do, the schedule is when to do it, and once both exist, you're out of the loop entirely. The work happens, and you just show up for the result.

Now the part that surprised me, because it's better than most people expect. A scheduled task doesn't sit on your laptop waiting for you to have it open. It runs up in the cloud, on Anthropic's servers, on the rhythm you picked. That means it fires even when your computer is closed, asleep, or shut in a bag across the house. You genuinely set it once and walk away. At 7am your laptop is dark and the thing still gets written. That's the whole "forget it" half of set it and forget it, and it's real.

There are two ways to set it up, and neither one is hard. The lazy way is to just ask for it out loud: tell Claude "run this every weekday at 7am," in plain English, and it gets the whole thing scheduled for you. The deliberate way is to go set it yourself. Look in the sidebar for the scheduled or scheduling area, on the desktop app or over at claude.ai/code/scheduled on the web, where you create the task, name it, drop in your recipe, and pick how often it runs. Same result either way, so use whichever feels more natural to you. The cadence choices are plain English too: hourly, daily, weekdays, weekly, or on demand when you want it. Mine is weekdays, because the market doesn't open on Sunday and I don't need a briefing about nothing.

Free, no paid plan, no desktop app, no download. Here's the move: run a manual schedule for one week.

Pick a standing time you'll actually keep, whether that's every Monday at 9am or every night after the kids are down. Then set one plain phone reminder that says "run my Claude recipe," and point it at that time.

For one week, when the reminder buzzes, you open Claude the normal way, paste your saved recipe from last week, and run it. By hand. That's the whole thing.

Here's why this is genuinely worth doing and not just a consolation prize. You're building the rhythm before you build the automation. By Friday you'll know three things you can't know any other way: whether the timing is actually right, whether the recipe holds up run after run, and whether you even want this on a schedule at all. Most people automate something and then quietly resent it because they never checked if the rhythm fit their real life. You'll have checked.

Then, when you're ready to move to the desktop app and let it run on its own, you're not guessing. You're just handing off a rhythm you already proved. The manual week isn't the slow version. It's the smart version.

I'll go first, like always.

You've heard me mention my 7am market brief a few times now. This week I want to tell it through the one lens I've never put on it: the timer.

For a long stretch, the recipe was good and I was still the problem. I'd trained it exactly how I wanted, but I had to remember to sit down and run it, and mornings are chaos in my house and at work. Some days I ran it late. Some days I forgot until the afternoon, when the whole point of a morning brief was long gone. The brief was good, but my follow-through was not. I was the one thing standing between me and my own system.

So I set it once. I told it when to run, and I let go of the wheel. Every weekday morning it writes itself before I'm awake, and it's just sitting there in my inbox when I come get my coffee. (Yes, I’ve set it and have Claude send it via email). I don't remember anything.

Here's the part I keep coming back to, because it's the real gift and it isn't the one you'd guess. The win was never the time I saved. It's that I stopped spending my mornings gathering and started spending them thinking. The gathering was grunt work I was never good at and never enjoyed, and it used to eat the exact hour when my head was clearest. Now that hour is mine. The recipe handles the hunt. I get to do the part I'm actually here for.

That's the trade I want to hand you. Not "AI does my work." More like: the part that quietly drained you gets handed off, and you keep the part you love.

So here's your hand-off, and it's one thing.

Take the recipe you saved last time (or choose another one, whatever you want), pick the day and time it should run, and give it a rhythm this week. If you're on a paid plan, set it up to run on its own, in the desktop app or on the web, and check the first result. If you don't, do the free manual week: one phone reminder, one standing time, run it by hand, and feel the rhythm. Either way, you stop remembering the task and start receiving it.

Next week is the one I've been circling since the very beginning. Not what any of this does, because by now you've got a real feel for that. This time it's why I started writing this at all, and why I keep showing up in your inbox to hand you these. It's the most personal thing I'll write here, and it's the piece I've been quietly building toward.

After that, we can go almost anywhere: hiring a whole team of Claudes to split up a big job, building your own second brain, wherever you tell me you want to go. But first, the why.

Until then.

Stop overthinking it.

Just get started.

JGS

P.S. Hit reply and tell me the one recurring thing you'd put on a timer. The Monday plan, the Friday wrap-up, the weekly digest of the thing you love. I read every one, and the best of them tend to show up in a future issue.