Claude on a schedule, with every job in git

Why this template

Quick to start

One click to deploy, an email and a password on the form. A setup page connects Claude, GitHub, your repos and your time zone, with no redeploy.

Jobs you keep

Each job’s instructions are a skill in your GitHub repo, and .claude/jobs.json records its schedule. Git keeps every job and every change, and a new server restores them.

Every run on record

Paperclip keeps each run’s status, result, full transcript, model and tokens. Only scheduled jobs run, one task per run.

Updates you choose

Fixes arrive as Railway update notices, with a changelog. Nothing changes until you apply one, and your data is kept.

From deploy to your first job

1. Deploy. Press Deploy on Railway, type your email and a password, and deploy. The first start takes a few minutes.

2. Connect your accounts. Open the CloudCLI service’s address. Its setup page signs Claude in with Claude Code’s own sign-in, connects GitHub with a one-time code, clones your repo and saves your time zone.

3. Ask for a job. In CloudCLI’s chat, say what should happen and when: “Every weekday at 8:00, list the open issues in my repo with a one-line summary each.” Claude writes the job’s skill in your repo, schedules it in Paperclip, records it in .claude/jobs.json and tests it once.

4. Follow it in Paperclip. Open the Paperclip service’s address, with the same login. Each job shows its schedule and next run, and each run its result, transcript and tokens.

Read on

What it isWhat you get, and how it differs from setting up Paperclip yourself.

Getting startedThe 18-step quickstart, with screenshots, from deploy to your first job.

Jobs in gitSkills, the jobs record, sync and restore.

TroubleshootingA blocked job, a missing login, a job that doesn't run.