litespeed/get-cache-status reports whether LiteSpeed is caching, what it is caching for whom, the configured TTLs, whether the object cache and browser cache are on, and whether a QUIC.cloud key is present.
Run it before changing anything, and again afterwards to confirm the change took.
At a glance
| Ability | litespeed/get-cache-status |
| 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
This is the orientation call for the whole suite. Cache problems are almost always a mismatch between what somebody believes is configured and what is, and a single call that states the actual position resolves most of them before any change is made.
Running it again afterwards matters just as much. Several LiteSpeed settings are written successfully and then not applied — because the server does not support the feature, because a constant in wp-config.php overrides the option, because another plugin filters it. Reading back is how you find out.
The QUIC.cloud key is reported as present or absent and never used. QUIC.cloud is LiteSpeed’s paid optimisation service, and spending somebody’s credits is not a thing an assistant should do as a side effect of a request — so no ability in this suite calls it.
Object and browser caching are included because they are separate systems that people reasonably assume are part of “is the cache on”.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
caching | object | Whether caching is on, and for whom. |
ttls | object | The configured TTLs. |
object_cache | object | Whether the object cache is on. |
browser_cache | object | Whether browser caching is on. |
quic_cloud_key_present | boolean | Whether a QUIC.cloud key is configured. Reported only; never used. |
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:
Is LiteSpeed actually caching this site?
It resolves to one call:
{
"ability": "litespeed/get-cache-status",
"parameters": {}
}Worth knowing
- Run before and after any change. Settings can be written and not applied.
- The QUIC.cloud key is reported, never used. No ability here spends credits.
- Object and browser caching are separate systems from the page cache.
Related abilities
- Get Cache Settings — the full configuration
- Get Environment Report — when the answer makes no sense
- Turn Caching On Or Off — the master switch
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category