Your agent signs in, then nothing happens
A completed sign-in with no tool calls after it usually means a CDN or firewall blocked the request. Read that in the Activity Log, confirm it, and fix it.
Read moreThe governed agent blog
Plain guides, governance notes, and honest use cases for running an AI agent against your own WordPress site.
A read-only look at your site and its plugins
Point an agent at a WordPress site for a plain inventory of the basics and the installed plugins, without handing it any power to change a thing.
Read moreOne search across every post type
Instead of hunting post type by post type, ask an agent once and see everywhere a phrase, product name, old link, or claim appears across your whole site.
Read moreThe abilities we deliberately left out
Most of the pitch is about what you can switch on. This post is about the floor under all of it: what an agent cannot do here, no matter what you enable.
Read moreWhat we fixed in the 1.7.1 correctness release
A fix-only release: WPML sweeps now read every configured language, tool discovery matches permission, and a broken discovery route resolves again.
Read moreWhat 1.7.0 adds: Enable all writes, and a fuller audit log
Version 1.7.0 adds a one-click way to enable a section's ordinary writes, deliberately leaving deletes and high-risk abilities locked, plus a fuller audit log.
Read moreWhat we fixed in the 1.7.0 correctness release
Version 1.7.0 closes an OAuth revocation race, stops a payment gateway credential leak, and fixes four ACF writes that were destroying content.
Read moreWhat we fixed: setting alt text said permission denied, for everyone
In 1.7.0 an agent setting an image's alt text hit a bare permission denied, with no hint that another tool would work. Why that happened, and what changed.
Read moreAI agent WordPress security risks
Five real risks of an AI agent on WordPress, deletion, data leakage, injected content, and credential exposure, mapped to the control that limits each one.
Read more