Release notes,
guides, and journal.
I ship in public. Every release shows up here with its audit trail, every comparison with receipts, every essay with the specific thing I learned. No revolutionary, no supercharged — just the breath WordPress has been holding.
MCP 2026-07-28 is final. What changes for WordPress and Respira?
The stable specification removes protocol sessions, adds server discovery, hardens authorization, and formalizes extensions. Respira 8.1 implements it with a tested legacy path, while Webflow MCP 2.0 shows why production governance matters.
Get the release notes & guides in your inbox.
Ships when I ship. No drip sequences, no digests, no "5 things" lists.
Agentic news dispatches
1 postsNo matches for ""
Try a builder name (Elementor, Divi, Bricks), a release version (6.0.0), or a concept (snapshots, MCP, CLI).
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.
From the workshop
Bronko rebuilt 16 pages with Respira for WordPress and measured each one against the original. The styling was wrong. Not broken, exactly. Just disconnected from the design presets already set up inside Divi 5. Fixes that should have bee…
Importers guess. That is the thing nobody says out loud. You hand a page builder your HTML, and it decides what you meant. A div becomes a section or it doesn't. A heading gets mapped to the nearest approximation. A broken image placehol…
The rules a designer would never bend used to live in their head. Now they live in the MCP. Art Direction gives each WordPress site one written standard: palette, type, and the designer's own DO and DON'T, stored where an AI assistant ac…
The client opens the control panel inside their own WordPress site and sees the agency's name. Not Respira's. White label in Respira for WordPress replaces every place a client could meet the interface: the name, the mark, all of it. No…
Toby Cryns is right that this is the gap. the shape of it is the interesting part. Lovable makes new things. WordPress’s harder problem is the sites that already exist: a builder already chosen, content already written, a client already…
"This is genuinely category-defining infrastructure that’s flying under most of the WordPress-AI coverage."