litespeed/apply-preset replaces the whole LiteSpeed configuration with one of five shipped presets: essentials, basic, advanced, aggressive or extreme — weakest to strongest.
LiteSpeed takes an automatic backup first, which is what makes this recoverable and why it confirms rather than being marked destructive.
At a glance
| Ability | litespeed/apply-preset |
| 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 |
It replaces everything
This replaces the entire configuration, not part of it. Every exclusion somebody added after a script broke, every tuning decision, every setting adjusted over years — all of it is replaced by the preset’s values. LiteSpeed takes an automatic backup first and litespeed/restore-preset-backup rolls back to it, which is the only reason this is recoverable. Anything above advanced changes front-end rendering and must be tested immediately.
Choosing a level
The presets are cumulative in aggression. Essentials turns on caching and little else. Basic adds the safe optimisation. Advanced adds the combination and deferral settings that usually work. Aggressive and extreme add the ones that usually need exclusions.
Everything from advanced upward changes how the front end renders, which means the only sensible way to apply one is to look at the site immediately afterwards — the home page, a post, a form, anything with a slider, and the checkout if there is one.
The automatic backup is the safety net and it is worth confirming it exists before you need it. litespeed/list-preset-backups shows what you can roll back to, and reading it before applying rather than after is the difference between a quick recovery and a bad afternoon.
A preset is a starting point, not a destination. The exclusions a site needs are specific to its theme and plugins, and no preset can know them — so the normal sequence is apply, test, then add exclusions for whatever broke.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
preset | string | Yes | essentials, basic, advanced, aggressive or extreme. |
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 |
|---|---|---|
preset | string | The preset applied. |
backup | string | The timestamp of the automatic backup taken first. |
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:
Set LiteSpeed up with the recommended settings.
It resolves to one call:
{
"ability": "litespeed/apply-preset",
"parameters": {
"preset": "advanced",
"confirm": true
}
}Worth knowing
- Replaces the entire configuration, including every exclusion.
- Anything above
advancedchanges rendering. Test the front end straight away. - Note the backup timestamp in the response — it is your way back.
- Expect to add exclusions afterwards. No preset knows your theme.
Related abilities
- List Preset Backups — check your rollback points first
- Restore A Preset Backup — the way back
- Export Settings — take your own record first
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category