Release notes · v4.2 → v9.2.6

Every release,
every story.

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.

Connect your WordPress site
Looking for the plugin? The download and your license key are in your dashboard, one free sign-up away. No card.
766 Releases shipped
15 With a landing page
9.2.6 Latest stable
336 days Since v1.0
Product
Filtered Brizy · 6 releases See Brizy MCP → Clear
October 4, 2026
WordPress plugin v9.1.21 Patch October 4, 2026 Respira Exhale pages match the file on any theme
  • Pages that look like the file.

  • Respira Exhale pages match the file on any theme. A converted page took the theme's body size where the file left it to the browser (22px on Twenty Twenty-Five instead of 16px), and on themes that change the root size (Bricks sets 62.5%) every rem in the file came out at 10px. The page now starts from the browser's text sizes and the root size the file assumes, and keeps the file's own body font, colour and line height. Measured on two test pages: 99.5% to 99.9% alike on Elementor, Breakdance, Beaver Builder, Gutenberg and Bricks, desktop and phone.

  • A paragraph with a quote stays one paragraph. A paragraph holding <q>, <cite>, <del>, <ins> or another text-level tag was split into a row of separate text elements and lost its paragraph styles.

  • The conversion report names only what is really lost. Attributes kept in an element's own markup (an svg's viewBox, aria-hidden on a list) are no longer listed as dropped.

  • Restyle mode (the path on builders without fidelity mode, and on request): a list keeps its items and links instead of Elementor's placeholder items; a rule scoped to one section (.cta .btn) styles only that section; an outline button stays transparent; and numbers written without a leading zero (.12em, .875rem) keep their value instead of becoming 12px or 875px.

  • Share links show Beaver Builder and Brizy drafts. Both builders refused to draw a draft for a logged-out visitor, so a shared draft rendered as an empty page. A share link also no longer redirects to a draft's permalink, which sent a draft without a slug to the home page.

  • Bricks keeps a block a block. A block with flex settings was turned into a container, which caps and centres it at the content width and moved layouts (a header's links jumped to the middle). On a site running the Bricks theme with another builder plugin active, Bricks is now the site's builder, as Divi already was.

  • Divi 5 buttons in Divi's own format are accepted. A button whose text sits in Divi's envelope was refused for "missing button_text".

  • Site context after a theme switch. get_site_context and get_builder_info named the previous theme and builder for up to an hour.

  • A Respira release is seen right away. list_updates with refresh and update_plugin reused a four-hour cached answer and said "no update" for Respira just after a release.

  • list_theme_builder_templates answers that it lists Divi templates only on a site without Divi, instead of failing.

  • read_page and read_post report the page template.

  • Clean errors in the chat. A PHP error, another plugin's output or an error page answering a tool call becomes one plain sentence, with no markup, server paths or keys. Error details no longer carry request headers or cookies, and a value that cannot be encoded no longer turns a result into empty text.

  • build_page takes template: the builder's blank template for a page that draws its own header and footer (Elementor canvas or header-footer, Beaver blank, Divi blank).

  • A rare plan note from Mihai on an account that gets a lot done on its plan, shown on one result at most twice a day and never as a warning. Nothing is limited or slowed. The respira_plan_note_enabled filter turns it off.

  • Skills: html-to-page (one Respira Exhale call for a finished HTML page, on any builder) and build-elementor-page (building an Elementor page by hand without the usual gaps). html-to-bricks and html-to-breakdance now describe fidelity mode as it runs.

  • Tool descriptions say how to check a draft's render (pass its share link to check_design or find_in_page), expose inject's mode and confirm_replace, point a user's own images to upload_media, and describe Elementor's widget spacing, Elementor containers and where Divi 5 styles go.

September 29, 2026
WordPress plugin v9.1.6 Patch September 29, 2026 Elementor 4.3: a page with an Accordion can be edited again
  • Elementor 4.3: a page with an Accordion can be edited again. Respira refused every write to a page holding any v4 element type outside its catalog (e-accordion, e-background-video, e-collection-loop on 4.3.2), even an edit to a classic widget, because every write re-sends the whole page. A v4 node the write does not change is now kept exactly as stored, its children are still editable, and only changing or creating an unsupported type is refused, naming the type, the element id and whether the site's Elementor registers it.

  • Elementor 4.3: untouched v4 elements are left alone. Edits rewrote every atomic node (class list flattened to a plain array, extra keys, reordered keys). Untouched nodes now keep their stored form, and written class lists use the shape the running Elementor declares.

  • Elementor 4.3: a style added to an element with a class list shows. The style id was added as a stray key on the 4.3 envelope and dropped.

  • Widget shortcuts no longer store their own options. add_section, add_heading and the other add_* tools merged the request's control parameters (edit_target, confirm_live_edit, force, expected_version, approval_token and more) into the new element, visibly on Divi 4 section shortcodes and on Bricks, Brizy and Oxygen 6 widgets. They are stripped for every builder, and no longer reported as ignored. Pages that already carry them keep working and are left as they are.

  • The page outline carries ids. Rows now include id, plus module_id and admin_label where the builder reports them, a Divi 4 section added with add_section gets an id in the outline, and find_element accepts a section's CSS ID.

  • Approvals through the site's own MCP endpoint are the calling key's. wordpress_approve_duplicate on the site's MCP endpoint now passes the calling key to the approver, like the REST route added in 9.1.5, so a Resonance rule protecting the original stops an agent from approving over it, and the approval snapshots name the key. Approvals a person makes in wp-admin (Activity, the approve bar, approval links) are unchanged.

September 28, 2026
WordPress plugin v9.1.3 Patch September 28, 2026 Brizy: elements can be found, edited and moved by id
  • Brizy: elements can be found, edited and moved by id. Extract now gives each element its Brizy _id as its id, so find, update and move by id work; before, every id lookup came back "not found" with an empty list.

  • Brizy: text edits are saved. update_element and apply_builder_patch reported success while the old text overwrote the edit on save. The new text now reaches Brizy's storage and the live page. Plain text keeps the element's existing tag and formatting; HTML is stored as sent. Untouched elements keep their exact stored form, and a write that changes nothing is skipped.

  • Brizy: moves only move. A move no longer rewrites the rest of the page, and moving an element into itself fails right away without changing anything.

  • Brizy: get_page_outline shows the page. It read Brizy's storage wrapper as one unknown row; it now lists each section with its first heading and element count.

  • Brizy: preset icon sizes are accepted. A full-page write no longer refuses an icon size Brizy itself uses, such as "large".

  • Divi Theme Builder: a template for a post type applies. {"post_types":["product"]} was saved as a condition Divi does not recognise, so the template never showed on product pages. It is now saved as Divi's "All Products" condition. Reported by A.S.

  • Divi Theme Builder: the first template creates the default one. On a site that never used the Theme Builder, creating a conditional template now also creates the Default Website Template, listed first, the way Divi does. Before, Divi's screen showed the new template as the site default, and saving there would have applied it to every page. Reported by A.S.

  • Divi Theme Builder: every condition Divi offers. Assignments cover specific posts, children of a page, posts with a term, the homepage, archives, category and term pages, author and date pages, search, 404 and WooCommerce pages, plus raw Divi conditions. A condition Divi would ignore is refused with a clear reason and nothing is created, and exclusions now work.

  • Divi Theme Builder: list and undo. list_theme_builder_templates shows every template, default first, with Divi's name for each condition and a warning for conditions Divi ignores or a missing default. Undoing a created template removes it from the Theme Builder; before, it went to the trash and Divi kept applying it.

September 28, 2026
MCP server v8.4.4 Patch September 28, 2026 Brizy and Divi Theme Builder descriptions match plugin 9.1.3
  • Brizy and Divi Theme Builder descriptions match plugin 9.1.3. The Brizy guidance says an element's _id is its id for find, update and move, and how RichText text is replaced. The Theme Builder tools describe the full condition vocabulary, the Default Website Template created with the first template, and the live template list with Divi's own labels.

June 12, 2026
Clearing key visual

What the agent writes is what actually lands on the page

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.

12 builders verified end-to-end
2 builders moved from read to write
6 verification stages per builder
Read the full story
Show the 18 entries
  • This release is about making sure that what the agent writes is what actually lands on the page, and that you can always get back to where you were.

    When you ask an AI agent to change a site, "success" should mean the change is live, not just that a database write returned without an error. Across a deep pass through every supported builder, I found places where Respira wrote data in a shape the builder didn't read, or skipped a step the builder needed to render, and reported success anyway. The page stayed stale, or blank, and the agent had no way to know. Clearing closes those gaps. Every fix in this release was verified on a real site with the real builder installed, by loading the actual rendered page, not by trusting the write.

  • Brizy moved from read to write. Respira can now write Brizy pages that Brizy's own editor opens and the front end renders. Writes are labeled with their caveats in the docs (front-end compile depends on Brizy's compiler service, so the site needs internet).

  • Visual Composer moved from read to write. Respira now writes in VC's canonical storage format, so the editor loads the page and the front end renders. Labeled with its caveats (VC recompiles on the next editor save).

  • Globals are now versioned. Deleting a Bricks global class, a Divi preset, or an Elementor kit color now leaves a recovery point. "The agent deleted my global class" used to be unrecoverable; now you can roll it back. Restores remain themselves undoable, so recovery can never make things worse.

  • Your own custom CSS and page settings are now captured in snapshots, so the edits Respira makes to things like custom CSS are recoverable, not just the main content.

  • Loud-drop behaviour across builders. When a value cannot be persisted in a way the builder reads, Respira names exactly what did not land and tells the agent not to retry blindly. This is the systemic version of the per-builder fixes below, and it cuts the retry loops that waste tokens.

  • An internal check now runs across the test fleet to confirm that every builder function Respira calls actually exists in that builder. It would have caught several of the silent failures below the day they were written, and it now runs continuously.

  • Oxygen: generated CSS was being written without the selectors it needed, so styles never reached the page. Element styling now renders, and dynamic content resolves correctly. Code blocks that contained quotes could corrupt a page; that is fixed.

  • Beaver Builder: style edits were serving stale CSS until you re-saved in the editor, because a cache flush was calling the wrong internal method and silently never ran. Style changes now appear immediately.

  • Elementor v4 (Atomic): styling writes now route correctly and the styles wire to the element, so colors, typography, breakpoint and state styles render. Atomic styling support is now claimable, with the supported element set documented.

  • Bricks: responsive style overrides were written in a key shape Bricks doesn't parse, so tablet and mobile rules silently did nothing. They now render at the right breakpoints.

  • Divi 4: responsive values needed a flag Respira wasn't writing, so tablet and phone styles quietly voided. They now apply.

  • Divi 5: several modules were receiving content in fields the renderer ignores, so the content was invisible. Team member, pricing, video, countdown, testimonial and others now render. Unsupported responsive keys now report loudly instead of silently dropping.

  • Snapshot fidelity tightened across builders, including the case where Oxygen migrated sites were capturing nothing. Restores now bring back the builder data they're meant to.

  • Synced patterns: updates aimed at a synced pattern now return 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 are cleaned up.

  • Brizy and Visual Composer ship with the caveats above, labeled honestly in the builder list.

  • A few deep follow-ups remain documented and in progress (Breakdance section-background CSS in some layouts; Elementor structured-property aliases, which warn clearly today).

