Your AI can't approve its own work

Respira for WordPress lets an AI assistant edit your live site, and it rests on one promise: the AI proposes, a person decides. Edits to a published page land on a draft copy that someone approves, and every change has a snapshot behind it. This week's releases make that line sharper, and Respira now sits on top of the official WordPress MCP Adapter.

9.1.26: the owner's controls belong to the owner

The settings that decide what an AI may do on your site are now out of the AI's reach. An assistant connected with a Respira key cannot open Settings, Governance, Keys, the approval queue, Reset or Troubleshoot. It cannot change its own tool profile, switch audit logging off, allow direct edits, approve its own drafts or create a new key. When it tries, Respira refuses, records the attempt, and tells the assistant to ask the site owner.

Nothing changes for you in wp-admin. The two routes an assistant legitimately needs stay open: generating an activity report, and receiving a fresh site token from your dashboard.

Three more lines in the same release:

• A limited key stays limited everywhere. A Read only, Content editor or Builder key is now held to its limits on WordPress's own routes too, not only on Respira's.
• Rules read every route the same way, however the letters in the address are written.
• A switch for Site Editor writes. Changing a block theme's templates, template parts, menus and patterns used to need a line in wp-config.php. It is now a toggle under Respira > Settings > Safety controls, off by default, because one template change reaches every page that uses it. An assistant that meets the closed switch is told where you turn it on.

9.1.27: structure changes are one restore away

Changing a post type, a taxonomy or an ACF field group now saves the previous definition first. Each change answers with a recovery snapshot, and one restore puts the old definition back, including an ACF group Respira registered itself. A wrong label, a dropped field or a moved location is no longer permanent.

Respira and the official WordPress MCP Adapter

The WordPress MCP Adapter is now a canonical plugin on WordPress.org, as Search Engine Journal and The Repository reported. It turns the abilities a site registers into tools any MCP client can call. That is the right foundation, and Respira builds on it:

• Respira works with the official plugin. Since 9.1.24 Respira no longer ships its own copy. Install the Adapter from WordPress.org and Respira's abilities appear through it, on their own address, next to Respira's own endpoint, so neither takes over the other.
• Calls through the Adapter are counted since 9.1.25, so you can see which route your assistants actually use.

What the Adapter does not do is decide whether a change should happen. It exposes abilities; it has no drafts, no approvals and no undo. Respira is the production layer on top: a draft copy a person approves before a published page changes, a snapshot before every write, rules the agent cannot override, and edits written in your page builder's own format across 17 builders. The Adapter gives an AI the keys. Respira decides which doors they open, and keeps a way back.

Written down this week

Four security pages now spell out what used to live only in the code:

• OAuth sign-in: PKCE, the two scopes, and when each token expires
• API key management: access profiles, scopes and the hourly limit
• Undo and verifying a restore: how to prove a page is back exactly as it was
• Usage limits: every limit, with the numbers

Update from your WordPress dashboard to get all of it. The full notes for every version are on the releases page.