The Claude -pocaylpse or: How I Learned to Stop Worrying and Love Scheduled Tasks

The Automated Operator

SubscribeSign in

The Claude -pocaylpse or: How I Learned to Stop Worrying and Love Scheduled Tasks<br>What do you mean my projects can't use millions of Opus tokens via a headless Claude Code session and not pay for them?!

Alex Willen<br>May 21, 2026

Share

If you use Claude Code, you probably received this email recently:

If you’re unfamiliar, claude -p is used to run a headless Claude Code session. Basically, if you have an application that needs to have Claude Code do something, it can silently fire up a session, send it a command and use the output. This is useful if you want to have Claude reason over something as part of a programmatic process, but you are cheap and don’t want to pay to use the API.<br>I make frequent use of claude -p in daily tasks, like running updated inventory projections for my cashflow dashboard, so this is something of a bummer.<br>A quick aside on communicating with one’s customers: this email is extremely bad. It claims that they’re implementing the change because the rules weren’t clear. But if the problem is a lack of clarity, the right solution would be to, y’know, clarify, not create a new usage policy that drastically reduces the value of the subscription. I’m pretty sympathetic to the labs’ challenges with soaring usage against a limited supply of compute, so if this email said, “Hey, we’re sorry but this feature we implemented has kinda blown up in our face, so we need to start charging for it at API rates,” I would understand! But please don’t treat me like I’m a moron. Also, why are you making me click a link in an email that’s coming later to get my credit? Just put the link in this email! Or don’t require me to click a link at all!<br>Anyway, I asked Claude what it would cost me per month if I leave everything in its current state. Answer:

Oh okay cool just a casual increase from $100/month to $3,000/month. No biggie.<br>So, how do we get costs back down to sub-$100, so they’re covered by my subscription, ideally without losing functionality?<br>The first fix is easy. I actually forgot the amazon_ads judge thing was still running (old experiment, oops), so I’ll just go ahead and turn that off.<br>Beyond that, I have two daily processes and then my family assistant, which my wife and I use to add things to our collective calendars and store memories via a dedicated Gmail account and a Telegram bot.<br>Moving From Claude -p to Desktop Scheduled Tasks

The daily processes fire via GitHub runners, which then invoke claude -p. The good news there is that I only use that setup because I started creating these sorts of recurring jobs before Claude had scheduled tasks. While the update isn’t 100% clear, it looks like if I install Claude Desktop and set them up to run daily from there, that’ll still use my subscription. Let’s start with my inventory projection skill, which runs once per week for each brand (the actual skill runs daily but only does 1-2 brands each time). It gathers sales and inventory data from Amazon, then follows a process to project my sales by month for the next 18 months. Those projections flow into my cashflow dashboard, so I know when I’ll need to place future orders and how much money will be required.<br>Skills aren’t automatically shared between Claude Code and Claude Desktop, so there is a bit of work to do here. The skill.md file needs to be copied from its project directory into Cowork’s skill directory. In doing this, I learned that Claude will mislead you about what directory this is — it told me it was \.claude\skills but then couldn’t find the skill directory or file in there. The best solution here is just to explain what you need to Claude Code, tell it to search the internet for relevant context and find the appropriate directory on your machine, then copy the skill over. (I would point you to the right place, but I’m on a PC and odds are good you’re on a Mac, so just let CC handle it.)<br>Once you’ve got the skill in the right place, open Claude Desktop, go to Cowork → Scheduled, click New Task, then select Set up manually. (I should note that Claude tells me Cowork scheduled tasks and Claude Code Desktop local routines are exactly the same thing, in case you’re wondering why I didn’t go with the latter.)

Enter a name and description. For instructions, since everything it needs is already in the skill, just tell it to run . If the skill needs to access any files on your hard drive, point it to the folder where those live. Set it to act without asking. Choose the schedule on which you want it to run. Once it’s all configured, click Save.

Once that’s done, click on your newly-created task, then click Run now. That’ll create a new entry in the History section — click on that to watch the skill execute.

If everything is set up correctly and Claude can access the skill, it should go off without a hitch. If it runs into any problems, it’ll let you know.<br>Here’s...