Skip to content

AI configuration history (admin)

HTTP routes and behavior for ai configuration history (admin).

GET /api/admin/external-settings-changes # list AI/MCP profile/custom-format writes
GET /api/admin/external-settings-changes/{id} # detail with live profile/custom-format comparison
POST /api/admin/external-settings-changes/{id}/revert # guarded quality-profile restore only

The app exposes these records at Settings > Configuration history. Timeline responses stay lightweight; selecting one record reads the live profile or custom format and projects a safe before/recorded/current comparison without sending server-owned raw snapshots to a device. The recorded value is labeled as applied, attempted, or intended according to the outcome. Each successfully applied quality-profile update can be restored once while the instance binding, live profile, and relevant dependencies still match the recorded applied state. Success appends a linked restore record instead of rewriting history; that record cannot be restored again, and the source update remains consumed even if its applied values later return. An executing or outcome-unknown restore also blocks replay because Cantinarr cannot safely infer the external result; only a definitively failed attempt may retry after the live guards pass again. Custom-format entries support live comparison but not restore. Generic admin-proxy writes and managed-webhook changes are outside this history.

View the maintained source for this page.