litespeed/get-object-cache-status reports whether the object cache is enabled, which backend it targets, its host and port, and whether LiteSpeed’s drop-in file is actually installed.
Configured and working are different things, and the drop-in is where they part company.
At a glance
| Ability | litespeed/get-object-cache-status |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Object & Browser 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
WordPress uses an object cache only if a file called object-cache.php exists in the content directory. LiteSpeed writes one when you enable the feature — unless the directory is not writable, or another caching plugin already put its own there, or a deployment process overwrites the directory on every release.
In any of those cases the setting says enabled, the backend is configured correctly, and WordPress is using its default in-memory cache that lasts one request. The site is exactly as slow as it was before, and nothing reports a problem.
So this reports the drop-in separately from the setting. The two together are the answer; either alone is not.
A misconfigured backend produces the same silence in a different way: WordPress falls back to the database rather than failing, and the only symptom is that the site is slow. litespeed/test-object-cache-connection is the call that actually opens the connection.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
enabled | boolean | Whether the object cache is switched on. |
backend | string | Which backend is configured. |
host | string | The configured host. |
port | integer | The configured port. |
dropin_installed | boolean | Whether object-cache.php is actually in place. |
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 the object cache actually working on this site?
It resolves to one call:
{
"ability": "litespeed/get-object-cache-status",
"parameters": {}
}Worth knowing
- Enabled without the drop-in means nothing is being cached.
- A deployment process that replaces the content directory can remove the drop-in silently.
- This reports configuration and the drop-in; the connection test proves the backend.
Related abilities
- Test Object Cache Connection — prove the backend answers
- Update Object Cache Settings — change the backend
- Flush The Object Cache — clear it
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category