Pharmacist moves Claude Code daily tasks to Windows Task Scheduler
A pharmacist and non-expert programmer has detailed a workflow for automating daily social media posts using Claude Code. Initially, the user relied on Claude Code's built-in recurring task feature to draft and post content to Threads. However, they discovered that the task only executed while the Claude desktop application remained open, causing missed posts when the app was closed.
What you can do with it
AI at Work →Schedule daily posts with Windows Task Scheduler and Claude Code
What you get You get reliable daily posting that works even when the AI app is closed.
Runs fixed-format posts via script, using AI only for setup and backup.
- Who for
- marketers and founders
- Cost
- Price not stated
- Effort
- an afternoon
Use it for
- Draft daily social posts
- Automate content scheduling
How to set it up · From the article
- Create a Node.js script for fixed-format posts
- Register the script in Windows Task Scheduler
- Keep Claude Code recurring task as a backup
Watch out Requires manual approval for resident automation and basic scripting knowledge
Claude Code in the tool directory · 8 changes covered
Key points from the news
- Claude Code recurring tasks only run while the desktop app is open, causing missed executions.
- User moved daily post generation to a Node.js script in Windows Task Scheduler for reliability.
- Eight design rules were established to ensure deterministic, safe, and limited automated posting.
To resolve this, the user migrated the execution logic to a standard Node.js script registered in the Windows Task Scheduler. This script runs at 7:13 PM daily, using pre-defined rules and fixed formats to generate posts without real-time AI decision-making. The AI is now used only for initial setup and as a backup mechanism. The author emphasizes that this approach ensures reliability by decoupling the automation from the AI application's state.
The article outlines eight design decisions, including setting upper limits on post counts, defining deterministic selection methods, and requiring human approval for any resident automation. The author notes that AI safety checks initially blocked the registration of the automatic posting script, requiring explicit user confirmation. This case study highlights a practical pattern for using AI for setup and a traditional scheduler for reliable, low-cost daily execution.
The story so far
2 episodes →- Pharmacist moves Claude Code daily tasks to Windows Task Schedulerthis story
Moving Claude Code's recurring tasks to the Windows Task Scheduler: 8 decisions made to run daily with a non-AI script
note.com · 31 October 2026
Loading the full article…
This text was published by note.com and written by RYU＠”独り薬剤師”の戯言. It is reproduced here with attribution so you can read it in full; the rights remain with the publisher. Read it at the source ↗
The headline, key points and digest above were generated by Digest AI's editorial model from the linked sources. Automated summaries can contain errors: the sources are the record. Spotted a mistake? Tell us. Published by Martin K., who runs Digest AI and handles corrections.
More in Agents & Tools
All →- Y Combinator and Olam Labs test 50-agent GPT-6.1 Sol swarm in Minecraft civilization experiment · 1 src
- Microsoft tests Context Vault, a new AI memory for Windows · 1 src
- Karpathy ships HackerTube in ~2 hours with Claude Opus 5.5 · 1 src
- DeepSeek Harness team releases open-source Super-agent prototype · 4 src
- Developer uses GLM-5.3-Flash and GPT-6.1 Sol for coding · 1 src
Comments
via GitHub Discussions