litespeed/update-purge-settings changes which events automatically purge the cache, and whether stale content is served while a page rebuilds.
Turning auto-purge off means edits do not appear until something purges manually. That is occasionally what somebody wants and usually not.
At a glance
| Ability | litespeed/update-purge-settings |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Purging |
| Requires | LiteSpeed Cache, active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
The rules are a trade between freshness and rebuild cost. Purging the whole site on every post publish keeps everything current and, on a site that publishes often, means the cache is never warm. Purging only the post keeps the cache warm and leaves the archives stale.
Most sites want something in between, and the right answer depends on how often the site publishes and how much of the front page is derived from recent posts.
Serve-stale is close to free and usually worth having on. The visitor who triggers a rebuild gets the old page instantly instead of waiting for PHP, and the next visitor gets the new one.
After narrowing the rules, check that edits still appear where they should. The failure is silent and slow — content that is correct in the admin and old on one particular page.
The write is a patch, not a replacement. Send one key and one key changes; everything else in the area is left alone. The response names the keys that actually moved, so a payload that matched the existing values comes back with an empty list rather than a misleading success.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
settings | object | Yes | A map of setting key to new value. Keys outside this area are refused, and the refusal lists what the area accepts. |
What comes back
| Name | Type | What it is |
|---|---|---|
updated | array | The keys that actually changed. An empty array means every value you sent was already set. |
settings | array | Every setting in the area after the write, in the read shape. |
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:
Serve stale pages while they rebuild.
It resolves to one call:
{
"ability": "litespeed/update-purge-settings",
"parameters": {
"settings": { "purge-stale": true }
}
}Worth knowing
- Auto-purge off means edits need a manual purge to appear.
- Serve-stale is usually worth having on.
- Check that edits still appear after narrowing the rules.
- A patch — unsent keys are untouched.
Related abilities
- Get Purge Settings — read the current rules
- Purge Posts — the manual purge you will need
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category