litespeed/update-advanced-settings changes the advanced settings: heartbeat control for the three contexts, instant-click prefetching, and debug logging.
Throttling the heartbeat is one of the cheapest wins available. Leaving debug logging on in production will fill the disk.
At a glance
| Ability | litespeed/update-advanced-settings |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Toolbox |
| 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 |
How it works
Start with the front-end heartbeat. Almost nothing uses it, every fire is an uncached WordPress bootstrap, and turning it off costs nothing on the overwhelming majority of sites.
The dashboard heartbeat can usually be slowed rather than stopped. The editor one is the one to leave alone unless there is a specific reason: it drives autosave and the post-lock notice, and stretching it means more lost work when a browser crashes and more chance of two people editing the same post unknowingly.
Instant-click prefetching fetches a page when a visitor hovers over its link, so the navigation feels instant. It is a genuine improvement and it multiplies requests — every hover is a page load, including hovers that never become clicks. On a well-cached site that is cheap; on an uncached one it is not.
Debug logging should be off in production. It is invaluable while diagnosing and it writes continuously, and the usual way a site runs out of disk is a log somebody forgot.
The write is a patch, not a replacement. Send one key and one key changes; everything else in the area is left alone. The response names the keys that actually moved, so a payload that matched the existing values comes back with an empty list rather than a misleading success.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
settings | object | Yes | A map of setting key to new value. Keys outside this area are refused, and the refusal lists what the area accepts. |
What comes back
| Name | Type | What it is |
|---|---|---|
updated | array | The keys that actually changed. An empty array means every value you sent was already set. |
settings | array | Every setting in the area after the write, in the read shape. |
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:
Turn off the front-end heartbeat.
It resolves to one call:
{
"ability": "litespeed/update-advanced-settings",
"parameters": {
"settings": { "misc-heartbeat-front" : false }
}
}Worth knowing
- Front-end heartbeat off is nearly always free.
- Leave the editor heartbeat alone unless you accept less frequent autosave.
- Instant-click prefetching multiplies requests — good on a cached site, costly otherwise.
- Turn debug logging off when you are finished with it.
Related abilities
- Get Advanced Settings — read the current values
- Get Environment Report — where the log would show up
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category