Rollback and checkpoints
A checkpoint saves the project’s whole file tree. From the Deploys & history section you switch the app back to an earlier build in seconds, or restore a checkpoint and deploy it.
A rollback changes code only. The data in the database stays as it is.
Checkpoints
There are two kinds:
- Named checkpoints. Click Create checkpoint in the Deploys & history section and type a label, or ask your agent: “Create a checkpoint ‘Approval flow done’ before you go on.” The agent calls the
checkpointtool. A project keeps up to 100 named checkpoints and none is deleted automatically; once full, manh.run refuses new ones. - Automatic copies. manh.run saves one before every write that changes or removes an existing file, before a feature block is added and before a checkpoint is restored. Automatic copies rotate among themselves; the newest 10 are kept.
Thanks to automatic copies, every file write by the agent can be undone. Before a big change, still create a named checkpoint so it is easy to find later.
The Deploys & history section
The Deploys & history section of the project sidebar lists every deploy and every checkpoint by day. Click a deploy row to open its detail page: status, the steps it ran, the deploy notes and the files changed since the previous successful deploy.
Three ways back to an earlier version:
- Instant rollback (on a successful deploy): switches the app to that build at once, without building again. manh.run keeps the 5 most recent builds. After that, Undo rollback puts back the version that was running.
- Roll back & deploy (on a checkpoint, or for a build older than the newest 5): restores the file tree to that checkpoint, then deploys.
- Restore files: restores only the file tree. The running app stays the same until the next Deploy.
Both rollback buttons need a 3-second press and hold, so you don’t trigger them by accident. Instant rollback leaves the draft files alone, so the agent keeps working on the version in progress.
Roll back through the agent
Ask your agent: “Take the app back to the checkpoint ‘Approval flow done’ and deploy it.” The agent does two steps:
restore_checkpointputs that file tree back. The running app hasn’t changed yet.deployships it.
A file tree that deployed successfully before skips check, so step 2 is never blocked by check rules added later.
What a rollback does not bring back
A rollback takes code and UI from the old version. These always come from the current settings:
- Secrets: a secret you changed or deleted does not come back with the old version.
- The custom domain: the app keeps running at its current address.
- Database data: tables and rows stay as they are. Columns the newer version added are still there.
manh.run does not back up databases. Before deploying a change that touches data, export the important tables to CSV from the Database section.
Next steps
- Logs and traffic — see how the new version behaves before deciding to roll back.
- Checkpoint tools — the
checkpointandrestore_checkpointtools agents use.