Version 1.12.0 lets an AI agent edit a WPBakery Page Builder or Avada page one element at a time. Every new tool starts off, a save that would change anything else on the page is refused, and each element edit comes with a way back through WordPress revisions when the site keeps them.
The catalog is now 216 abilities, up from 186. The 30 new tools cover WPBakery Page Builder, Avada and block-theme navigation menus. The release also fixes a bug that let three general content tools overwrite a Divi page layout.
Agent Abilities for MCP is a free WordPress plugin that lets Claude or ChatGPT work on your site as a WordPress user you pick, with this plugin’s own tools off until you turn them on.
Takeaways:
- WPBakery Page Builder (12 tools) and Avada (18 tools) pages can be read as an outline of elements, then changed, added to, moved or removed one element at a time. All of the new tools start off.
- An element write is refused, with nothing saved, if saving the page as the connected user would change anything else on it. Element edits return a revision id for Restore revision when WordPress kept one, and settings writes return the previous values.
- Site-wide builder settings and the Avada Studio import need a user who can manage options. The import has its own switch, which no Enable all button ticks.
- update-page, update-post and replace-in-post could overwrite a Divi layout in every release from 1.7.4 to 1.11.2. They now refuse.
- None of the 30 new tools appears in the Changes tab.
Can an AI agent edit a WPBakery or Avada page without breaking it?
It can edit one element at a time, and a write that would change anything else on the page is refused with nothing saved. That is a guard, not a guarantee: a revision is the way back only when WordPress kept one, and the Studio import and navigation edits have no undo from this plugin.
Edit one element, not the whole page
A page builder owns its page’s layout, so a whole-page text edit can report success and change nothing. Until now an agent on an Avada page could only read the markup of Avada’s builder (Fusion Builder) and replace text inside it. The new tools work on the page the way the builder does, one element at a time.
The flow is the same on both builders:
- Read the outline.
avada-get-page-contentorwpbakery-get-page-contentwithinclude_structurereturns each element’s tag, nesting depth, attributes and a fingerprint, which is a short hash of that element’s stored source. It also returns a fingerprint for the whole page. - Look up the element.
avada-list-elementsandwpbakery-list-elementslist the elements the builder has on your site and, for one element, each setting and whether it can be written. - Name the element. Each write names the element by its index and fingerprint. A page that changed since the read is refused.
- Write. Update, insert, move or remove one element. A saved WPBakery template, a Templatera template (Templatera is a WPBakery add-on for templates) or an Avada Library item (Avada’s saved sections, columns and elements) can be placed too.
| Area | Tools | New in 1.12.0 | Who can use them |
|---|---|---|---|
| WPBakery Page Builder | 12 | 12 | Edit access to the post; the site-wide tools need manage options |
| Avada | 18 | 16 | Edit access to the post; the site-wide tools need manage options |
| Block-theme navigation | 2 | 2 | A user who can edit theme options |
The Avada integration page and the WPBakery Page Builder page list every tool, and the page builders docs cover permissions. The full catalog is on the abilities page.
What the guard refuses
A write that would touch anything beyond the element you asked for is refused, and nothing is saved.
These are the main refusals:
- a stale element index or page fingerprint
- an element type the builder’s own element map does not list
- a setting the element does not have, or one that cannot be written
- an update that would add or remove an element
- an edit to a global Avada Library element on the page that shows it, because that is edited in the Library
- a removal when no revision could bring the element back
Text, links and images work for anyone who can edit the page, and so do colours and spacing in Avada. Code blocks, raw HTML and JS, Design Options, page CSS and JS, and settings that can carry script need a user who may post unfiltered HTML. So do square brackets, percent-encoded brackets and data-* attributes in body text.
A builder’s Role Manager is its own permission setting. Neither builder’s Role Manager widens or narrows what an agent can do with this plugin’s tools: the agent gets what its WordPress user can do. WPBakery is the one exception, because its Role Manager decides whether this user may save custom JS, and WPBakery’s own save filter still runs. If you rely on a Role Manager setting to hold an editor back, connect the agent as a user whose WordPress role already fits.
A way back for each kind of edit
The Changes tab from 1.11.2 still covers 25 tools, and none of the 30 new ones is among them. Most new writes bring their own route back instead.
| What the agent changed | The way back |
|---|---|
| An element, a template or a Library item on a page | The tool returns restore_revision_id when WordPress kept a revision. Pass it to restore-revision, which now works on Avada and WPBakery pages. |
| Page CSS or JS, Avada page options | No revision is kept. The tool returns previous, and you send it back. |
| WPBakery settings, Avada Global Options, layouts, Slider settings | The tool returns previous, and you send it back. |
| A block-theme navigation | Not in the Changes tab. The earlier version can be restored only if WordPress already kept it as a revision. |
| An imported Avada Studio item | No undo from this plugin. You delete the item in Avada’s Library. |
A revision is not guaranteed. The response says so when the site or content type keeps none, when WordPress saved none before the change, or when the revision limit or another plugin deleted it during the save. Remove element is refused up front when no revision could bring the element back, and for an Avada form or off canvas panel, which keep none.
Some plugins turn revisions off for the whole site, GeoDirectory among them. A WP_POST_REVISIONS line in wp-config.php turns them back on.
One caveat on Avada page options: sending previous back restores every value as Avada reads it, but not always the same stored bytes. An option stored as default comes back as no stored option, which Avada treats the same.
Site-wide settings and the Avada Studio import
Some changes reach every page at once, so they need a user who can manage options. That covers WPBakery settings, Avada Global Options, Avada layouts and their sections, Avada Slider settings and both Avada Studio tools.
The three writes that change site-wide options (WPBakery settings, Avada Global Options and Avada layouts) are classed as destructive. After an Avada Global Options change, a page cache plugin keeps serving its cached pages until you purge it.
Avada Studio is Avada’s own library of ready-made templates, sections, elements, icons, forms and off canvas panels. The two Studio tools start off, and the import is not part of the high-risk lock.
avada-import-studio-itemhas its own switch. No Enable all button ticks it.avada-list-studio-itemsis refused until the import is on.- Both need a user who can manage options.
When an agent uses them, Avada downloads the catalogue and items from avada.studio under your site’s own Avada registration. This plugin sends nothing in that exchange and only checks with Avada that Studio is available. Avada’s terms and privacy policy apply.
Navigation menus, page parents and the homepage
Two new core tools, list-navigations and update-navigation, read and replace block-theme menus (the navigation a block theme’s Navigation block shows). A classic menu is not listed there, and list-menus still covers those. The menus and homepage docs have the details.
update-navigation replaces the whole navigation, including blocks that are not links, such as a page list, which list-navigations names under other_blocks. It takes up to three levels and 100 items, and it refuses a navigation owned by a page builder. Each link is saved as a plain custom link, so open in a new tab, rel, CSS classes and a link’s binding to a page are not kept.
Three smaller additions go with it. create-page and update-page take a parent and a template, update-site-settings can set the static homepage and the posts page, and wc-update-product can remove an attribute.
The Divi fix
Since the Divi check arrived in 1.7.4, update-page, update-post and replace-in-post could overwrite the layout of a page built with Divi, and 1.11.2 still did. The plugin’s builder check looked for a key named et_pb_use_builder, which is a form field name. Divi stores _et_pb_use_builder, so the check never saw a Divi page.
All three now refuse a Divi page, as they do for the other builders. If you enabled any of them on a site with Divi pages, update, and look over Divi pages an agent edited with any earlier version.
Smaller changes
| Change | What it means |
|---|---|
| Plugins’ own tools | The tab that was called Other plugins has a new name, and the Search sub-tab on Abilities is now Site search. |
| Alert modes | Notifications read Email alerts as they happen and One email a day. |
| Admin accent | The plugin’s accent colour follows your WordPress Admin Color Scheme. |
| Connection links | The Connection tab adds Add to Cursor and Add to VS Code links. Cursor documents its install link format. |
| Old site address | The Connection tab can end tokens issued for an earlier site address. |
| Expired tokens | An expired or revoked OAuth token now gets error="invalid_token" in the 401, which RFC 6750 defines for exactly that case. A client can then refresh or sign in again. |
| Alert email timing | On hosts that cannot close the page before sending, alert emails go through WP-Cron. Where WP-Cron never runs, an alert can arrive an hour or more late. |
What it does not do
- Flexbox and grid items in WPBakery: adding an element to a WPBakery flexbox or grid container item, or moving one in, is refused. Elements already inside can be reordered, updated and removed.
- Visual Composer Website Builder gets no editing tools. The general content tools still refuse its pages.
- Avada typography is not writable in page options or element settings. In Global Options it is writable as sub-values such as font family and size.
- Avada settings driven by dynamic data are refused for everyone.
- The Studio import has no undo in this plugin.
- The Avada element tools need Avada Builder 3.15.6 or later.
Before release we ran 91 test prompts through claude.ai and ChatGPT on a demo site with WPBakery, Avada, Avada Core and Templatera active. They covered both builders, the Avada Studio import, navigation, the Divi refusal, OAuth and the WooCommerce fixes. The defects they found were fixed and re-tested.
The run did not include opening the Avada Live builder, or either builder’s own editor, after a write, so open the first edited page in the builder yourself. Treat a first edit on a live page as a test, and keep a backup.
After you update
Nothing changes for your agents until you enable a tool. The Divi fix applies as soon as 1.12.0 is installed. The new tools appear on the Abilities tab, and the WPBakery and Avada ones appear on the Integrations tab only while their plugin is active.
To try it on one page, enable the read tools first, then one write tool. The builder write tools are in no preset except Custom, so a preset will not switch them on for you.
The full history is on the changelog. The release before this one was 1.11.2.