Several repos

You can connect as many repos as you need. Each one gets its own project in Paperclip and its own jobs.

Add a repo

1. Open /setup on CloudCLI’s address.
2. In step 3. Your repo, choose or type the repo, and press Use this repo.

The repo is added; the ones already there stay. It shows as a pill in the step’s title, and as a project in CloudCLI’s sidebar.

One project per repo

	Where
The repo’s clone in CloudCLI	~/<name>, in CloudCLI’s home folder
The repo’s project in Paperclip	Named after the repo
Paperclip’s own checkout of it	Made at the project’s first job
Its jobs’ skills	.claude/skills/ in that repo
Its jobs record	.claude/jobs.json in that repo

The first repo takes the project Paperclip starts with, renamed after the repo. Each later repo gets a new project.

A job runs on a checkout of its own repo only, so its skill must be in that repo.

A job belongs to the repo of the chat

To make a job for a repo, open a chat in that repo’s project in CloudCLI and ask there. Claude writes the skill in that repo, and the job goes in that repo’s project.

Asked from somewhere else, such as the home folder, a repo that isn’t connected, or a chat where it isn’t clear, Claude asks which repo the job is for.

See which repo a job runs on

Ask Claude “which jobs do I have?”. The list names each job’s repo:

e8b29a5f  Weekday open issues digest  [active]  repo: acme/website  0 8 * * 1-5 America/Toronto  next: 2026-11-04 08:00 America/Toronto  last: 2026-11-03 22:45 America/Toronto completed

In Paperclip, a job’s project is its repo.

Move a job to another repo

Ask Claude: “move the digest to acme/docs”. It moves the job to that repo’s project and records the move in both repos’ .claude/jobs.json. Move the job’s skill too, since the job now looks for it in the other repo.

Two repos with the same name

A fork and its original, such as me/app and org/app, can both be connected. The second is cloned into ~/<owner>-<name>, and its Paperclip project is named owner/name.

Remove a repo

The setup page has no button for it. By hand (not tested on this template yet):

1. Stop the repo’s jobs: ask Claude to archive them, or archive the repo’s project in Paperclip.
2. Delete the repo’s folder in CloudCLI’s terminal, and remove its project from CloudCLI’s sidebar. While the folder is there, the template adds it back to the sidebar at the next start.

Who can see what

All your repos’ jobs run as the same Runner agent, with the same secrets. A job’s run only checks out its own repo, but a secret on the Runner can be read by every job. See Secrets.