litespeed/purge-cache purges LiteSpeed’s cache by target, from everything down to the front page alone.
It is not confirm-gated, because nothing is lost. But on a large site every page now rebuilds on its next visitor, so the narrowest target that fixes the problem is the right one.
At a glance
| Ability | litespeed/purge-cache |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Purging |
| 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 |
The targets, and what each costs
all clears everything including generated CSS and JS. It is the reflex and it is usually too much: the generated assets take real work to rebuild and are rarely the problem.
lscache is the page cache only, which is the right target for “content looks stale”. object is the object cache and opcache the PHP opcode cache — different systems that happen to be purgeable from the same place.
css-js clears generated assets only, which is the target after a theme update, and ucss the unique-CSS artefacts. front-page is exactly what it says.
The cost of over-purging is invisible at the moment you do it and lands on the next few hundred visitors. On a busy site a full purge at peak time can be the difference between a responsive site and one that falls over, because every request that would have been served from cache now runs PHP.
Nothing is lost by purging, which is why there is no confirmation — but “recoverable” and “free” are not the same thing.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
target | string | No — defaults to all | all, lscache, object, opcache, css-js, ucss or front-page. |
What comes back
| Name | Type | What it is |
|---|---|---|
target | string | The target that was purged. |
purged | boolean | Whether the purge 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:
Clear the page cache.
It resolves to one call:
{
"ability": "litespeed/purge-cache",
"parameters": {
"target": "lscache"
}
}Worth knowing
- Prefer the narrowest target. A full purge is rarely necessary.
- Purging at peak time on a busy site moves real load onto the server.
- Nothing is lost — but the rebuild is not free.
- Idempotent.
Related abilities
- Purge URLs — when one page is stale
- Purge Posts — after an edit made outside WordPress
- Purge Generated CSS And JS — after a theme update
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category