What 1.7.7 changes: one Save changes button on the Abilities tab
The Abilities tab had a main Save button plus four on its cards, and pressing only the main one lost edits to meta keys and content types. 1.7.7 has one button.
Read morePlain guides, governance notes, and honest use cases for running an AI agent against your own WordPress site.
The Abilities tab had a main Save button plus four on its cards, and pressing only the main one lost edits to meta keys and content types. 1.7.7 has one button.
Read moreBefore 1.7.6, an OAuth token for the MCP endpoint also signed its holder in elsewhere on a WordPress site. What it reached, what changed, and what else shipped.
Read moreWordPress returns one value for both 'nothing here' and 'could not ask'. Nine review rounds on 1.7.5 kept finding that bug, once in a consent check.
Read moreThe per-connection allowlist was a typed textarea in 1.7.4. In 1.7.5 it is a searchable checkbox picker with role and client selects, so no more spelling slugs.
Read moreAsk an agent to edit an Elementor page and the write used to report success while the page stayed the same. In 1.7.4 it refuses and names the builder.
Read moreThe first release that changed the ability catalog: five new integrations, two core abilities, a page builder write guard, and an allowlist that only narrows.
Read moreOn sites with a persistent object cache, read-only mode and the high-risk lock could refuse to change, and the activity log recorded the change as done anyway.
Read moreThe sign-in screen now identifies a connector by its verified redirect host, and the Activity Log records requests that reach WordPress and fail.
Read moreA default of ours stopped ChatGPT connecting. Also fixed: a mangled redirect address, a session ID for a session never written, and a tool list that ate memory.
Read more