What 1.11.2 changes: undo what an AI agent changed

Version 1.11.2 came out on 10 November 2026 (GMT). Its main change is a way back: a Changes tab that puts back what an agent changed, and two optional tools that let an agent undo its own work.

Two tools were added, so the catalog is now 186 abilities, 92 in core and 94 from integrations. Both new tools start off.

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. Updating needs no setup. History starts recording from the update, and you can switch it off.

Takeaways:

  • A new Changes tab keeps up to 30 days of what agents changed with 25 of this plugin’s tools. Revert puts a change back if the item hasn’t been edited since, and Revert all puts back a site-wide find and replace as one group.
  • Two new tools, list-changes and undo-change, let an agent undo its own changes from the last 24 hours. Both start off.
  • Every write tool now says in its response whether its change can be undone, and why not when it can’t.
  • wc-update-payment-gateway’s order is now a zero-based position. A script that passed a stored sort value now gets a position.

The Changes tab

Before this release, the nearest thing to a way back was WordPress revisions, through the Restore revision tool. Revisions are a thin net for an agent’s edits. WordPress saves no revision on insert and stores the new state on update, so on a first edit to a post with no earlier revisions there is no earlier copy to go back to.

The Changes tab keeps that copy itself. Each covered edit gets a row with when it happened, the tool, the item, the field names it touched, the user it ran as and a status. The tab lists field names and never contents, though the earlier values are stored in a table in your site’s database.

These actions sit on the tab:

Action What it does
Revert Puts one change back if the item has not been edited since. It refuses a revert that would overwrite a newer edit.
Revert all Puts a site-wide find and replace back as one group.
Clear history Deletes the whole history. Nothing in it can be reverted afterwards.

A post row that touched the content and has revisions also links to WordPress’s own Compare revisions screen.

The tab keeps up to 30 days. When the history is full, the oldest values go first, so 30 days is the most you can count on. Undo what an AI agent changed in WordPress has the screenshot and the full list, and the docs page covers the settings.

What it covers, and what it does not

It records changes made with 25 tools: posts, pages and custom post types, creates, trashes, block edits, terms, custom fields (post and term meta), featured images and SEO fields. Undoing a create moves the new item to the Trash. The SEO tools are in that count and appear only while their SEO plugin is active.

It does not cover any other tool of this plugin’s. That includes permanent deletes, orders, refunds, user accounts, file uploads, WooCommerce products, ACF field values, menus, comments and events. Tools from other plugins are not recorded either, and notifications, webhooks and anything already read are not recalled.

Inside the 25 tools a revert can still be refused: the item was edited after the agent’s change, the change was too large to keep, a plugin filters the field, a page builder now owns the post, or the Trash is switched off. A meta key that looks like a secret has no value stored at all.

Each write tool’s response now carries an undo answer saying whether the change can be undone. For a tool outside the 25 it gives the reason, so an agent does not promise a rollback it cannot deliver.

Agents can undo their own changes

Two new core tools, list-changes and undo-change, let an agent correct itself.

  • list-changes is a read tool. It lists the connection’s own recent changes to one post or term, with the field names and whether each can be undone now. It never returns a value.
  • undo-change reverts one change per call. It works only on a change made on the agent’s own connection, from the last 24 hours, with a limit of 30 undo calls an hour per connection.

Both start off. Because undo-change is destructive, the Read only, Content editor and Shop manager presets leave it out. The Custom preset narrows nothing.

The site owner is not held to the 24-hour window. If a change is older, an agent is refused, and you can still revert it from the Changes tab while it is kept.

What the history stores

Undo needs the earlier values, so the plugin keeps them, in a table of its own in your database. The earlier values stay in your database and are never sent to us. list-changes gives an agent field names, never a value.

  • It records only while the plugin is active, and the Keep change history switch under Settings turns it off.
  • The table is dropped on every uninstall and emptied by Reset.
  • WordPress’s export and erase personal data tools now cover the change history, and the activity log too.
  • Developers can add regular expressions for meta keys whose values should not be stored with the new aafm_undo_secret_key_patterns filter.

Fixes in 1.11.2

Fix What changed
Payment gateway order wc-update-payment-gateway now takes order as a zero-based position, as wc-get-payment-gateway reports it, and renumbers the stored gateway order. Two gateways could end up sharing one sort value, and WooCommerce then dropped one from checkout.
Order payment method wc-get-order returns payment_method and payment_method_title.
Sale price A variation’s sale price can be cleared by sending an empty string.
Named errors A refund above the remaining amount, a user deleting their own account, deleting or demoting the last administrator, a missing reassign user, trashing an item already in the Trash and a tool aimed at a content type that isn’t exposed each return a named error instead of a generic one.
Products and terms Add post terms aimed at a product still refuses when products are not exposed as a content type. It now says to use wc-update-product, to callers who can edit.
Post counts Count posts lists the statuses that plugins register, for any that have posts.
Descriptions Several tool descriptions and messages were reworded, including Replace in post and Replace block, which now say a post with no earlier revisions has no earlier copy to restore, and that undo-change or the Changes tab can revert the change while change history is on.

After you update

Change history records agent edits from the update on, in a new table kept up to 30 days and dropped on uninstall. A one-time notice on the plugin’s pages says so, and you can dismiss it. To stop recording, switch off Keep change history under Settings.

The two agent undo tools start off, so nothing changes for your agents until you enable them. If a script passes a stored gateway sort value to wc-update-payment-gateway, change it to send a position.

The full history is on the changelog. The release before this one was 1.11.1.

When to keep a backup anyway

Undo is not a rollback for the whole site. It covers 25 tools, it keeps up to 30 days, and it will not undo a permanent delete, an order, a refund or a file upload. For those, keep a backup. A revert is also not a promise: the item has to be unchanged since the agent’s edit, and the tab itself lists field names, with only a Compare revisions link to WordPress’s own screen when the post has revisions.