litespeed/get-purge-settings reads the automatic purge rules: which events purge what, whether stale content is served while a page rebuilds, and the scheduled daily purge.
These rules, not the TTLs, are what actually keeps a WordPress site fresh.
At a glance
| Ability | litespeed/get-purge-settings |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Purging |
| Requires | LiteSpeed Cache, active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
Publishing a post should purge the post, the front page, the archives it appears on and the feed. Which of those actually happens is configurable, and a site with the rules narrowed — often during a performance exercise years earlier — has edits that appear on the post and not on the front page.
That symptom is baffling from the front end and obvious here.
The serve-stale setting is the other thing worth reading. With it on, a visitor arriving while a page rebuilds gets the old version immediately rather than waiting; with it off they wait. On a slow page under load that difference is large.
The scheduled daily purge is configured separately and reported here so the whole purge picture is in one place.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
settings | array | One row per setting: its key, its current value, its type, and whether this suite can write it. |
count | integer | How many settings the area holds. |
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:
Why do post edits not show on the front page?
It resolves to one call:
{
"ability": "litespeed/get-purge-settings",
"parameters": {}
}Worth knowing
- Purge rules matter more than TTLs for freshness on a WordPress site.
- Narrowed rules are a common cause of “the edit shows here but not there”.
- Serve-stale trades a slightly old page for a much faster one under load.
Related abilities
- Update Purge Settings — change the rules
- Update Scheduled Purge — the daily schedule
- Update Cache TTLs — the backstop, not the mechanism
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category