The dangerous failure is the one that reports success.
When an AI agent edits a site, the failure that throws an error is the easy one. The dangerous one reports success while the page stays stale or blank, because the data was written in a shape the builder does not read. The agent has no way to know. It retries. The page stays wrong, and you find out from a visitor.
Clearing is a deep pass through the supported builders, down to each builder's own internals, to find and close those gaps. Where Respira wrote data the builder ignored, or skipped a step the builder needed to render, the write path was fixed. Where a value genuinely cannot land, Respira now says so out loud instead of pretending.
Each fix was verified by loading the real rendered page on a real install with the real builder active, not by trusting the success message. That is the whole release in one sentence.
What changed, grouped by what you feel.
Three groups of outcomes, not a flat changelog. The full per-builder detail lives on the plugin page.
Styling now lands
Fixes for places where a style write succeeded while the page stayed the same.
These were the quiet failures. The write returned fine, the data sat in the database, and the page kept rendering the old look because the builder reads styles from a different shape or a different step. Each one below is now verified against the rendered page.
- Oxygen: element styling now renders on the page, and dynamic content resolves. it did not before.
- Beaver Builder: style edits appear immediately instead of waiting for a re-save in the editor.
- Elementor v4 (Atomic): colors, typography, breakpoint and state styles now wire to the element and render. the supported element set is documented.
- Bricks: tablet and mobile style overrides now apply at the right breakpoints instead of silently doing nothing.
- Divi 4: tablet and phone styles now apply instead of quietly voiding.
- Divi 5: modules that were receiving content in fields the renderer ignores now render it. team member, pricing, video, countdown, testimonial and others.
Two builders moved from read to write
Brizy and Visual Composer, shipped with their caveats stated.
Both were read-only before this release. Both now take writes that their own editors open and their front ends render, verified on real installs.
- Brizy: Respira writes pages the Brizy editor opens and the front end renders. front-end compile depends on Brizy’s cloud compiler service, so the site needs internet.
- Visual Composer: Respira writes in VC’s canonical storage format. the editor loads the page, the front end renders, and VC recompiles on the next editor save.
Writes fail loudly, not silently
When something cannot land, Respira says so by name.
When a value cannot be persisted in a shape the builder reads, Respira now names exactly what did not land and tells the agent not to retry blindly. That is what cuts the retry loops that waste your tokens.
- Synced patterns: an update aimed at a synced pattern now returns a clear message naming the actual pattern to edit, instead of silently doing nothing.
- WPBakery: raw HTML and unknown shortcode types are now encoded and reported correctly instead of rendering as garbage or literal brackets.
- Gutenberg: buttons now write canonical markup so they render styled, and stale helper attributes get cleaned up.
Recovery got deeper.
More of your site comes back.
recovery is the heart of Respira, and this release widened what it brings back.
Recovery covers the content and builder data Respira writes, with the documented exceptions listed on the builders page. This release pushed that coverage past the main content.
- your own custom CSS and page settings are now captured, so the edits Respira makes there are recoverable, not just the main content.
- snapshot fidelity was tightened across builders, including a case where some Oxygen migrated sites were capturing nothing.
- globals are now versioned. deleting a Bricks global class, a Divi preset, or an Elementor kit color leaves a recovery point. "the agent deleted my global class" used to be unrecoverable. now you can roll it back.
- restores are themselves undoable, so a recovery step has its own way back.
- Bricks global classes
- Divi presets
- Elementor kit colors
- your custom CSS
- page settings
Proven on real sites, not success messages.
Behind this release is a test fleet: one real WordPress install per builder, with the real builder active, and one command that re-tests the whole product across them. Twelve builder legs passed the gate end-to-end. A new internal check also confirms that the builder functions Respira calls exist in that builder's current version, continuously, so this class of silent failure gets caught the day it is written.
- G.1 BuildBuilds a page with that builder’s own elements on a real install with the real builder active.
- G.2 Live updateEdits an existing page and confirms the new value persisted where the builder actually reads it.
- G.3 Loud refusalAsks for an element type the builder does not have and expects a refusal that names it, not a quiet success.
- G.4 RollbackRestores the page and compares the stored builder data byte for byte on that leg.
- G.5 Rendered pageLoads the actual front-end page and checks the change is visibly there.
The edges, stated plainly.
A release that is honest about its edges is one you can trust with a live site. The list is short this time because most of the previous limits closed. The full per-builder detail, caveats included, lives on the plugin page.
The builders page and the full diff.
Try 7.4 on a site you maintain.
i named this one Clearing because that is what it felt like, walking out of the fog between "the write worked" and "the page changed". if you put an agent on a live site, this is the release i would want under it.
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.
