A Divi Library item made of one module can be edited
- fix A Divi Library item made of one module can be edited. A library item whose whole
- fix apply_builder_patch takes the identifier shape find_element gives you. An agent
Account
Explore
Release notes · v4.2 → v8.9.0
A single timeline. Every version Respira has shipped, with the stories behind the ones that mattered. Click into any release tagged story for the full write-up.
A Divi Library item made of one module can be edited
Fidelity mode for HTML conversion, on Divi 5 and Bricks
An HTML page converted to Divi keeps its stylesheet and its classes
A refused connect now says why
A Respira outage was reported as a fault on your site
Divi 5 button text colour was written somewhere Divi never reads
updates.unset did nothing on Divi 4 and said it worked
Elementor atomic writes deleted the element's children
The advice for editing one of two identical elements did not work
Specialty sections keep their layout
A ::selection rule no longer paints the whole page
The Divi Library, as tools
wordpress_save_divi_library_item and wordpress_apply_divi_library_item
A Divi 5 page built by Respira can finally use Divi's own styling engine
Divi 5 presets are first-class tools
The phantom "4KB limit" is gone
A post's publish date can be corrected after the fact
WebMCP site tools work now
A row nested inside a column was deleted by any write that rebuilt the page
One edit to one heading on an Oxygen page deleted the body copy of every rich text element on that page
A write receipt said nothing had changed while the Yoast title it had just saved sat in the database
151 of 163 native abilities directed an agent straight into a 404
apply_builder_patch and update_element's unset operation had no valid shape a strict client could use
Respira spoke sixteen page builders. As of 8.0 it also speaks WordPress's own Site Editor: block templates, synced patterns, block navigation and design tokens, readable and writable on the same safety contract as everything else. A navigation link changes by exact block path, not by rewriting the menu. A pattern is created, read back through WordPress, render-checked, then placed by reference. Structural edits can wait for your approval, and every write leaves a snapshot, a normalised diff and a server-render result. The WooCommerce add-on goes to 4.0 alongside it, and its storefront tools now try the native block path first, so a shop built in the Site Editor stops being a place where the store tools quietly go dark. Building all of that meant auditing the safety layer itself, which turned up two places where the safety mechanism was the thing doing the damage: a Divi serialiser rule written for brand-new pages was firing on every write path, and undoing a Theme Builder create could trash a template the agent never created. Both fixed, both pinned by permanent tests.
The setup and connection screens were rebuilt around one source of truth. You link a site once, then watch the moment your first agent reaches it: the screen updates on its own and names what just happened, for example "connected. Claude just ran update_page on page #42". The plugin, the dashboard and your agent now read the same connection state, so they always agree on whether a site is connected and what access it has. One-click installs (the Desktop app, Cursor, Cowork) lead the way in, with browser sign-in still there for ChatGPT and claude.ai. Sites also arrive in the dashboard with their real WordPress title instead of a bare URL, which matters the moment you run more than one. And seven builder fixes land across Bricks, Divi, Elementor 4.x and Gutenberg.
A deep pass through every supported builder, closing the gaps where a write reported success but the page stayed stale or blank. Styling now lands on Oxygen, Beaver Builder, Elementor v4 Atomic, Bricks, Divi 4 and Divi 5. Brizy and Visual Composer move from read to write, with their caveats stated. Recovery gets deeper: custom CSS and page settings are captured, and globals are versioned, so deleting a Bricks global class, a Divi preset, or an Elementor kit color leaves a recovery point. And when something cannot be persisted in a way the builder reads, Respira says exactly what did not land instead of reporting success. Every fix verified on a real site by loading the actual rendered page.
README accuracy pass: 30 skills
Flatsome UX Builder joins as builder #12. 15 new WooCommerce Commerce tools with storefront design intelligence. Context-aware MCP tool filtering reduces tools in context by ~40. Three coordinated releases.
65 new tools. Element-level editing across every supported builder, build_page declarative page creation, HTML-to-builder conversion, stock-image search, tool governance, and dynamic schemas for 12 builders.