Click through the redesigned admin
This is the real plugin React UI running with stub data. Every screen renders, every tab clicks, every form responds. Nothing here writes to a real WordPress site; the audit-log rows, the agent list, the activity report, and the health scores are all fixtures. Use it to see what the plugin looks like before you install it.
What's new since 7.0.
Respira Playbooks
The agent authors a workflow once. Every future run is one tool call.
A Playbook is a typed JSON workflow composition stored in wp_respira_playbooks. The agent describes the workflow in plain text, Respira validates the JSON, persists the row, and registers it as a WordPress Ability via wp_register_ability. From that moment it appears in the MCP tool catalog as respira-playbooks/<id> and runs as a single typed call. Production-safe by construction: destructive tools are refused at create-time, static + runtime cycle detection cap recursion at depth 5, and every step routes through the existing audit + snapshot belt.
- Five new MCP tools: respira_create_playbook · list · get · update · delete
- Templates use {{input.x}} for caller args and {{<capture>.field}} for prior-step results
- 22 destructive tools refused at create-time with split-the-flow hints in the error
- Static cycle detection + runtime depth cap make sub-playbook composition safe
- wp-admin → Respira → Playbooks lists every Playbook, inspect / export / delete in one screen
- Public directory at respira.press/playbooks (opt-in per site)
respira_create_playbook({
id: "case-study-create",
label: "Create Case Study",
input_schema: {
type: "object",
properties: {
client_name: { type: "string" },
industry: { type: "string" }
},
required: ["client_name", "industry"]
},
steps: [
{
tool: "respira_create_custom_post",
args: { post_type: "case_study",
title: "{{input.client_name}}",
status: "draft" },
capture: "post"
},
{
tool: "respira_update_custom_post",
args: { type: "case_study",
id: "{{post.id}}",
meta: { industry: "{{input.industry}}" } }
}
]
})
// On every subsequent run:
respira_invoke_ability({
ability: "respira-playbooks/case-study-create",
args: { client_name: "GlobalBank", industry: "banking" }
})Custom Structures
12 new MCP tools — CPTs, taxonomies, ACF field groups
Agents can now provision a Custom Post Type, a custom taxonomy, and an ACF field group in three tool calls. No PHP, no plugin install, no filesystem write. Definitions are stored in wp_options and registered against WordPress core via register_post_type / register_taxonomy / acf_add_local_field_group on init. Slug allowlist server-side, reserved WordPress + WooCommerce slugs refused, deletes are conservative (orphans surface in the response).
- respira_create_post_type / update / delete / list_custom_post_types
- respira_create_taxonomy / update / delete / list_custom_taxonomies
- respira_create_acf_field_group / update / delete / list_acf_field_groups (when ACF active)
- Closes the "agent provisions structure" surface without touching plugin files
Four new page builders
Spectra, Kadence, GenerateBlocks, SeedProd — coverage goes 12 → 16
Spectra (UAG namespace), Kadence Blocks, and GenerateBlocks join with full read + write support. SeedProd is audit-only in v7.1 — agents read and report on landing pages, but writes are blocked because SeedProd's proprietary layout JSON isn't documented at attribute granularity. Write support lands in 7.1.x once the schema is reverse-engineered against more customer fixtures.
- Spectra (UAG) — full read + write
- Kadence Blocks — full read + write
- GenerateBlocks — full read + write
- SeedProd — audit-only in v7.1, write in 7.1.x
Full 108-module Divi 5 catalogue
Was 16 hand-curated. Now scanned weekly from the live Divi catalogue.
The Divi 5 adapter went from 16 hand-curated module schemas to the full 108-module catalogue. Five new modules Elegant Themes shipped in Divi 5.5/5.6 (plus Timeline's child) land with rich attribute schemas, flat alias → deep path mappings, and module-specific safety hooks. SVG writes route through Divi's own SvgSanitizer; Instagram writes against a disconnected account surface a warning instead of silently succeeding.
- 108 Divi 5 modules in Respira's schema lookup (was 16)
- Six new 5.5/5.6: Timeline · Timeline Item · Breadcrumbs · SVG · Table of Contents · Instagram Feed
- Runtime introspection scanner reruns in ~150ms after every Divi release
- 18 silent-write flat alias bugs fixed (admin_label, padding, button_color, …)
Redesigned wp-admin
React-first surface. Live agent ↔ Respira ↔ site bridge view.
The plugin admin is a React-first surface. Live bridge view of agent ↔ Respira ↔ site. Real telemetry cards (MCP clients online, approvals waiting, activity tail, intelligence chart). Density toggle, command-K palette, dark by default with one-click light theme. The 7.0.x classic admin is gone — every screen is the React shell now.
- Live bridge view with three-node health (agent · Respira · your site)
- 11 new REST endpoints, all reading real audit data
- Connected MCP clients card with per-key scope + local revoke
- Skeleton + error states everywhere — no silent blank pages
Connect from anywhere
Point Claude or ChatGPT at your site with a link and a key.
There is now a native MCP endpoint on your site. Point Claude or ChatGPT at it with a link and a key. Nothing to install, and it works from the web or your phone. The local setup is still there if you want it, but you no longer need a desktop app to connect.
- A link and a key, no install step
- Works from the web or your phone
- Same per-key scope and approval rules as the local setup
SEO on categories and tags
Term titles and descriptions, not just pages and posts.
Your agent now writes SEO titles and descriptions for categories and tags, not just pages and posts. Term archive pages were a blind spot before. Now they read and write through the same SEO tools as the rest of the site.
- Read and write SEO titles and descriptions on any term
- Covers categories, tags, and custom taxonomies
- Same SEO tools that already cover pages and posts
generate_activity_report — your audit log becomes a client report.
Respira reads a month of work on this site, totals the numbers, and hands your AI a writing prompt.
Six framings: personal_recap, agency_client_report, agency_case_study,
team_report, testimonial_draft, build_in_public. Anonymize toggle for case studies.
Below is the structured data behind a typical run, mirroring the exact shape generate_activity_report
returns: meta, totals, time_savings (with optional cost_saved when you supply an hourly_rate), top_tools,
top_builders, summary_cards, client_highlights, proof_points, safety_notes.
summary_cardstop_tools- write
update_module14× - read
extract_builder_content23× - write
create_page_duplicate12× - read
analyze_seo8× - write
apply_accessibility_fixes5×
top_builders- divi
31 edits18 snapshots - gutenberg
9 edits7 snapshots - elementor
2 edits2 snapshots
client_highlights- Work completed across the selected site window. 132 recorded tool calls produced 42 completed edits across 14 page(s), 9 post(s), and 0 product(s).
- Every meaningful change stayed reversible. 27 snapshot(s) were created during this period, giving the work a rollback path instead of relying on manual undo.
- Time saved against manual WordPress work. Respira estimates 5.1 hours saved for the selected work, using the configured per-tool manual-time baselines.
proof_points- Recorded work
- 132 calls, 42 edits
- Coverage
- 14 pages, 9 posts, 0 products
- Reversibility
- 27 snapshots, 2 rollbacks
- Estimated time saved
- 5.1 hours
- Estimated value
- 407.33 EUR
safety_notes- 27 rollback snapshot(s) were created in this window.
- 2 rollback(s) were invoked. Review the operational appendix before sending a client-facing version.
- Tool error rate was 0.76% for the selected period.
What changed for each adapter.
Coverage went 12 → 16 builders. Below is what shipped per adapter in v7.1 — including the four new ones and the three already-supported builders that got the deepest work.
Runtime catalogue scan from Divi's Packages/ModuleLibrary/. 6 new 5.5/5.6 modules ship with rich schemas + SvgSanitizer + Instagram warnings.
$$type envelope-preserving writer for atomic v4 widgets. 20-entry atomic catalog, supports_children covers all 11 v4 layout types.
Element-name validator with did-you-mean. Templates CPT first-class CRUD. Bricks ACSS / breakpoints / palettes endpoints under respira/v2.
Full UAG namespace coverage. Drops into the same extract/update/inject contract as the other 15 builders.
Kadence Blocks (not the theme — separate adapter). Standard widget shortcut map + write-trace contract.
Container / Grid / Heading / Buttons / Image surfaces with their typed attribute schemas.
Landing-page builder. Audit-only in v7.1 — agents read and report on pages but writes are blocked because SeedProd's proprietary layout JSON isn't documented at attribute granularity (paid customers' landing pages are too high-value to risk corruption). Write support lands in 7.1.x.
From 16 modules to the full 108-cell catalogue.
v7.0 supported 16 Divi 5 modules by hand. v7.1 auto-scans the Divi 5.6 catalogue at runtime and lights up the full 108 — including the six new modules Elegant Themes shipped this year (Timeline, Timeline Item, Breadcrumbs, SVG, Table of Contents, Instagram Feed).
The five cross-cutting invariants every adapter still inherits.
- A.1 Render-validation gatePost-write HEAD-fetch + parser-walk on persisted blob.
- A.2 Universal write-traceEvery adapter exposes build_write_trace with 12 canonical fields.
- A.3 Variables CRUD shapeUniversal /builder/{builder}/variables/{type} across color, typography, spacing, breakpoints.
- A.4 Catalog auto-scanHand-curated registries replaced with 1h-cached filesystem scans.
- A.5 Typed validators12 canonical type slugs (color / dimension / url / integer / number / boolean / string / enum / font_family / image_url / svg / class_list).
Docs, SDK, and the full diff.
Install 7.1 on a site you maintain.
7.1 is a cumulative roll-forward from any v6.x or v7.0 release with zero breaking changes. The Maker plan covers one site. Builder covers five. Studio scales to 250.
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.
