Sync after dashboard edits

You can change jobs in Paperclip’s dashboard: turn one off, edit its schedule. Those changes are made in Paperclip only. sync writes them into each repo’s .claude/jobs.json, so git stays the full record.

Claude does it for you

Before changing jobs, and whenever you mention a change you made in Paperclip, Claude lists your jobs. When the list says some jobs are “not recorded as they are now”, Claude runs sync right away and tells you.

So in practice you only need to tell Claude: “I paused the digest in Paperclip.” Or ask “which jobs do I have?” and Claude notices.

What list reports

At the end of the job list, the jobs script says where a repo’s record and Paperclip disagree:

Not recorded as they are now in acme/website's .claude/jobs.json: "Weekday open issues digest". Record them with: sync

acme/website's .claude/jobs.json lists jobs Paperclip doesn't have: "Daily uptime check" (0 7 * * * America/Toronto, active, needs STATUS_WEBHOOK_URL). Recreate them with: restore

The first is a dashboard edit, or a job made before the record existed: sync records it. The second is a new server, or a repo used on another server: see Restore on a new server.

What sync does

For each connected repo, sync:

• writes every active and paused job as it is in Paperclip;
• removes jobs that were archived in Paperclip;
• keeps jobs that Paperclip doesn’t have at all, so a new server can still restore them;
• keeps each job’s secret names;
• commits and pushes the file, with the message “Jobs recorded as they are in Paperclip”.

Recorded in acme/website's .claude/jobs.json: commit 1a2b3c4, pushed.

When a repo’s record lists jobs Paperclip doesn’t have, sync says so, and how to restore them or remove them from the file.

Ask for it

Record my jobs.

Claude runs sync. sync --repo acme/website limits it to one repo.