Claude Code can run prompts on a schedule while you keep working. Use /loop to poll builds, watch PRs, monitor deploys, or set reminders.
Basic Usage
/loop 5m check if the deployment finished and tell me what happenedClaude sets up a recurring task that fires every 5 minutes in the background. You keep working normally, and Claude runs the check between your turns.
Interval Syntax
/loop 30m check the build # every 30 minutes
/loop check the build every 2h # trailing interval works too
/loop check the build # no interval = every 10 minutesSupported units: s (seconds), m (minutes), h (hours), d (days). Seconds get rounded up to the nearest minute.
Loop Over Other Commands
You can schedule any slash command or skill to run on repeat:
/loop 20m /review-pr 1234Every 20 minutes, Claude runs your PR review command as if you typed it.
One-Time Reminders
Skip /loop and just ask in plain English:
remind me at 3pm to push the release branchin 45 minutes, check whether the integration tests passedClaude schedules a single-fire task that deletes itself after running.
Managing Tasks
what scheduled tasks do I have? # list all
cancel the deploy check job # cancel by descriptionYou can have up to 50 scheduled tasks per session.
Good Use Cases
- Deploy monitoring:
/loop 5m check if the deploy to production succeeded - PR babysitting:
/loop 15m check PR #42 for new review comments - CI watching:
/loop 10m are the CI checks passing on main? - Build polling:
in 20 minutes, check if the build finished - Self-reminders:
remind me at 4pm to commit my work before the meeting
Limitations
- Session-scoped: tasks die when you close the terminal
- No catch-up: if Claude is busy when a task is due, it fires once when free
- 3-day expiry: recurring tasks auto-delete after 3 days
- Idle only: tasks fire between your turns, not mid-response
For scheduling that survives restarts, use GitHub Actions with a schedule trigger instead.