litespeed/get-crawler-settings reads the crawler configuration: whether it is enabled, the crawl interval, the server load limit, the sitemap it works from, and the roles and cookies it simulates.
It is separate from litespeed/get-crawler-status, which reports what a run is currently doing.
At a glance
| Ability | litespeed/get-crawler-settings |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › The Crawler |
| 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
Every settings read in this suite returns the same shape — key, current value, type, and whether the key is writable — and every settings write takes the same shape back: a map of key to value, applied as a patch. Keys are owned by exactly one area, and litespeed/list-settings-areas is the map of which area owns what.
The roles and cookies are the part worth understanding. A crawler that simulates no role warms only the logged-out cache; one that simulates a subscriber warms a second set of copies; add a currency cookie and there is a third. Each combination is a separate crawler variant and a separate pass over the whole sitemap.
That is how a crawler configuration that looks small turns into a crawl that takes hours. litespeed/list-crawlers shows the resulting variants, which is usually a surprise the first time.
The load limit is the safety valve: the crawler pauses when server load rises above it. Set too high, it keeps crawling while real visitors queue.
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:
How is the LiteSpeed crawler set up?
It resolves to one call:
{
"ability": "litespeed/get-crawler-settings",
"parameters": {}
}Worth knowing
- Each role-and-cookie combination is a separate full pass over the sitemap.
- The load limit is what stops a crawl hurting real visitors.
- Configuration only — the status ability reports the run.
Related abilities
- List Crawlers — the variants this configuration generates
- Get Crawler Status — what is happening now
- Update Crawler Settings — change it
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category