Updates

Both app services build from the template’s public repo, mikedepo/paperclip-cloudcli. When AvgSoft changes it, Railway shows an Update available button on your project’s canvas.

• Updates are opt-in. Nothing changes in your deployment until you apply one, and you can skip any.
• Read the changelog first. Each entry says what changed and anything you need to do.
• Your data is kept. An update replaces the services’ code only.

Apply an update

From the canvas

1. Open your project in Railway. Press Update available.

2. Press Yes (“Do you want to update Paperclip to its latest version?”).

3. It updates one service at a time. Press Update available again for the other one: Paperclip first, then CloudCLI.

From a service's settings

1. Open the service (Paperclip, then CloudCLI), then its Settings.

2. Under Source, find Upstream Repo and press Check for updates.

3. Press Update.

Each service rebuilds and restarts, which takes a few minutes. Jobs that were due during the restart are skipped, not replayed.

Screenshot to comeThe Update available button on the project's canvasRailway's canvas with the Update available button, and the Yes prompt.

What an update changes, and what it doesn’t

Changed	Kept
The template’s code: the start scripts, the setup page, the jobs skill and script, the Runner’s instructions	Everything on the volumes: Paperclip’s data, CloudCLI’s home folder with your sign-ins, chats and repo clones
	The database: your jobs and runs
	Your variables and service settings
	Your repos, skills, records and memory, in git

Variables and settings only change for new deploys. When an update needs one changed, its changelog entry says so.

Which version you have

Each service’s deploy log starts with the commit it runs, and the changelog’s address:

[paperclip-cloudcli] Paperclip service, code 2d84847
[paperclip-cloudcli] What changed: https://github.com/mikedepo/paperclip-cloudcli/blob/main/CHANGELOG.md

Match the commit with the repo’s history to see which changelog entries you have.

The tools CloudCLI installs

CloudCLI, Claude Code, Codex and the GitHub CLI are installed into CloudCLI’s volume at the first start. They keep their own update paths:

• CloudCLI has its own Update button. A newer CloudCLI you installed is kept.
• Claude Code and Codex update themselves.

Paperclip’s version is pinned in the template, and moves with template updates.

Eject

Railway’s Eject, in the same settings section, copies the template’s repo into your GitHub account so you can change the code yourself. The license allows this for your own deployment. Updates then reach your copy as a branch for you to merge. This hasn’t been tested.