What 1.10.2 changes: playbooks on limited connections

Version 1.10.2 lets connections on the Content editor and Shop manager presets read playbooks, the step-by-step instructions you write on the Playbooks tab. It came out on 5 November 2026, a day after 1.10.1.

In 1.10.1 only Read only and Custom connections could list and load a playbook. Content editor is the preset built for content work, so those connections had no way to use the feature. Nothing else needs changing, and the catalog is still 184 abilities, 90 in core and 94 from integrations.

Takeaways:

  • Content editor and Shop manager connections can now use List playbooks and Get playbook, once you switch those two tools on.
  • The Playbooks editor refuses to save over a playbook someone else changed after you opened it.
  • A request from another site’s web page now gets a 403 even when it carries wrong credentials.
  • A paused connection leaves no “paused” note in the server instructions after you resume it.

Playbooks on limited connections

Two reads were added to two presets, and nothing else was.

Preset Reached the two playbook tools in 1.10.1 Reaches them in 1.10.2
Read only Yes Yes
Content editor No Yes
Shop manager No Yes
Custom Yes Yes

Settings, the Activity Log and site info stay outside Content editor and Shop manager. A preset still only narrows what you switched on under Abilities, so the two tools stay off until you enable them in the Site section.

On our demo site, claude.ai listed the playbooks on a Content editor connection, loaded Publish checklist and walked it, and ChatGPT listed and loaded the same playbook. The walk-through is in run WordPress playbooks in ChatGPT or Claude on limited access.

The Playbooks editor has a new check as well. If someone else saved the playbook after you opened it, your save is refused and your text stays in the form, so you can copy it, reload to see their version and add your change again.

A web page’s origin is checked before its credentials

1.10.1 refused a request from another site’s web page with a 403, but a request that also carried a wrong Application Password got a 401 first. Now the origin check runs before authentication, so a foreign web page gets the 403 whatever credentials it sends.

On our demo, on a build made just before this release, a foreign Origin with a made-up Application Password got a 403 with the code aafm_origin_not_allowed, and an Origin of https://claude.ai with a made-up password got a 401. The check does not apply to a request with no Origin header.

Responses requested with ?_envelope=1, a WordPress REST parameter that moves a response’s status and headers into its body, now send Cache-Control: no-store like every other response from this endpoint. A logged-out ?_envelope=1 request on the demo carried it.

Smaller changes

  • A paused connection used to get a “paused” line in the server instructions, and a client could keep showing it after you pressed Resume. The line is gone. The refusal on each tool call still says the connection is paused.
  • The refusal for an unknown ACF field now names fields only to a connection that could list them with List ACF field groups. Anyone else still gets a refusal that says nothing was written.
  • An app the site no longer recognizes, for example after its registration was deleted, now gets the steps and the MCP URL to add it again.
  • Seven integration tool descriptions now match what the tools do. Update WooCommerce customer, for one, now says it needs the edit_users capability on top of the high-risk lock. Every description that lists page builders names all five: Elementor, Divi, Beaver Builder, Avada and Visual Composer.
  • The ability picker on the Playbooks tab has space between its search box and the count line.

Since 1.11.1 (2026-11-08): the five builders named above are now ten, with Oxygen, Breakdance, Brizy, Bricks and WPBakery added. An excerpt-only edit is the one write the guard lets through. See the changelog.

Updating

To use playbooks on a limited connection, turn on List playbooks and Get playbook, then make the client reload its tools: in ChatGPT, Settings, Integrations, Plugins, the app, Refresh, and in Claude a new chat.

The full history is on the changelog. The release before this one was 1.10.1, and the Playbooks docs and the Playbooks library cover the feature itself.