litespeed/get-advanced-settings reads the advanced settings: WordPress heartbeat control for the front end, the dashboard and the editor; instant-click prefetching; and LiteSpeed’s debug logging.
The heartbeat controls are a real performance lever on a busy site and are easy to overlook.
At a glance
| Ability | litespeed/get-advanced-settings |
| 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
The WordPress heartbeat is an AJAX request that fires on a timer while somebody has a page open. In the editor it drives autosave and lock notices; on the dashboard it updates widgets; on the front end it usually does nothing useful at all.
Each of those requests is a full WordPress bootstrap that bypasses the page cache entirely. Ten editors with the admin open is a steady stream of uncached requests, and on a shared host that is a meaningful fraction of the site’s capacity.
So the three contexts are controlled separately. Turning the front-end heartbeat off is nearly always free; slowing the dashboard one is usually fine; interfering with the editor one costs autosave frequency and lock detection, which is a real trade.
Debug logging is the other thing here, and it is the setting most likely to be left on. It writes a log file continuously, and on a busy site it fills a disk.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
settings | array | One row per setting: its key, its current value, its type, and whether this suite can write it. |
count | integer | How many settings the area holds. |
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 heartbeat throttled on this site?
It resolves to one call:
{
"ability": "litespeed/get-advanced-settings",
"parameters": {}
}Worth knowing
- Heartbeat requests bypass the page cache entirely.
- The three contexts — front end, dashboard, editor — are controlled separately.
- Debug logging left on in production fills disks.
Related abilities
- Update Advanced Settings — change them
- Get Environment Report — the wider diagnostic
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category