Paperclip's dashboard

Paperclip’s dashboard shows everything the jobs do. Open the Paperclip service’s address in Railway and sign in with the same email and password as CloudCLI.

Claude gives you direct links: every job, task and run the jobs script mentions comes with its page in the dashboard.

Where things are

The template names Paperclip’s company Jobs, so tasks are numbered JOB-1, JOB-2, and so on.

You want	Go to
An overview: the Runner’s latest task, run activity, success rate	Dashboard
Your jobs, their schedules, next and last runs	Routines
One job: its schedule, agent, prompt and recent runs; run it now; turn it on or off	Routines, then the job
A run’s result	The run’s task (JOB-n), under Tasks or from the job’s recent runs
Every run with its model, tokens, duration and transcript	Agents, Runner, Runs
The Runner’s model	Agents, Runner, its configuration
Keys and settings your jobs use	Agents, Runner, Harness / Runtime, Environment variables
Your repos	Projects: one project per repo
Outside services: apps and connections	Connectors (Paperclip’s apps). See Outside services.

Editing jobs in the dashboard

You can change a job in the dashboard: turn it off, edit its schedule, run it now. Claude records those changes in the repo’s .claude/jobs.json the next time it looks at your jobs. See Sync after dashboard edits.

Asking Claude is still the simpler way: it changes the job and records it in one step.

What to leave to the template

The template manages some of what you see in Paperclip, and rewrites it at every start:

• The Runner’s instructions. Edits are replaced at the next start. To change what a job does, change its skill.
• The company, the Runner and the projects for your repos. Add repos on CloudCLI’s /setup page, which gives each its project.

The rest is yours: your jobs, their schedules, the Runner’s model, secrets you add, and apps, connections and plugins. See What the template manages.