litespeed/get-environment-report returns LiteSpeed’s own environment report: server software, PHP configuration, the active plugins, and the conflicts it detects.
It is the first thing to read when caching behaves in a way the settings do not explain, and the thing to attach when asking LiteSpeed support for help.
At a glance
| Ability | litespeed/get-environment-report |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Toolbox |
| 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
A large part of LiteSpeed’s functionality requires the LiteSpeed web server or OpenLiteSpeed underneath. The plugin installs and configures perfectly happily on Apache or nginx, and a good deal of it simply does not work there — page caching most of all.
That produces the most confusing category of problem in this suite: every setting is correct, the plugin reports success, and nothing is cached. The server line in this report answers it immediately.
Plugin conflicts are the second category. Two caching plugins, or one caching plugin and an optimisation plugin, will each write their own rules and drop-ins and the result is not the sum of the two. LiteSpeed detects the common conflicts and names them here.
The PHP configuration matters for the parts that write files — generated assets, the object cache drop-in — where an open_basedir restriction or an unwritable directory produces silent fallbacks rather than errors.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
server | object | Server software and version. |
php | object | The relevant PHP configuration. |
plugins | array | Active plugins. |
conflicts | array | Conflicts LiteSpeed detects. |
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:
Nothing is being cached and the settings look right — why?
It resolves to one call:
{
"ability": "litespeed/get-environment-report",
"parameters": {}
}Worth knowing
- Page caching needs a LiteSpeed server. On Apache or nginx much of the plugin does nothing.
- Two caching plugins do not combine. They conflict.
- Attach this when asking LiteSpeed support for help.
Related abilities
- Get Cache Status — what the plugin thinks it is doing
- Export Settings — the configuration to go with it
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category