Runs on your own Claude plan — no token markup

Cron for Claude Code.

Schedule claude -p jobs that run on your machine, on your Claude plan. We handle the cron, retries, history and alerts.

Start free Read the docs

Free forever for hobby use · No credit card · Cancel anytime

your terminal
$ curl -fsSL https://cronforclaude.com/install.sh | sh
$ cronforclaude add my-mac --token=csr_live_…
✓ runner online — next run in 4h 12m
cronforclaude · dashboard
Schedules
17
Online runners
2/2
Jobs · 24h
284
+12%
Recent jobs
iterateFindEatsucceeded
iterateLawHerosucceeded
ideate-saasansicoderunning
iterateatvrefqueued
How it works

Three steps. Done.

  1. 1

    Add a runner

    Click Create runner, then paste the one-line install on any Mac or Linux box with the Claude CLI logged in.

  2. 2

    Write a schedule

    Pick a cron expression — we preview the next fires — and a prompt. Tags, retries and alerts are optional.

  3. 3

    Watch it run

    Live activity timeline, stdout / stderr, exit code and token cost. Replay anything that failed.

Why Cron for Claude

Orchestrate the Claude CLI you already pay for.

Use your own Claude plan

The runner calls claude -p with the Claude login already on the box — no second subscription, no per-job markup.

Your machine, your files

Jobs run where your code already lives. Working directories stay local; secrets never touch our servers.

Production scheduling

Cron and one-shot triggers, skip-if-running, retries with backoff, crash recovery, optional --resume.

Cron you can trust

Per-schedule timezone, validated expressions, a live next-fire preview, and full run history.

Alerts, not spam

Telegram pings on failure, success, or always — set per schedule, overridable per project.

Built for teams

Multiple orgs with roles, API keys for CI, and an audit log on every change.

Vs. running cron yourself

crontab + ssh works. Until it doesn't.

crontab on your Mac
  • ×Fires while the laptop sleeps — silently lost.
  • ×No history. Did Tuesday's run even succeed?
  • ×One bad flag stalls forever on a permission prompt.
  • ×SSH into three machines to see what ran where.
  • ×No retries, no backoff, no alerts.
  • ×Pause one job? Edit a text file in vi.
cronforclaude
  • Server-side cron — the runner picks jobs up when next online.
  • Every run kept: prompt, stdout, stderr, tokens, cost.
  • Unattended-safe permission handling on by default.
  • One dashboard across every machine you own.
  • Retries with backoff; a Telegram ping when something breaks.
  • Toggle, re-cron or edit a schedule in one click — no SSH.

Free to start. Honest pricing.

The free tier covers hobby use. Paid plans scale schedules, runners and history — nothing else.

See plans Start free
  • No credit card
  • Cancel anytime
  • Your runner · your keys
  • Stop billing in 1 click