Apyrn Tools
All tools

Claude Code schedule and loop command generator

A scheduled Claude Code task runs a prompt against a repository on a cron cadence, while a loop repeats a task during an active session.

Generate Claude Code schedule and loop commands from templates and plain-language frequencies, with optional GitHub Actions YAML. Runs in your browser.

Browser-sideNo accountCopy, download, or print

Last reviewed

Your inputs are saved as a draft in this browser only. Nothing is uploaded.

Jump to result
Interactive workspace

Inputs

Result

More export options
Command typeschedule
TemplateprReview
Frequencydaily 9am
Cron expression0 9 * * *

Confirm the cron expression in your scheduler's timezone.

Command:
/schedule daily 9am "Review all open pull requests"

Derived cron (daily 9am):
0 9 * * *

GitHub Actions workflow:

name: Claude Code Automated Task
on:
  schedule:
    - cron: '0 9 * * *'
  workflow_dispatch:

jobs:
  claude-task:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0
      - name: Run Claude Code
        uses: anthropics/claude-code-action@v1
        with:
          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
          task: "Review all open pull requests"
          allowed_tools: "read_file,write_file,bash"

How to use it

  1. Choose the command type: schedule a persistent task or loop during active work.
  2. Pick a template and write the frequency in plain language, such as daily 9am.
  3. Describe the task instructions and set the repository, branch, and allowed tools.
  4. Generate the command, check the derived cron expression, and copy the GitHub Actions YAML if you included it.

Questions

What is the difference between schedule and loop?
Schedule creates a persistent task that runs on the derived cron cadence, while loop repeats only during an active Claude session. The GitHub Actions workflow is a scheduled fallback for tasks that must run unattended.
How is the cron expression derived from the frequency?
The plain-language frequency, such as daily 9am, every 15 minutes, or weekly monday, is parsed into a cron expression. Confirm the result in your scheduler's timezone before relying on it.
Is my task description sent anywhere?
No. The command and workflow YAML are generated entirely in your browser and nothing is uploaded.
Which timezone does the GitHub Actions schedule use?
UTC. GitHub Actions cron schedules always run in UTC, so 0 9 * * * runs at 09:00 UTC, which is 14:30 in India. Scheduled workflows can also start a few minutes late when GitHub is busy.