Setup should show the site coming alive, not a checklist.
Connecting a site used to be a form you filled in and a state you had to take on faith. The plugin said one thing, the dashboard said another, and you were left guessing whether an agent could actually reach the site and what it was allowed to do. That gap is the thing this release closes.
The setup and connection screens were rebuilt to tell the same story as your respira.press dashboard. You link the site once. Then you watch the moment an agent first 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 one-click installs lead the way in, the Desktop app, Cursor and Cowork, and signing in through the browser stays available for ChatGPT and claude.ai.
Underneath, the screens now read connection state from a single source. The plugin, the dashboard and your agent always agree on whether a site is connected and what access it has. No more two screens disagreeing about the same site.
One source of truth, shown as it happens.
You see the connection land.
link the site once, then watch the first agent reach it and name what it did.
The setup and connection screens were rebuilt so the plugin tells the same story as your dashboard. State is read from one place now, so nothing has to be reconciled in your head.
- link a site once, then the screen updates on its own the moment an agent first reaches it.
- when an app connects, the screen names what just happened, for example "connected. Claude just ran update_page on page #42".
- one-click installs lead: the Desktop app, Cursor and Cowork. browser sign-in stays available for ChatGPT and claude.ai.
- version and scope are shown coherently, so what the agent can do is plain to read.
- the plugin’s setup screen
- the plugin’s connection screen
- your respira.press dashboard
- the agent connecting to the site
Your sites arrive with their real names.
The plugin now sends your WordPress site title when it activates and when it checks in. A site shows up by name instead of a bare URL, which matters the moment you manage more than one. This pairs with the dashboard's new friendly-name and inline rename, so the site you are looking at is the site you think it is.
Seven fixes, grouped by where you would hit them.
Each one was checked against the real builder on a real install, not the tool result. The full per-builder detail lives on the plugin page.
Two Bricks fixes you would notice on the next edit
Moves keep siblings, and same-tab links stay same-tab.
These were the kind of edits that look fine in the tool result and go wrong on the page. Both are fixed and checked against the real Bricks tree.
- moving or nesting an element no longer drops the elements next to it. the move now runs on a flat tree, so siblings stay where they were.
- a link set to open in the same tab now does. a falsy "open in new tab" value used to leak through and force a new tab.
Divi edits land, and odd settings stop corrupting posts
Single-module edits refresh the cache, and bracketed colors are safe.
Two Divi paths that could leave the page stale or, worse, break a custom post type. Both closed.
- editing a single module now refreshes Divi’s cached static CSS, so the new styling shows instead of waiting on a full re-save.
- custom post types are no longer corrupted by color settings that contain square brackets. the value is handled instead of breaking the stored data.
Atomic elements render, and Columns stay intact
Elementor 4.x renders instead of blanking, and nested edits are honored.
The last group covers Elementor 4.x atomic elements and a pair of editing cases inside Gutenberg blocks.
- Elementor 4.x: atomic elements render instead of coming back empty, and no longer throw a 500 in the page head.
- Gutenberg: editing inside a Columns block no longer blanks the column wrapper around it.
- a nested "append" edit is honored as an append now, instead of being treated as a full replace that overwrites what was there.
The builders page and the full diff.
Connect a site you maintain.
i wanted setup to feel like the site coming alive, not a form you submit and hope worked. link one site, put an agent on it, and watch the screen name the first thing it does. if you run more than one site, this is the release where they finally show up by name.
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.
