litespeed/get-cache-settings returns every page-cache setting at once: the master switch, ESI, what is cached for whom, all the TTLs, the six exclusion lists, the vary rules and guest mode.
It is the orientation call. Read it before tuning anything.
At a glance
| Ability | litespeed/get-cache-settings |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Page Cache |
| 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
Every settings read in this suite returns the same shape — key, current value, type, and whether the key is writable — and every settings write takes the same shape back: a map of key to value, applied as a patch. Keys are owned by exactly one area, and litespeed/list-settings-areas is the map of which area owns what.
Reading everything in one call matters here more than it usually would, because LiteSpeed’s cache behaviour is emergent. No single setting tells you what the cache is doing — the master switch says caching is on, the scope says it covers logged-in users, an exclusion list says a URI is skipped, and a vary rule says a cookie splits the copy. The behaviour is all four together.
The writable flag on each row is the other reason to start here. Not every setting LiteSpeed holds can be written through this suite, and knowing which before you plan a change saves discovering it halfway.
This is a read of configuration. For what the cache is currently doing — whether it is serving, what is warm — litespeed/get-cache-status is the call.
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:
How is LiteSpeed caching configured on this site?
It resolves to one call:
{
"ability": "litespeed/get-cache-settings",
"parameters": {}
}Worth knowing
- Configuration, not behaviour.
litespeed/get-cache-statusis the behavioural read. - The
writableflag tells you what this suite can change. - Cache behaviour is the sum of the switch, the scope, the exclusions and the vary rules.
Related abilities
- Get Cache Status — what the cache is actually doing
- List Settings Areas — which ability writes which key
- Update Cache Settings — change the general settings
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category