litespeed/restore-preset-backup rolls the configuration back to a backup taken before a preset was applied.
It takes the timestamp reported by litespeed/list-preset-backups. An unknown timestamp is refused rather than silently doing nothing.
At a glance
| Ability | litespeed/restore-preset-backup |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Toolbox |
| Requires | LiteSpeed Cache, active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Not idempotent — each call changes the row set, so re-running is not a no-op |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
Rolling back replaces everything too
This replaces the current configuration wholesale with the backed-up one. Anything configured since that backup was taken — exclusions added while fixing what the preset broke, settings tuned since — is replaced along with everything else. Rolling back is not partial.
How it works
The refusal matters because the alternative is worse than an error. A restore given a timestamp it cannot find has nothing to apply, and a silent no-op looks exactly like a successful restore until somebody checks the settings.
That would be a bad thing to discover while recovering from a broken preset, which is precisely when this ability gets used.
The restore is wholesale, in both directions. It does not merge the backup with the current configuration, and it does not preserve changes made since — so work done fixing the problem is rolled back along with the problem.
Restoring does not purge. The cached pages and generated assets were built under the configuration you just replaced, so purge afterwards.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
timestamp | string | Yes | The backup timestamp, from litespeed/list-preset-backups. |
confirm | boolean | Yes — must be true | The irreversibility gate. Without it the call is refused before anything is touched. |
What comes back
| Name | Type | What it is |
|---|---|---|
restored | string | The backup that was restored. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Roll LiteSpeed back to how it was before the preset.
It resolves to one call:
{
"ability": "litespeed/restore-preset-backup",
"parameters": {
"timestamp": "2026-09-20_14-05-11",
"confirm": true
}
}Worth knowing
- An unknown timestamp is refused, not ignored.
- Everything configured since the backup is replaced too.
- Purge afterwards — cached output was built under the old configuration.
- Get the timestamp from the listing; do not guess the format.
Related abilities
- List Preset Backups — get a valid timestamp
- Apply A Configuration Preset — what you are rolling back
- Purge Cache — required after restoring
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category