Change, pause or archive a job

Ask Claude in CloudCLI. Each change is made in Paperclip, then recorded in the repo’s .claude/jobs.json as a commit.

You ask	Claude runs	The commit says
“Move the digest to 9:00.”	update "<job>" --cron "0 9 * * 1-5"	Job "Weekday open issues digest" changed: schedule 0 9 * * 1-5 America/Toronto
“Rename it to Morning digest.”	update "<job>" --title "Morning digest"	Job "Morning digest" changed: renamed from "Weekday open issues digest"
“Pause the digest.”	pause "<job>"	Job "Morning digest" paused
“Resume it.”	resume "<job>"	Job "Morning digest" active
“Archive the digest.”	archive "<job>"	Job "Morning digest" archived
“Run it now.”	run "<job>"	No commit: a run doesn’t change the job.

Jobs are named by their title, in any case, or by the start of their ID. “The digest” works when only one job’s title contains “digest”.

Change what a job does

What a job does is its skill, not the job. Ask Claude to change the instructions: “the digest should also list pull requests”. Claude edits .claude/skills/<name>/SKILL.md, commits and pushes it, then tests the job.

You can also edit the skill yourself, anywhere, and push. The Runner pulls before every run, so the next run uses what is pushed.

Pause and resume

A paused job doesn’t run on its schedule until you resume it. It keeps its schedule and its history.

In Paperclip, the job’s on/off switch turns it off too. Claude records that change in git the next time it looks at your jobs; see Sync after dashboard edits.

Archive

Archiving takes a job out of Paperclip’s list of jobs and out of .claude/jobs.json. It no longer runs. The repo’s git history keeps it.

To bring an archived job back, ask Claude to create it again. The old entry in git history has its title, prompt and schedule.

Move a job to another repo

Ask Claude: “move the digest to the acme/website repo”. It moves the job to that repo’s project (update "<job>" --repo acme/website) and records the move in both repos: one commit removes it from the old record, one adds it to the new.

Move the job’s skill too: the job now runs on the other repo, and looks for its skill there.

Hand a job to Codex

With Codex connected, ask “run the digest with Codex”. Claude runs update "<job>" --agent Codex. “Run it with Claude again” moves it back to the Runner. See Codex.

When the record wasn’t pushed

Claude passes on the script’s “Recorded in” line after each change. If it says “not committed” or “not pushed”, Claude fixes it, usually with a pull, and pushes. If the clone is on another branch than the default one, the line says so: merge that branch to keep the record on the default branch.