Classic Editor keeps two options, but what a site actually does depends on more than those options. A site that has never saved the settings has no stored value at all and still behaves as classic; on multisite, the network can lock per-site settings entirely.
editor/get-editor-settings reports the configuration in effect and the layer that decided it, so your AI works from what the site does rather than what the options table happens to hold.
At a glance
| Ability | editor/get-editor-settings |
| Toolset | Classic Editor — toolset/classic-editor |
| Group | Classic Editor › Editor Settings |
| Requires | Classic Editor, 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
It returns the site-wide default editor, whether users may choose their own, the raw stored values, the current user’s preference, and on multisite whether the network has locked per-site settings.
Pass user_id to resolve another user’s preference instead of the current one. That preference is only consulted while users are allowed to choose.
The message names the deciding layer — for example “Editor: classic (decided by the site setting)” — so the answer can be shown to a person as-is.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
user_id | integer | No | Resolve the per-user preference for this user instead of the current one. Only consulted when users are allowed to choose. |
What comes back
| Name | Type | What it is |
|---|---|---|
settings | object | The effective editor, the layer that decided it, the stored values, the user preference and any network lock. |
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:
Which editor are authors getting on this site, and why?
It resolves to one call:
{
"ability": "editor/get-editor-settings",
"parameters": {}
}Worth knowing
- Read this rather than the options directly — an unsaved site has no stored value but behaves as classic.
- The per-user preference is user meta under the blog-prefixed key
{prefix}classic-editor-settings, with the valuesclassicorblock. - On multisite the network may lock per-site settings; the result says so when it does.
Related abilities
- Update Editor Settings — change the default or the user switch
- Get Post Editor — the answer for one particular post
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category