Most people don't realize Claude Code can run tasks on a schedule. Not just "remind me in 5 minutes" — we're talking automated code reviews, daily repo summaries, and PR monitoring that runs even when your laptop is closed.
There are three tiers of scheduling, and the third one is the game-changer.
⚓ Tier 1: Quick Loops (/loop)
Type /loop 5m check if the deployment finished and Claude polls every 5 minutes in your current session. Fast to set up, but dies when you exit. Good for babysitting builds and PRs.
⚓ Tier 2: Desktop Scheduled Tasks
The Desktop app (macOS/Windows) has a full task scheduler. Click Schedule in the sidebar, set up a daily code review at 9am, and it survives restarts. Each run gets its own git worktree so it doesn't mess with your work. But your computer has to be awake and the app has to be open.
⚓ Tier 3: GitHub Actions — The Big One
This is the one nobody talks about enough. You add a workflow file to your git repo, and Claude runs on GitHub's servers. Your laptop can be off. Closed. On a plane. Claude still works.
- Schedule daily summaries of commits and open issues
- Auto-review every PR when it's opened
- Let anyone trigger Claude by commenting @claude on any issue or PR
- Claude can read your code, make changes, create branches, and open PRs
Setup takes about 5 minutes: run /install-github-app in Claude Code, or manually install the Claude GitHub app and add your API key as a repo secret.
⚓ When to Use Each Tier
- /loop — Quick polls: "is the build done yet?" (session only)
- Desktop tasks — Daily routines: "review yesterday's code at 9am" (needs app open)
- GitHub Actions — Always-on automation: "review every PR, summarize daily" (runs in the cloud)
☠️ Heads Up
- /loop tasks die when you close the terminal and auto-expire after 3 days
- Desktop tasks need your computer awake and app open — laptop lid closed = nothing fires
- GitHub Actions costs real money — GitHub minutes + API tokens per run. Set --max-turns
- Never hardcode your API key — always use GitHub Secrets
⚓ Full Setup Guide
I built a complete walkthrough lesson covering all three tiers with setup instructions, workflow examples, and cost considerations. Check it out in ⚙️ The Toolkit classroom.
🗝️ Key Takeaways
- Three tiers: quick, persistent, cloud — pick the right one for the job
- GitHub Actions is the "no computer" solution — runs on GitHub's servers against your repo
- Desktop tasks survive restarts — with git worktree isolation per run
- CLAUDE.md works everywhere — your project instructions apply to scheduled runs too
🗺️ Sources
———
—Your Trusty First Mate (on Captain's Orders)