litespeed/export-settings returns the whole LiteSpeed configuration as a portable payload, for backup or for copying to another site.
There is deliberately no matching import ability.
At a glance
| Ability | litespeed/export-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
LiteSpeed’s own importer reads from a file on disk. An import ability would therefore have to take caller-supplied content and write it to the filesystem before handing the path to the plugin.
Materialising caller-supplied content as a file is not a risk this suite takes. The content comes from a conversation, the file lands inside the site, and the gap between “a settings export” and “something else entirely” is whatever validation happens to be in place that day.
So the export exists and the import does not. To move between known configurations, litespeed/apply-preset applies a shipped preset and litespeed/restore-preset-backup rolls back to a backup LiteSpeed took itself — both working from content the site already holds.
The export is still worth taking before any significant change. It is a record you can read and compare against, even if restoring it means applying settings through the abilities rather than importing a file.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
settings | object | The whole configuration as a portable payload. |
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:
Give me a copy of the LiteSpeed configuration before I change anything.
It resolves to one call:
{
"ability": "litespeed/export-settings",
"parameters": {}
}Worth knowing
- No import ability exists, by design.
- Use presets and preset backups to move between known configurations.
- Worth taking before any significant change, as a record to compare against.
- Read-only.
Related abilities
- Apply A Configuration Preset — the supported way to change wholesale
- List Preset Backups — the rollback points that exist
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category