# What changed in Respira from 9.0 to 9.2.6

> A month of Respira for WordPress in one page: Avada and YOOtheme Pro as builders 18 and 19, Divi inserts that leave the rest of the page alone, Elementor 4.3, plan mode, redirects, a lighter plugin, and client notes that arrive with photos.

Source: https://www.respira.press/blog/respira-9-0-to-9-2-6

---

![A Respira card on warm paper: What changed from 9.0 to 9.2.6, 63 plugin releases in a month, with the Respira mandala rising out of an open box](https://www.respira.press/blog/respira-9-0-to-9-2-6/respira-9-0-to-9-2-6-kv.webp) 

From 9.0 on 16 September to 9.2.6 on 15 October.

Respira for WordPress lets an AI assistant edit your live WordPress site in your page builder's own format, with a draft copy you approve and a snapshot behind every change. Between 9.0 on 16 September and 9.2.6 on 15 October I shipped 63 releases of the plugin, and the Respira MCP server went from 8.3.25 to 8.6.1\. If you update every few weeks, this is the page that says what is different, sorted by what you can now do rather than by version number. 

## Two more builders: YOOtheme Pro and Avada

Respira now works with 19 page builders. **YOOtheme Pro** arrived in 9.2.0\. Pages are read and written as YOOtheme builder layouts, and every write is saved through YOOtheme's own builder, so a page opens in the YOOtheme customizer like one built there. Your AI gets every element's fields and allowed values from the running theme, custom elements from child themes included. YOOtheme's site templates (single posts, the blog index, archives, search, the 404 page) can be read and changed too. A new template starts disabled so you can look at it first, and changing an enabled one needs your confirmation. 

**Avada** arrived in 9.2.6\. Pages built with Avada Builder are read and written as Avada's own shortcodes: containers, rows, columns and elements such as titles, text blocks, buttons, images, toggles, checklists and code blocks. Anything Respira does not model, a third-party shortcode, a newer Avada element or a Library global, is kept exactly as it was, byte for byte, and a write that would not read back the same way is refused before anything is saved. After every write the page's compiled Avada CSS is cleared so the change shows, and the edit link opens the page in Avada Live. 

Avada's design system, Layouts and Library are in reach as well. Your AI can read the global colour palette and typography sets and change them through Avada's own Global Options; because that restyles every page at once, it asks you first and takes a snapshot that a restore puts back. Layouts (which header, page title bar, content and footer each one uses, and where it applies) can be listed, read, created and changed, and a new Layout without conditions starts out showing nowhere. Library items are placed the way Avada places them, so a global item keeps following edits to the original. All of it was checked on a real Avada 7.16.2 site with Avada Builder 3.16.2\. Pricing Table, Tabs and Testimonials were rebuilt in Avada 7.16 and are marked experimental, so check those in Avada Live after a change. 

Every builder now also says what it can write (9.2.0). Thrive Architect, which only edits existing text, and SeedProd, which is read only, refuse a page build before anything is written, instead of failing halfway. 

## Divi: inserts that leave the rest of the page alone

Adding content to a Divi page used to read the whole page and write the whole page back. In 9.2.6 only the new content is written, spliced into the stored page at one position. Every other byte stays as stored, including global module references, third-party blocks and modules Respira does not know, and the plugin checks that before and after the write. A full-width global hero no longer comes back boxed inside a new section. A large page can also be built in small pieces now (the frame first, then rows and modules by position), and a retried piece never lands twice. 

- **Divi 5.15 Components and Slots survive every write** (9.2.6), checked on a Divi 5.15.1 site. The module catalogue now lists 117 module types.
- **A full rewrite keeps the blocks it did not change**, byte for byte, and refuses a rewrite that would restructure one of them (9.2.6).
- **Edit links open Divi pages in the Divi Visual Builder**, and Elementor, Bricks, Beaver Builder, Breakdance and Oxygen 6 pages in their own editors (9.2.6).
- **Native Divi 5 styling by default** (9.1.0). A style Divi has a design setting for is written as that setting, so the next person can see and edit it in the Visual Builder. Measured on Divi 5.13 with the styling a real prompt carries, native attributes went from 63 of 116 requested styles to 110.
- **Theme Builder headers and footers you can review first** (9.1.15). Your AI can build a global header or footer unassigned, show it to you, then put that same layout live. Template conditions cover everything Divi offers (9.1.3).
- **Hide an element per device** on Divi 5 (9.1.9), and **Additional CSS changes show** on Divi 4 and 5 without saving a layout again (9.1.32).
- **Divi 4 sites are no longer mistaken for Divi 5** (9.1.30).

## Elementor 4.3

Elementor 4.3 brought new element types and a new text format, and Respira caught up in steps. Edits work on pages with the new headings and paragraphs (9.1.1), and a page with an accordion can be edited (9.1.6). In 9.2.6 the accordion, background video and list elements can be built and edited, modelled from Elementor 4.3.5's own code next to the 20 v4 element types Respira already knew. The list needs Elementor's e\_list feature, which Elementor ships switched off, and is refused with that reason elsewhere. Pages Respira writes can now be saved in the Elementor editor: before storing a new or changed v4 element, Respira asks the running Elementor to check its settings the way its own save does, so nothing is stored that Elementor would throw away. Element ids look like Elementor's own, and a style written as plain CSS reaches the page on Elementor 4.2 and newer (9.0.12). 

## Edits that land on every builder

In 9.0.3 to 9.0.5 I ran every add-element tool and every element edit on every builder I have a test site for, and read the published page after each call. Edits now land 13 or 14 times out of 14 on each builder; before, the same edits reached the page between 0 and 8 times out of 14 while reporting success. The add tools render on Elementor, Bricks, Beaver Builder, Breakdance, Oxygen 6, Divi 4, WPBakery and block sites. Since then: 

- **A change can name the page version it was based on** (9.0.3), and is refused with nothing written if someone else changed the page in the meantime.
- **Brizy elements can be found, edited and moved by id**, and text edits are saved (9.1.3).
- **WPBakery pages with many addon elements can be read and edited again** (9.2.4). On a site where every call ran out of memory, the same calls now finish in under two seconds.
- **A heading shows its words** on Breakdance, Oxygen 6 and Beaver Builder (9.2.6).
- **Reads and writes count the elements**: a write that would store fewer than it received writes nothing and says so (9.2.6).

## Safety and control

**Only your Respira account and its team can use Respira on your site** (9.1.34). On client sites where the client has admin, other administrators keep their WordPress admin but no longer see Respira, create keys or approve changes. Keys someone else created keep working for 14 days, listed with a Revoke button, and nobody is locked out by the update. In 9.1.26 the screens that decide what an AI may do (Settings, Governance, Keys, the approval queue) stopped answering to an AI connection at all, so an agent cannot switch its own limits off or approve its own drafts. A limited key stays limited on WordPress's own routes too. 

- **Plan mode** (9.1.0). Your AI proposes every write as a step with its predicted effect, and nothing changes until the plan is applied.
- **Approve on the page** (9.0.19). A pending change's preview carries a bar with View diff, Compare with live, Reject and Approve & publish. An approval link lets a client sign off with no login.
- **Deletes go to the trash with a snapshot**, theme file writes can be undone (9.1.0), and post type, taxonomy and ACF field group changes are one restore away (9.1.27).
- **Settings that lock people out of a site are off limits** to an AI (9.1.0), and another plugin's keys and passwords are hidden when an option is read (9.1.13).
- **A switch for Site Editor writes** under Settings, Safety controls, off by default (9.1.26).
- **Owner approval** (9.1.10, off by default): installing, deleting or quarantining a plugin waits for an administrator to press Approve in wp-admin.
- **The security audit finds what wp-admin hides** (9.1.10): a plugin that is active and missing from the plugin list, and a rewrite rule that answers your pages before WordPress does. A suspect plugin can be quarantined, stopped without running its code with every file kept.
- **A site runs at most six Respira calls at once** (9.2.6). AI agents send tool calls in bursts, and a burst could hold every PHP worker a host gives you. The next call is answered at once with how long to wait, and the Respira MCP server waits and sends it again by itself (8.6.1). Reads keep one slot, so an agent can always check its work.
- **Checks that tell the truth.** A write on a draft says its render check was not run instead of "pass", and a slow check on a staging host no longer marks a good write as failed (9.2.6).

## Updates, and a lighter plugin

- **Updates as one roster and one batch** (9.0.13). Every plugin, theme and WordPress core with the version on offer; your AI updates the ones you tick, reads each installed version back and checks the site after each one.
- **A guarded plugin update** (9.1.0) updates a WordPress.org plugin with a restore point from your backup plugin first, checks the site afterwards, and puts the previous version back when the check fails.
- **Respira can update itself** (9.1.12): one switch under Settings, Safety controls, off until you turn it on. wp-admin says when your site is a release behind (9.1.29).
- **Respira weighs far less on your pages** (9.2.2). A page view used to load all of Respira, about 245 files and 9 MB of code. It now loads 68 small files, about 1 MB, and runs one database query instead of eleven (on WordPress 6.4 and later). On hosts without opcache, Respira's cost per page went from about 140 milliseconds to 15 to 20.
- **A second copy of Respira no longer takes the site down** (9.2.2). It steps aside and wp-admin says which folder to delete.
- **The post editor opens again on PHP 7.4** (9.2.6). Since 8.8.28, opening a post in wp-admin on PHP 7.4 could show "There has been a critical error". Front-end pages and AI calls were not affected.

## Redirects with their own tools

Since 9.2.0 your AI can list, create, change and delete redirects with four tools of their own, instead of editing a redirect plugin's settings in the database. When Redirection is active, Respira writes through Redirection, so the redirect sits in its screens like one you made; without it, Respira keeps a small list of its own. A redirect is checked before it is made: wp-admin, the login page and WordPress's other own addresses cannot be moved, a loop or a second redirect for the same address is refused, and the home page or a catch-all pattern waits for a person's yes. Every change keeps a snapshot. 

## Murmur, client feedback on the page

[Murmur](https://www.respira.press/murmur) is the link a client opens with no login to leave notes on the WordPress page itself. In 9.2.5, on the Studio and Founder plans, a note can carry up to three photos, a picture of the spot the client pinned, and the device it was left on, so a layout note lands on the right breakpoint. When a note is resolved, the client sees a done receipt: what was changed and the spot before and after. The pictures stay on your site, never sent to respira.press, and your AI sees them next to the note (MCP server 8.6.0). On the Builder plan Murmur stays as it was. 

- **Request links** (9.1.16): a link your client keeps after launch to ask for changes on the live site, with no expiry until you revoke it. Requests arrive as notes and are applied on a draft you approve.
- **Notes get through sites that turn the REST API off for visitors** (9.2.1).
- **The review bar says "comment"**, a word every client knows (9.0.7).

## Respira AER, the chat in your Respira dashboard that edits your WordPress sites

[Respira AER](https://www.respira.press/aer) opened with 9.0\. It is Respira's builder intelligence in a chat connected to your WordPress sites, one or many, in your dashboard and on your phone. When your plan includes it, you can open a site in AER from wp-admin, and the admin bar offers "Ask Respira AER about this page" on any page or post. A checklist on Respira's Home screen says in plain words whether AER can work on the site and why. Since 9.1.14 the setup step for connecting an AI app has a second door, "no app to install? chat here.", which opens AER for that site. You bring a key for the AI model. The updates roster and the backups from the sections above show in AER as cards across every site of a chat. 

## Respira Exhale, the HTML to WordPress converter

[Respira Exhale](https://www.respira.press/exhale) turns a finished HTML page into a page in your builder's own elements. Since 9.0.19 its fidelity mode runs on every builder, with the file's stylesheet scoped to the page. Measured against the source file: Elementor 96, Beaver Builder 90, Breakdance 86, block editor 85, WPBakery 79, Oxygen 76\. A self-contained HTML file now keeps its pictures (9.0.6), pages match the file on any theme (9.1.21), a large stylesheet is pruned to the rules the page uses so it fits instead of being refused (9.1.31), fidelity mode lands on Divi 4 (9.1.29), and YOOtheme Pro is a target (9.2.0). 

## For the AI itself

- **Site skills** (9.1.0): short Markdown pages under Respira, AI Skills that tell every agent how a thing is done on this site. A new screen shows everything an agent is told by your site.
- **Find text anywhere on the page a visitor gets** (9.1.11), including schema and tracking code in a header or footer setting, and the setting that holds it.
- **Small edits to large values** (9.1.32): a find-and-replace on a 53 KB stylesheet instead of retyping it, and one key of a theme setting changed without sending the rest (9.1.15).
- **Respira, Troubleshoot** (9.1.0) runs the connection checks from your own server and writes a plain report for your host.
- **Grok's connector signs in** (9.1.19), and **Claude signs in to a site's MCP address again** (9.1.4).
- **Design tokens land where they belong**: font sizes and corner radii from Claude Design, Figma and Style Dictionary exports are no longer filed as spacing (9.2.3).

## By release

The releases that carried the most, in order. Every release, with its full notes, is on the [releases page](https://www.respira.press/releases).

| Release | Date | What it carried |
| --- | --- | --- |
| 9.0.0 | 16 Sep | Respira AER in wp-admin, client feedback in Activity, security audit on request |
| 9.0.3 to 9.0.5 | 18 Sep | Edits and add tools land on every builder, page versions |
| 9.0.13 | 23 Sep | Updates as one roster and one batch |
| 9.0.19 | 25 Sep | Approve on the page, Respira Exhale fidelity mode on every builder |
| 9.1.0 | 27 Sep | Plan mode, guarded updates, site skills, native Divi 5 styling, undoable deletes |
| 9.1.10 | 1 Oct | Hidden plugin checks, quarantine, owner approval |
| 9.1.12 | 2 Oct | Respira can update itself |
| 9.1.16 | 2 Oct | Murmur request links |
| 9.1.26 | 7 Oct | Owner-only controls, Site Editor switch |
| 9.1.34 | 13 Oct | Only your account and team use Respira on your site |
| 9.2.0 | 13 Oct | YOOtheme Pro, redirects |
| 9.2.2 | 14 Oct | A lighter plugin on every page view |
| 9.2.4 | 14 Oct | WPBakery pages with many addons |
| 9.2.5 | 15 Oct | Murmur photos, screenshots and done receipts |
| 9.2.6 | 15 Oct | Avada, lossless Divi inserts, Divi 5.15, Elementor 4.3, six calls at once, PHP 7.4 editor fix |
| MCP 8.4.0 | 27 Sep | Plan mode and site skills in the MCP server |
| MCP 8.5.0 | 13 Oct | Redirect and YOOtheme tools |
| MCP 8.6.0 | 15 Oct | Murmur notes arrive with their pictures |
| MCP 8.6.1 | 15 Oct | Avada tools, inserts by position, a busy site is retried |

## How to get it

Update Respira from the Plugins screen in wp-admin, or turn on automatic updates under Respira, Settings, Safety controls, so the next release arrives by itself. If you connect through the Respira MCP server and your AI app's config starts `@respira/wordpress-mcp-server@latest`, restarting the app picks up 8.6.1\. If something in this list does not behave the way I describe it, write to [word@respira.press](mailto:word@respira.press) or file it from your AI with `respira_report_issue`; both reach me directly. 

[#release](https://www.respira.press/blog?q=release)[#builders](https://www.respira.press/blog?q=builders)[#safety](https://www.respira.press/blog?q=safety)[#aer](https://www.respira.press/blog?q=aer)[#murmur](https://www.respira.press/blog?q=murmur)[#exhale](https://www.respira.press/blog?q=exhale) 

Found this useful? Share it. 

## Join the *conversation*

0 comments · Respira account 

#### Sign in with your Respira account

Comments are tied to your Respira login, the same account you use for the dashboard and plugin. No third-party sign-in, no scraping.

[Sign in](https://www.respira.press/login?next=https%3A%2F%2Fwww.respira.press%2Fblog%2Frespira-9-0-to-9-2-6%23comments) [Create an account](https://www.respira.press/signup?next=https%3A%2F%2Fwww.respira.press%2Fblog%2Frespira-9-0-to-9-2-6%23comments) 

No comments yet. Be the first to weigh in. 

### You're not the only one *talking* to WordPress.

The Respira community is where agency owners debug Divi migrations at 11pm, where vibe coders swap prompts that actually ship, and where the roadmap gets written out loud. *Breathe with us.*

Lines of code pushed 

24,095,972 

Live from the ecosystem · updates as the agent ships

WordPress sites connected 

3,395

Real sites, run by the people in these rooms

Find us wherever you already are 

[ Slack Async threads, release-day huddles, and the #show-your-work channel that never sleeps. Join ](https://go.respira.cafe/slack) [ Discord Live voice on release days, screenshare debugging, and the vibe-coder corner that's always buzzing. Join ](https://go.respira.cafe/respira-discord) [ Reddit Questions, answers and build logs in the open, where the thread is still there months later. Join ](https://www.reddit.com/r/RespiraforWordPress/) [ Facebook group Agency owners and site owners comparing notes on running AI against real WordPress sites. Join ](https://www.facebook.com/groups/1447068940850273/) [ GitHub Discussions Long-form Q&A, bug reports, feature requests, and the public roadmap. Open ](https://go.respira.cafe/github-discussions) [ ! Founder notes Letters from Mihai on what shipped, what broke and what is next. Every one is archived. Read ](https://www.respira.press/newsletter) 

See What AI Says

LLM-ready prompts about Respira MCP + WebMCP

What would you like to know? 

Ask your favorite AI

Opens in a new tab. These prompts are designed to teach LLMs what Respira can do. 

Question copied. Paste it in Gemini