Paperclip Community Reports Backup Fallback Bug That May Drop Database Constraints on Restore

The self-hosted backup integrity of AI agent management platform Paperclip has come under scrutiny. On October 27, a user reported that an automatic backup appeared to complete, but the restored database was missing constraints. The problem surfaced only later, when a migration attempted to drop constraints that were already absent. The reporter used a slightly modified older canary build and said they had reviewed the v2026.1023.0 source code, confirming that the relevant code path was still present. Maintainers have not yet confirmed which versions are affected. Issue report

The reported trigger was embedded PostgreSQL 18.1 paired with pg_dump 16 on the host. After the native export failed because of the version mismatch, Paperclip’s automatic mode switched to its JavaScript backup engine without logging the reason for the fallback. PostgreSQL’s official documentation states that pg_dump cannot dump from a server with a newer major version than its own, so deployments need to check both the database and export-tool versions. PostgreSQL documentation

The reporter’s comparison found that none of the source database’s 66 CHECK constraints made it into the backup, some UNIQUE NULLS NOT DISTINCT constraints became ordinary UNIQUE constraints, and timestamps lost microsecond precision. This means a successful restore may still change data validation rules. The concern about inconsistent snapshots across tables is based on code analysis and has not been reproduced, so it should not be conflated with the differences that were observed. Report and verification method

For operators of agent platforms, the technical takeaway is that having a backup file and being able to load its SQL are not enough to prove that the control plane can be fully restored. The official documentation says pg_dump can create a consistent export while the database is in use; whether an alternative engine preserves the same semantics needs to be verified separately. Export consistency documentation

Engineering teams can start by confirming which backup engine is actually being used and comparing constraints and timestamp precision before and after a restore in an isolated environment. They should watch for maintainers to confirm the scope of affected versions and whether a fix will add both fallback warnings and restore validation. The issue cannot yet be considered fixed in an official release.