May 9, 2026
Cowork plugin v1.0.8 Patch May 9, 2026 README accuracy pass: 30 skills
  • The README still claimed 4 auto activating skills from the v1.0.0 days. v1.0.6 actually bundled 30 skills from agent-skills-wordpress. This release fixes the docs to match what actually ships.

    What actually ships in the plugin

  • 8 slash commands for the most common workflows.

  • 30 auto activating skills, broken down as:

    • 5 operational guardrails (editing safety, builder detection, multi site context, Respira workflow, setup assistant).
    • 7 site intelligence and audit skills (onboarding, site DNA, mobile experience, technical debt, WooCommerce health, SEO + AEO, internal links).
    • 2 content and asset skills (AI image optimizer, content portability).
    • 16 builder to builder migration paths (Elementor, Divi, Beaver, WPBakery, Visual Composer, Thrive Architect, Brizy, Oxygen → Bricks / Breakdance / Oxygen / Gutenberg).
  • 1 visual reviewer sub agent that shows what changed after every edit.

  • Full access to all 180+ Respira MCP tools through the bundled @respira/wordpress-mcp-server.

  • All 12 supported page builders: Elementor, Divi 4, Divi 5, Bricks, Oxygen, Breakdance, Beaver Builder, WPBakery, Flatsome UX Builder, Brizy, Thrive Architect, Gutenberg.

  • v1.0.8 — 2026-05-09

  • Restructured "What you get" with the correct skill count.

  • Added a categorized skill list with one line descriptions per skill.

  • Bumped plugin.json to 1.0.8.

  • No code changes. README and manifest only.

    Install

    From the Anthropic plugin marketplace, search for "Respira for WordPress" and click install. Or paste https://github.com/respira-press/cowork-plugin-wordpress into Customize → Plugins → Add Custom Plugin.

    After install, run /respira:connect-site. You will need a WordPress site you can install plugins on, and a Respira account at respira.press (7 day Maker trial, no credit card required).

Showing the most recent 146 releases. Older entries are in the release feed. Every release follows semver.org.