litespeed/get-optimization-status reports what the optimisation pipeline has actually produced: whether minify, combine and defer are active for CSS and JS, and whether the generated assets exist on disk.
Configured and working are different things, and this is the call that tells them apart.
At a glance
| Ability | litespeed/get-optimization-status |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › CSS, JS & HTML |
| 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
LiteSpeed generates combined and minified assets lazily, on the first request that needs them, and writes them to disk. So there is a window — after enabling the feature, after a purge, after a deployment that wiped the directory — where the settings say combine and no combined file exists.
During that window the site serves the original assets and looks exactly like a site with optimisation switched off. Reading the settings tells you nothing; reading the disk tells you everything.
The more persistent version of the same problem is a directory the web server cannot write to. LiteSpeed does not fail loudly for that — it falls back to serving the originals, quietly, forever.
So this is the call after enabling optimisation and the call when optimisation appears to have no effect. If assets exist on disk, the pipeline is working; if they do not, the question is why.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
css | object | Whether minify, combine and defer are active for CSS. |
js | object | The same for JS. |
generated_assets | object | Whether generated files exist on disk, and how many. |
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:
I turned on CSS combining but nothing changed — is it working?
It resolves to one call:
{
"ability": "litespeed/get-optimization-status",
"parameters": {}
}Worth knowing
- Assets are generated lazily. Empty right after enabling is normal; empty a day later is not.
- An unwritable directory makes LiteSpeed fall back silently.
- This reads the disk; the settings read reads the configuration.
Related abilities
- Get Optimisation Settings — what is configured
- Purge Generated CSS And JS — force a regeneration
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category