Tool calls that worked are no longer recorded as unfinished
- fix Tool calls that worked are no longer recorded as unfinished. When an assistant called
- change Three error messages now tell the assistant what to do next. An unknown post type
Account
Explore
Release notes · v4.2 → v9.0.9
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.
Tool calls that worked are no longer recorded as unfinished
A copy of a page converted in fidelity mode keeps its design
Review links say "comment"
and use one of the site ids it
a note. Tool names and parameters are
Claude Desktop's Cowork and Code sessions could not start Respira
diagnose_connection says when a host blocks ChatGPT
Comments, not murmurs or notes
A judge your model can call
A step that asks for too many tool calls no longer ends the run
A self-contained HTML file keeps its pictures
An edit reaches the page on every builder
The add_* tools render on Elementor
The add_* tools render on Bricks
A write can name the page version it was based on
A check after every content change
A Gutenberg container no longer saves empty when its children arrive under an unfamiliar word
diagnose_connection says when the host answers /.well-known/ itself
Murmur's element outline stays on the element after scrolling
Respira AER is the agent workspace in the Respira dashboard. Respira for WordPress 9.0 is the runtime installed on each site: it gives AER secure access to the site's builders, memory, approvals, snapshots and receipts without putting another chat inside wp-admin. Across 8.x the plugin learned five things one release at a time. It remembers a site and enforces its rules. It knows the site's art direction and checks work against it. It lets clients talk back through Murmur. It lands a designed page as native builder output. And it proves what change runs did. Version 9.0 brings those parts together and adds an Open in Respira AER button plus a Ready for Respira AER checklist. Murmur links and client notes, spoken ones included, show up where you work. Site memory and Art Direction are on screen next to the pages they govern. The security audit gives the same answer whether you or your agent run it from an app connected over MCP, from Respira AER or from the site's own endpoint: the known vulnerabilities that match its plugins, themes and WordPress version, checked against Wordfence Intelligence, each with the version that fixes it, and never a clean report when that database cannot be reached. Change runs leave receipts, and reversible content work keeps its snapshot or undo.
Divi 5 duplicates can be edited independently
Duplicate Page understands the page ID names agents already use
An approval now covers exactly what was approved
Every review link is signed
Themes are checked for known vulnerabilities too
Your clients can speak their murmur
A readiness checklist per site
Custom CSS in a page's settings now needs your approval
Murmur review links
Murmur: seven tools for the review links your clients talk back
The post update tools say they take categories, tags and taxonomies
A Divi Library item made of one module can be edited
Fidelity mode for HTML conversion, on Divi 5 and Bricks
Share links with a lifetime you choose
apply_builder_patch accepts find_element's identifier shapes
Hosts that turn PUT, PATCH and DELETE into reads
wordpress_create_share_link
An HTML page converted to Divi keeps its stylesheet and its classes
A refused connect now says why
The public key check was an oracle, and an amplifier
A Respira outage was reported as a fault on your site
The connection diagnostic now reports why your tools are missing
One failed handshake made a site look broken for the rest of the session
Builder-aware tool routing
Revoking an API key did not reliably revoke it
Respira could adopt another vendor's AI agent as the user it writes as
Text a stranger typed into your checkout no longer reaches your AI as-is
Settings told almost everyone that white-label does not exist yet
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
Creating a translation rewrote the other translations in German
Uploading a JPEG never worked
The advice for editing one of two identical elements did not work
A save could arrive at WordPress as a read, and answer as one
A plain anchor no longer converts into a button
Editing any element on a Flatsome page was refused
The accessibility scan was inventing findings
The check that would have told that site owner why he got
A hidden administrator that hides its own age is now found
Modules from third-party builders answer for their own settings
Respira checks what a write did to the rest of the page
Specialty sections keep their layout
A ::selection rule no longer paints the whole page
An approval-gated tool asked for an argument it never advertised
build_page wrote attribute names Flatsome does not read
Scoped design tokens resolve per element
The other half of the Kadence
Kadence blocks keep their content when you edit something else
Shorthand CSS now maps
Editing one block no longer empties the headings, lists and images around it
The data-respira annotation vocabulary
The Divi Library, as tools
wordpress_save_divi_library_item and wordpress_apply_divi_library_item
41 skills, snapshot-safe migrations, corrected install docs
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
Respira's REST responses are no longer printed twice
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.
Released 2026-07-16.
Released 2026-07-16.
Released 2026-07-16.
Released 2026-07-16.
Released 2026-07-16.
Released 2026-07-16. Agent-Ready Commerce: AI assistants can now find, read, and sell from your store. 79 MCP tools (up from 56).
Released 2026-07-16.
Released 2026-07-16. The full commerce surface: 56 MCP tools (up from 21). Completes the v3.0 rollout that began in June: the release was built and published then, but the update was never offered to customer sites, which kept stores on the
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.
A React-first plugin admin built around live telemetry: a bridge view of agent ↔ Respira ↔ site, real cards driven by eleven new REST endpoints, and a personalised greeting. A public add-on SDK ships so third-party plugin authors can register their own MCP abilities. And a new MCP tool, generate_activity_report, turns this site's audit log into a structured report your own agent shapes into prose — six framings cover the use cases customers actually have, time-saved math is calibrated to conservative per-tool baselines, and Respira never writes a single line of prose itself.
Released 2026-05-27.
wp.org review fixes
WordPress.org Plugin Directory submission
hardening pass
first public release
Zero-touch Cowork onboarding (Open in Cowork)
unified ~/.respira/config.json flow + connect-site rewrite
audience-first README rewrite
README accuracy pass: 30 skills
README hero KV + signup copy accuracy
The biggest release since v5. Every builder adapter promoted in lockstep. Five cross-cutting Phase A invariants every adapter now inherits — render-validation gate, universal write-trace, Variables CRUD shape, source-driven catalog auto-scan, per-property typed validators — plus Phase B slices per builder that close the family-bug arcs surfaced across v6.10.x. 1076 standalone test assertions across 27 alpha cycles, zero failures.
The release I should have shipped weeks ago. Closes 14 customer-reported bugs across 5 named trial threads and all 7 open public GitHub issues, plus 5 cross-cutting audits — JSON post-meta unicode safety across every adapter, MCP server tool-schema audit, duplicator kses bypass, schema endpoints anon-readable, render-trace fields on every write. New respira_diagnose_connection tool surfaces edge-layer interception so REST returning homepage HTML instead of JSON stops being opaque.
Self-updater fatal on every WP cron tick. class-updater.php:104 called \Respira_License::get_license_key() which has never existed on the core License class — every site that activated the add-on threw Uncaught Error: Call to undefined meth
drop keytar, fix whoami after login, unstick terminal, warm welcome
fix 307 redirect breaking respira auth login
54 ACF tools covering field reads and writes, field-group management, ACF Pro repeaters, flexible content, galleries, options pages, relationships, and bulk updates. Every write snapshot-backed and dry-run previewable. Works on approximately 2 million WordPress sites that use ACF today.
per-package READMEs on npm
Foundation release
The deepest Oxygen Builder MCP integration available. 49 components, 140+ schema properties, fuzzy-matching settings validator, data repair pipeline, Oxygen 6 detection, and 10 layout patterns.
The deepest Breakdance Builder MCP integration available. 84 elements across 7 categories, 120+ schema properties, nesting validation, fuzzy matching, content/design data preservation, and 8 layout patterns.
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.
7 new Bricks-dedicated tools. Cross-site element search, page health diagnostics, Automatic.css integration, query loop discovery, style profiling, and design system export.
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.
Every AI edit now has an undo button. New Changes page in wp-admin, storage management, merge-mode default for approvals, and WebMCP write-tool protection. Three months of "can you revert that?" tickets, gone.
Compact MCP responses, working-copy reuse, simpler multi-site setup, and a broad reliability pass driven by a single support ticket from a customer who asked for their money back. They stayed.
Fixed: when a site cannot reach respira.press to check its licence, the add-on keeps working for 3 days from the last check that confirmed the licence. The grace used to restart with every failed check, so it never ran out, and it also appl
Fixed: WordPress did not show an Enable/Disable auto-updates control for the WooCommerce add-on while it was already current. The updater supplied metadata only when a newer package existed; WordPress also needs an explicit current-version
Fixed: nine write tools could not run on hosts that block the PUT method. Those hosts are common enough that Respira already retries such a write as a POST, but these routes were registered to accept PUT only, so the retry arrived at a rout
Added: writes now say whether the AI actually looked at what it changed. A write names an id, and until now nothing checked where that id came from, so an assistant that read your catalogue and one that carried an id over from a different s
Added: size limits on price and stock writes. Every write tool already checked that the caller was allowed to make the change and that the batch was not enormous. None of them checked how far the change went, so "set every product in this c
Security: text a customer typed into your checkout no longer reaches your AI assistant as-is. Customer reads returned the name, company and address lines exactly as they were entered, and a tool result is not a document: whatever is in it l
Fixed: listing orders failed outright on any store that has ever issued a refund. WooCommerce's own order query returns refunds alongside orders by default, and a refund is not an order: it carries no order number, no customer and no billin
Fixed: setting a category image did nothing and said it worked. update-category only ever read name, slug, description and parent, so image_id fell through untouched, the update ran with nothing to change, and the unchanged category came ba
Added: order reads now return customer_ip_address, customer_user_agent and meta_data. Without the request fingerprint and the order meta, the order tools could not support payment-fraud triage at all, and the reporter kept a competing plugi
Fixed: the update notice for this add-on could never clear itself. 4.0.2 bumped the plugin header but not the version constant underneath it, and the constant is what the updater reports to the server as your installed version. So every sit
Fixed: a site running both Respira and this add-on printed "Ability category respira-woocommerce is already registered" on every request. Both plugins registered the same category, so with the add-on installed the collision was guaranteed r
Fixed: an agent orders summary could 500 the whole site on hosts that answer plugin bootstrap before WooCommerce finishes waking up. It now waits for WooCommerce's own readiness signal before touching order data, and falls back to an honest
Storefront intelligence is now FSE-first with page-builder fallback. On a block theme, analysing a shop page returns real structural analysis against the native archive-product template instead of "no page builder detected". The two badge t
Fatal error on HPOS stores (PHP 8). The daily license check, which also gathers a small agent-orders summary for the dashboard, could run on the plugins_loaded hook before WooCommerce initialized its order data store. On stores using High-P
Thrive Architect product pages — description edits didn't appear on the frontend — bulk_update_products with description / short_description wrote to post_content via WooCommerce setters, but Thrive Architect renders from its own wp_postmet
Product category CRUD endpoints and MCP tools (list/get/create/update/delete).
Release pipeline reliability: ensures fresh tag/release creation behavior.
Initial WooCommerce add-on release.