13 areas
96 named operations, grouped by the work they do rather than by the tool that carries them. Each page below says what people ask for, what happens, and what that area deliberately will not do.
Every count on this page is derived from the plugin's own operation reference. Nothing here is a number typed into a marketing page.
Along with the whole safety model: the preview before every write, the capability check, the snapshot, the read-back, the rollback, the activity log and every switch.
The everyday work an editor does by hand: drafting, updating, restructuring, fixing links. An agent can do all of it, one addressed block at a time, and you see the diff before anything lands.
17 opsUploads, imports from a URL, alt text and captions, attachment and resizing. The import path is the most carefully written code in the plugin, because a fetch made by your own server is the one place an agent could be pointed somewhere it should not go.
8 opsMenus, their items, their nesting and their theme locations. The whole tree moves in one call, because navigation reordered item by item is briefly wrong in a way people notice.
6 opsDocuments, elements, widget settings, global tokens and display conditions. Elementor stores a page as one serialised tree, so every write here snapshots the whole document — which is why a rollback restores the page rather than a fragment of it.
19 opsACF and Meta Box groups, their fields and their values. Values go through the field plugin’s own update function rather than straight into post meta, so its formatting, serialisation and hooks all still run.
8 opsTitles, descriptions and robots directives, through the plugin the site already runs. There is no SiteHelm SEO table: the change shows up on your plugin’s own screens, and switching agents off leaves nothing behind.
6 opsList by status, approve, hold, spam or trash, and reply beneath a comment. Everything here asks for the same permission the site’s own moderation screen asks for.
3 opsWhich forms the site holds, what each one asks, its embed shortcode, and its most recent entries. Nothing here writes. That is a design decision, not a gap.
3 opsThe roster, and a single write: replacing a user’s roles with one role the site has actually registered. Role changes ask for promote_users and are declared high risk, because this is the operation that can change who else may act.
2 opsThirteen fields and no more: title, tagline, timezone, date and time formats, posts per page, front-page geometry, permalinks, discussion defaults and search-engine visibility. The allowlist is the whole feature.
2 opsConnection, environment, integration health, one operation’s schema on demand, and the ledger of everything that has changed. This is how a session starts well instead of failing halfway through.
5 opsPro adds operations for work that spans a whole site or a whole shop. It never takes one away, and it never gates a safety control.
Site-wide settings, schema, the 404 log and redirections, and bulk fixes across up to fifty posts in one previewed, reversible change.
8 opsProducts read and written; orders and customers read only, and always will be. A shop’s order history is a financial record, and there is no operation in the pair that could reach one indirectly.
8 opsThese are not roadmap gaps, and no tier unlocks them. They are the reason the list above is a list rather than a shrug.
No eval, no snippet store, no theme-file editor. There is no path from an agent to executing code.
No query passthrough. Every read and write goes through a typed operation with a schema.
No arbitrary file writes, and no WP-CLI passthrough.
Nothing is destroyed without a snapshot that can put it back.
Get the free plugin Connect an agent to it
All 96 operations in one list, each with its capability, risk and rollback policy.
referenceThe five gates every write passes, and the 11 refusals it can come back with.
referenceRequest it. Requests are public and votable, and are what the roadmap is built from.
board
SiteHelm