litespeed/flush-object-cache flushes the object cache through LiteSpeed’s own handler.
On a site running LiteSpeed, prefer this over the generic cache/flush-object-cache ability.
At a glance
| Ability | litespeed/flush-object-cache |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Object & Browser Cache |
| Requires | LiteSpeed Cache, active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
Same data, different bookkeeping
Both abilities clear the same entries. The difference is that LiteSpeed does not learn that the generic one happened: its own counters, its statistics and the hooks it fires on a flush are all bypassed.
In practice that means a site whose object cache is flushed generically shows a LiteSpeed admin screen reporting a cache state that no longer exists, and any integration listening for LiteSpeed’s flush event never fires.
Neither is catastrophic. But there is no reason to take the inconsistency when the LiteSpeed-aware call is right here.
Flushing the object cache is cheap in one sense — nothing is lost, everything is recomputed — and expensive in another, since every recomputation is a database query that was being avoided. On a busy site a flush is a load spike.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
flushed | boolean | Whether the flush was issued. |
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:
Flush the object cache.
It resolves to one call:
{
"ability": "litespeed/flush-object-cache",
"parameters": {}
}Worth knowing
- Prefer this over the generic flush on a LiteSpeed site.
- Nothing is lost, but everything is recomputed — it is a load spike on a busy site.
- Idempotent.
Related abilities
- Get Object Cache Status — check it is actually running
- Purge Cache — the page-cache equivalent
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category