Changelog
Every release, in detail.
Release notes for Novamira and Novamira Pro.
v1.12.3
Latest- Fix: Blocks sent to the Block Editor Queue without any settings of their own now save with all of their content. Such a block reached the hidden editor in a form the editor could mistake for outdated content that needed converting, and the conversion discarded the block's items: a bulleted or numbered list was saved empty, or with a single blank item, while the queue still reported the item as finalized. Queue items created before this release are corrected as they are read, so batches already waiting do not need to be recreated.
- Fix: Novamira CLI setup prompts now tell AI agents to select the installer for their current shell and switch to device authorization when browser sign-in cannot complete, so headless connections can finish without manual troubleshooting.
- Minor Fixes
v1.12.2
- Fix: Activating Novamira with WordPress debugging on no longer prints a "Translation loading for the `novamira` domain was triggered too early" notice, followed by "Cannot modify header information" warnings in wp-admin. Feature names and descriptions are now translated when they are displayed rather than while the plugin loads, and abilities still register as early as before.
- Fix: CSS and JavaScript files created in the sandbox can be loaded by site pages again. PHP and all other sandbox files remain blocked from direct web requests, and protection files installed by the previous release are upgraded automatically without replacing custom server rules.
v1.12.1
- Fix: Browser sign-in now completes on hosting with an external object cache, where a freshly opened approval link could be reported as invalid or expired before it was ever used. The short-lived approval state is now kept in the database, so AI clients that could not get past the approval screen, such as ChatGPT, connect again.
- Tweak: The Troubleshoot page now confirms that every OAuth table is installed instead of checking only the first one, so a partial installation is reported rather than appearing healthy.
v1.12.0
- New: A Features page lets administrators turn complete Novamira components on or off (Pro specializations will arrive with the future Novamira Pro 1.9.0 release). Abilities previously turned off individually are turned back on when their component is active.
- Tweak: Features, skills, abilities, and sandbox files now share a quieter interface with clearer hierarchy and consistent disabled states. Incomplete user skills now state what is missing and how to complete them.
- Fix: Agent context is now categorized as read-only context, so Novamira Chat no longer asks for code-execution approval before retrieving it.
- Fix: The Block Editor Queue now rejects page-builder blocks that require their builder's own runtime and directs AI agents to the appropriate integration, instead of accepting batches that cannot be finalized.
- Fix: WP-CLI abilities are now exposed only when the server can execute WP-CLI. AI agents that request them by name on unsupported servers receive the reason they are unavailable.
- Fix: The Block Editor Queue now reports when its hidden editor is unavailable instead of describing every third-party block as unregistered. WordPress 7.1 can also access the hidden editor directly again.
- Fix: Novamira Design now recognizes Do and Don't guidance grouped under labels or subheadings, including typographic apostrophes. Design checks enforce the same guidance and warn when none is recognized.
- Fix: Novamira Visual no longer lists internal system abilities as usable backend tools.
- Fix: ChatGPT connectors can now pass arguments to Novamira abilities through the generic execution tool instead of rejecting them as invalid.
- Fix: Novamira's full AI toolset remains available when another plugin loads the WordPress Abilities API first, instead of exposing only ability discovery.
- Minor Fixes
v1.11.6
- Fix: Novamira no longer announces classes of its bundled MCP Adapter at a location the plugin does not ship. On a site where another plugin checks whether those classes exist, that check ended in a critical error on every page after updating to 1.11.5.
v1.11.5
- New: The Configuration page now covers all 72 AI agents supported by the Novamira CLI installer, from Claude Code and Codex CLI to Hermes Agent and OpenClaw. Choose an agent once and see only the connection routes that work for it: Novamira CLI, OAuth, or Application Password.
- Tweak: Recurring admin notices now use a consistent close button and stay dismissed for each administrator, while critical setup errors remain visible.
- Tweak: When the OAuth tables are missing, the Troubleshoot page now names what is actually stopping the installer — AI Abilities being off, a domain lock, or the site not being served over HTTPS — instead of suggesting a deactivate and reactivate cycle that could not have helped.
- Tweak: Updated the bundled MCP Adapter to version 0.6.1.
- Fix: Anything a sandbox file prints while it loads is now discarded instead of being added to the response being built at the time. A single leftover debug line in a sandbox file used to appear ahead of the JSON on the MCP and OAuth endpoints, which broke every AI client's connection with a parse error, and showed up on front-end pages and admin screens too. With WP_DEBUG on, the discarded text is written to the PHP error log along with the file that printed it.
- Fix: A sandbox file that stops with an error no longer ends the whole request. The remaining sandbox files still load, WordPress finishes loading, and safe mode switches on from the next request as before — where previously one broken sandbox file could surface as an unrelated fatal error elsewhere in WordPress.
- Fix: The Block Editor Queue can now finalize third-party blocks in Chromium on WordPress 7.1, where the isolated editor previously caused registered block libraries to appear unavailable.
- Fix: AI clients that support both device authorization and browser sign-in, such as Visual Studio Code, can now connect over OAuth. They were registered as device-only clients, which discarded the redirect address they needed and left them refused at sign-in with "This application is registered for device authorization."
- Fix: The admin warning for detected connection problems now opens Troubleshoot directly instead of sending administrators to Configuration.
- Minor Fixes
v1.11.4
- New: Before deactivating Novamira, the review page now shows stored Novamira Pro memories, user-added skills, and Chat sessions. Choose whether to preserve or permanently delete each data type when removing the plugin.
- New: AI clients can now discover which Gutenberg block types a site has registered and read each block's attribute schema, supports, and nesting constraints before composing content, instead of finding out about a wrong block name or attribute only when a Block Editor Queue batch fails.
- Tweak: The Troubleshoot page can now clear this site's registration limits, so an AI client that reports too many attempts can be connected again right away instead of waiting for the hourly budget to refill. Connected clients are left untouched.
- Fix: Revoking a connection from Manage Connections now frees its connection slot right away, where the slot stayed in use until the connection expired on its own and could keep new clients from registering.
- Fix: The Block Editor Queue endpoints for claiming, completing, and failing queue items now respond with a clear "send a JSON object body" error when a request arrives without a JSON body or with a malformed one, instead of stopping with a PHP fatal error that left the batch stuck in the running state.
- Fix: The Block Editor Queue now mounts blocks in the hidden block editor before saving them, so blocks that receive their settings from the editor itself save complete. Previously blocks from libraries such as Kadence Blocks, Spectra, and GenerateBlocks could save without their per-block style IDs and layout markers — rendering unstyled, or with a row's columns stacked full-width — even though the queue reported success.
- Minor Fixes
v1.11.3
- New: The Configuration page now asks for the AI client before the authentication method, shows every supported client, and explains technically why an authentication method or cloud-only client cannot work in the current environment.
- New: Novamira detects Kinsta, WP Engine, Hostinger, SiteGround, Pantheon, and Cloudflare security layers that may classify direct connections from cloud AI clients as bot traffic. Application Password is recommended where appropriate, while OAuth remains available with a dismissible technical warning and an editable support email template.
- New: A dedicated Manage Connections page brings OAuth connected apps and Novamira Application Passwords together, with their usage details and revoke actions.
- New: Command-line tools can sign in with a device code when their browser runs on another machine, such as a shell reached over SSH or inside a container. The tool shows a short code, and you approve it from any device where you are signed in to this site. Only approve a code you started yourself.
- New: Before deactivation, Novamira warns when sandbox files may be powering site functionality, provides a copyable prompt for moving them to persistent storage, and lets administrators choose whether uninstall should remove OAuth data and revoke Novamira Application Passwords across all users.
- Tweak: Codex in ChatGPT Desktop and Codex CLI now have separate setup instructions, and the consumer Gemini CLI entry has moved to Antigravity CLI with its current MCP configuration format.
- Tweak: simplify troubleshooting for blocked OAuth connections.
- Tweak: AI clients now receive the WordPress user ID behind their connection and are warned not to modify Novamira or revoke the credentials keeping that connection active.
- Fix: Claude Code connection commands now register the MCP server globally for the current user.
- Fix: The Block Editor Queue no longer fails every batch with a "Blocked a frame with origin ... from accessing a cross-origin frame" error. When the hidden block editor iframe cannot be read, the queue now serializes with the block runtime of the queue page itself and reports why the iframe was unavailable, instead of failing the batch.
- Minor Fixes
v1.11.2
- Fix: Abilities that take no parameters, such as reading the active design or listing the design library, now work with AI clients that send no input at all, where they previously returned an invalid input error.
- Fix: WP-CLI now runs on Windows, including Local (Local by Flywheel) sites. Set NOVAMIRA_WP_CLI_COMMAND or use the novamira_wp_cli_command filter when detection is not enough.
- Fix: Background WP-CLI jobs on Windows return their job ID and the command's real exit code, and no longer corrupt paths or arguments containing %, !, quotation marks or accented characters.
- Fix: A wp.bat launcher is used only when its wp-cli.phar sits beside it, so command arguments never pass through the Windows command interpreter.
- Fix: OAuth key generation failures now report what OpenSSL refused and how to fix it, and "wp novamira oauth-keys generate" creates the keys from a working PHP environment.
- Minor Fixes
v1.11.1
- Fix: OAuth connections no longer ask users to reconnect for additional permissions.
v1.11.0
- New: Introduced REST API endpoints for the Novamira CLI. More information: novamira.ai/cli.
- Fix: Running PHP through an AI agent no longer logs a PHP warning on every call, which on some server setups flooded the error log and made large operations return a gateway error even though the change had already been saved.
- Minor Fixes
v1.10.1
- New: The one-click .mcpb bundle download for Claude Desktop is available again; it requires Claude Desktop 1.24012.1 or later.
- New: A Troubleshoot page runs on-demand checks on your site's AI connection and points at what to fix, including whether a CDN, firewall, or security plugin in front of the site is filtering AI clients. It produces a copyable report.
- New: A dashboard notice warns administrators when a change on the site stops a previously working AI connection from authenticating, so a connection that suddenly breaks does not go unnoticed.
- Tweak: Developers can raise the limit of 50 simultaneous OAuth connections with the novamira_oauth_max_clients filter.
- Fix: OAuth sign-in now works for AI clients that request the discovery documents with the resource path appended or inserted, as current connectors do, and on WordPress installed in a subdirectory, where those requests previously returned a "page not found" error.
- Fix: Imported design directions now recognize heading and body fonts declared as CSS custom properties or labelled lines, so a design no longer saves without an activatable font pair.
- Minor Fixes
v1.10.0
- New: Novamira Design. AI agents establish one saved design direction for your site and build every page within it, guarded by anti-slop checks; the new Design page lets you preview, import, edit and activate directions. Companion skills cover the workflow, from the design brief to the finished pages.
- Minor Fixes
v1.9.2
- New: ChatGPT support. Connect ChatGPT to your site with OAuth sign-in through its developer-mode custom connector.
- Tweak: Overwriting a post through the Gutenberg pending-change flow is now treated as a destructive action, so your AI client asks before replacing content.
- Tweak: Reading skills can no longer be turned off, so your skills always stay available even when other abilities are disabled.
- Tweak: Calling an ability you've turned off now reports that it is switched off and can be re-enabled, instead of a confusing "not found".
- Fix: Saving Gutenberg content no longer strips backslashes, which could corrupt blocks that rely on escaped characters.
- Minor Fixes
v1.9.1
- New: OAuth sign-in for AI clients. Claude and other MCP clients can connect through a standard OAuth authorization flow, approving access from your WordPress login. The Connect page walks you through each client with per-client setup steps.
- Fix: Abilities Hub enable, disable, and bulk actions no longer fail with an "Invalid ability name" error on some sites.
- Minor Fixes
v1.9.0
- New: Novamira Chat, an AI agent that lives inside your WordPress dashboard. Describe what you want in plain language and it makes the change, showing you exactly what it will do and asking for your approval first. It runs on your own AI provider key, so there is no subscription and you pay only for what the AI uses. Use it on a staging site with backups. Requires WordPress 7 and your own AI provider API key.
- Tweak: The write-file ability now rejects base64 and binary payloads, and points agents to the upload-link ability for large uploads.
- Minor Fixes
v1.8.1
- Fix: The Claude Desktop one-click bundle (.mcpb) is not connecting on recent Claude Desktop versions, so manual configuration is shown by default for now while we look for a solution.
v1.8.0
- New: Novamira Visual, an experimental browser workspace where you watch your AI agent work on WordPress in real time. Instead of working out of sight, the agent opens your pages and the block editor in front of you. For development and staging sites. Elementor and Bricks support comes with Novamira Pro.
- Minor Fixes
v1.7.1
- New: Claude Desktop gets a one-click .mcpb bundle download that installs the MCP server without editing any config files.
- New: The Connect page now asks you to pick your AI client first; the connection options (prompt, bundle, or manual JSON) appear only after that choice, tailored to the selected client.
- Tweak: When AI Abilities are disabled, existing application passwords are listed below step 1 without the step 2 framing, so the setup flow is clearer.
- Fix: WordPress 6.9 ability discovery no longer emits PHP notices for missing or late-registered ability categories.
- Minor Fixes
v1.7.0
- New: A Context page for giving AI agents stable, site-wide guidance they apply automatically on this site. If you also run Novamira Pro, this page appears once Pro is updated to 1.3.0 or later; until then Pro keeps providing custom instructions as before.
- Minor Fixes
v1.6.0
- New: A new Abilities Hub screen lists every ability available to AI agents, grouped by the plugin that provides it, so you can enable or disable each one individually.
- Tweak: Gutenberg pages built by AI agents now consistently use native and third-party blocks, so the result stays editable in the block editor; previously they could sometimes place content in a single raw HTML block.
- Tweak: Before building or restructuring a page, AI agents now confirm which approach you want to use (a page builder, the block editor, or the theme itself) instead of assuming one.
- Tweak: The Configuration page now notes that the paste-to-agent prompt includes your application password, and links to the manual configuration if you prefer not to share it with the AI.
- Minor Fixes
v1.5.1
- Tweak: The Novamira admin bar item now includes a dropdown toggle for turning AI Abilities on and off.
- Minor Fixes
v1.5.0
- New: In the Gutenberg Block Editor AI agents can now create and edit third party blocks valid from the first save
- Tweak: Large-file uploads and browser admin access now use header-based handoff flows, so generated endpoint URLs stay short and easier to reuse in tool commands.
v1.4.0
- New: Gutenberg (Block Editor) support, AI agents can now author and edit posts, pages, templates, template parts, and navigation menus, with native blocks valid from the first save
- New: The Configuration page now includes direct HTTP snippets for Claude and Codex clients that cannot use the default npx-based MCP setup.
- Minor Fixes
v1.3.0
- New: Skills. Create or upload Markdown playbooks your AI follows automatically on this site, including a built-in skill that teaches your AI to write new ones.
- New: AI agents can now create short-lived, one-time WordPress admin access links for browser automation tools, without exposing admin passwords.
- Tweak: The Sandbox files page now uses the same compact card layout as the Skills page, with an Enable/Disable toggle and file-type badges.
- Minor Fixes
v1.2.1
- New: AI agents can now run WP-CLI commands through Novamira, with support for background jobs.
- Minor Fixes
v1.2.0
- New: AI agents can now upload plugin, theme, media, and other large files more easily.
- New: A "paste to your AI agent" block on the Configuration page lets you copy a short description and have your AI client set up the MCP server connection for you, instead of editing JSON config files by hand.
- New: The Configuration page warns when AI Abilities are turned on against what looks like a production site, with a reminder to keep them on staging or development copies only.
- New: If you already have a saved application password (for example from a password manager), a new field on the Configuration page lets you paste it directly and skip generating a new one.
- New: Local HTTPS development sites with self-signed certificates are detected automatically, and the generated client configs include the small flag Node.js needs to accept the certificate.
- New: When the site is on a local hostname over HTTP, the Application Passwords notice now explains the exact line to add to wp-config.php to enable them.
- Tweak: Redesigned the Configuration page into three numbered cards (Enable AI Abilities, Application Password, Connect Your AI Client) so the setup reads top to bottom.
- Tweak: The MCP endpoint is now /wp-json/mcp/novamira. The previous /wp-json/mcp/mcp-adapter-default-server keeps working for AI clients that are already connected, no action needed.
- Tweak: Per-client JSON snippets are collapsed by default behind a "Need the JSON config for a specific client?" link, since most setups now use the paste-to-agent block.
- Tweak: AI agents working with data-modeling plugins (ACF, JetEngine, Pods, ACPT, Meta Box, Toolset, CPT UI, WooCommerce, etc.) are now told to use the plugin's own UI or API instead of registering post types, taxonomies, or fields directly in PHP, avoiding broken slugs and labels later.
- Fix: PHP notices about duplicate ability registration on every wp-cron tick no longer appear in the error log.
- Minor Fixes
v1.1.2
- New: Configuration instructions for the OpenAI Codex CLI MCP client.
- Fix: The Novamira ON admin bar indicator now only appears for administrators who can manage Novamira settings.
- Minor Fixes
v1.1.1
- Improvement: The Configuration page now detects when Application Passwords have been disabled by a security plugin (e.g. Solid Security, Wordfence) and shows a clear explanation instead of the generic HTTPS/local-environment message.
- Improvement: Moved the AI Abilities on/off switch to the top of the Configuration page making clear they are needed for the MCP to work.
- Improvement: When an AI agent sends invalid input, the error message now includes the specific per-property details the agent needs to correct it — so the agent can fix its own mistake in one try instead of guessing or asking the user.
- Minor Fixes
v1.1.0
- Fix: Recursive directory listings no longer fail when a folder contains a broken shortcut (symlink) — the listing now skips over it gracefully and includes the rest of the results.
- Improvement: AI agents now reliably receive site context and usage instructions, even on MCP clients that previously ignored them during connection setup.
- Improvement: Updated the bundled MCP Adapter library to version 0.5.0.
- Fix: Ability failures are now surfaced as proper errors instead of being masked by a success response.
- Minor Fixes
v1.0.3
- Fix: Sandbox crash detection failed to detect fatal errors thrown indirectly from WordPress core or third-party code called by a sandbox file.
v1.0.2
- Fix: Sandbox crash detection now uses a shutdown handler instead of a file marker, eliminating false positives from concurrent requests and external code calling exit().
- Fix: Execute-ability coerced empty parameters (`{}`) to `null`, causing "input is not of type object" validation errors for abilities with all-optional properties.
- Remove: PHP syntax validation from write-file and edit-file abilities — the sandbox already catches syntax errors at runtime, making pre-write validation redundant.
- Minor Fixes
v1.0.1
- New: Configuration instructions for 7 additional MCP clients: Cline, Roo Code, Kilo Code, GitHub Copilot, Amazon Q, Gemini CLI, and Antigravity.
- New: MCP server name now defaults to the site domain for easier multi-site setups.
- New: MCP server instructions include site locale and multilingual context.
- Fix: Admin page header spacing.
v1.0.0
- 🎉 First stable release.
v1.0.0-rc4
- New: Domain-locking for AI abilities — the site hostname is stored when abilities are enabled. If the domain changes (e.g. a staging database is restored on a different server), abilities automatically deactivate and an admin notice explains what happened.
- New: MCP server instructions — AI agents now receive context about the WordPress environment (version, active plugins) during MCP initialization.
- Minor fixes.
v1.0.0-rc3
- Fix: Shell quoting in the Claude Code mcp add command — the MCP server URL and other env values were not properly quoted, causing syntax errors when pasting the generated command.
v1.0.0-rc2
- Minor fixes.
v1.0.0-rc1
- Release candidate for 1.0.
- Eight abilities: execute-php, read-file, write-file, edit-file, delete-file, disable-file, enable-file, list-directory.
- PHP sandbox with crash recovery and safe mode.
v1.9.0
Latest- New: Blocksy specialization (requires the Blocksy theme 2.1.47 or newer, with Blocksy Companion and Companion Pro also supported): AI agents can set up the theme's global design, per-page layout, header and footer, and Companion features. A companion skill walks agents through the workflows.
- Tweak: Divi modules are now written through the dedicated Divi tools, so what an agent builds saves and renders as expected.
- Tweak: Kadence pages on a site where the block editor cannot run now come back with that as the reason, so the agent reports it instead of working around it.
- Tweak: Novamira Pro specializations can now be turned on or off with their related abilities and skills from the Novamira Features page (requires Novamira 1.12.0 or newer).
- Tweak: Uninstalling Novamira Pro now deactivates its license and cleans up after itself, handing any Context instructions over to the base Novamira plugin and removing its own settings, caches, scheduled checks, and admin notices.
- Fix: Elementor pages now open in the editor showing the content an agent has just written, instead of an older editor autosave. Writes aimed at a revision or autosave id are refused with a message naming the parent post to target.
- Fix: An Elementor write that does not persist now comes back as an error instead of a success reply, so the agent can act on it rather than carry on with a page that never changed.
- Fix: Elementor content and styles that arrive in the wrong shape are now refused with a validation error that names the offending element and the shape expected there, instead of being saved as a style that does nothing.
- Fix: Divi 5 pages composed one section at a time now open complete in the Divi builder, which previously showed only the first section even though the front end rendered them all. Pages built before this release are put back together on the next write.
- Fix: The Divi 5 tools now appear on sites that run Divi through a child theme whose parent theme folder was renamed.
- Fix: Meta Box post types can now be kept off the public site while staying editable in wp-admin, through the standard WordPress visibility settings.
- Fix: The Code Snippets tools work again on Code Snippets 3.10 (free and Pro), and the supported older versions keep working unchanged. AI agents are also told when a snippet is locked, when an edit was not applied, and which snippets a deleted Pro condition was gating.
- Minor fixes
v1.8.3
- New: Spectra Blocks specialization (requires the Spectra Blocks plugin 0.0.8 or newer; the Spectra Blocks Pro add-on is detected when present). AI agents can check the install state and version pair, browse the block catalogue with its activation state, read the plugin settings including reCAPTCHA configuration and Global Block Styles, and inspect Popup Builder popups down to their block markup. A companion skill covers the workflows and keeps the legacy Spectra (UAGB) plugin clearly separate.
- Tweak: The Kadence, GenerateBlocks, and GeneratePress build skills now teach agents about editor-assigned block settings (per-block style IDs and layout markers). With the upcoming Novamira release the Block Editor Queue fills them in automatically at finalization; on Novamira 1.11.3 and earlier the skills instruct agents to supply them by hand, so composed blocks no longer save unstyled or with a row's columns collapsed while the queue reports success.
- Fix: The Spectra build and integration skills now walk agents through the real Block Editor Queue pipeline for composing uagb/* content, where they previously pointed at per-block editing tools that do not exist, stopping every Spectra page build at the first step. They also cover Spectra's editor-assigned block_id, so composed blocks no longer save unstyled on Novamira 1.11.3 and earlier.
- Minor fixes
v1.8.2
- New: Voxel specialization (requires the Voxel theme 1.7.8.3 or newer). AI agents can build a Voxel site's content model, create and edit listings, set up the templates each post type renders through, and read its commerce and community data
- Fix: WordPress admin pages keep loading normally on sites where the license status is refreshed while the page is being built, instead of ending in a critical error.
- Minor fixes
v1.8.1
- New: Oxygen 6 specialization (requires Oxygen 6.0 or newer): AI agents can build pages and templates, style them through the global design system, bind live content and loops, and manage form submissions. A companion skill walks agents through the workflow.
- Tweak: Feedback reports on Novamira now have a place to go: the agent points you to https://novamira.ai/feedback, where you send the report yourself after reviewing it. The agent also offers to prepare one when the same problem keeps coming back after it has genuinely tried to fix it, instead of waiting for you to ask.
- Minor fixes
v1.8.0
- New: Weglot specialization (requires Weglot 5.0 or newer). AI agents can set up the connection, configure the original and translated languages, style the language switcher, and control which pages are translated and under which web addresses. A companion skill covers the boundaries.
- Fix: AI agents can now call the tools that take no required input, whatever MCP client they run in. Those tools previously came back with an input error unless the client sent an empty object explicitly.
- Fix: The Elementor editor keeps working inside the Novamira Visual workspace on Elementor 4.1 and newer. Novamira Visual now turns off Elementor's editor isolation policy so the workspace can drive the editor, and site owners who prefer Elementor's isolation can restore it with the novamira/visual/use_elementor_document_isolation filter.
- Fix: Bricks operations that fail now come back to AI agents as real errors instead of replies that look like success, so an agent no longer carries on after a failed color palette, global class, variable, theme style, or dynamic data operation.
- Fix: Bricks template display conditions written by AI agents are always stored in the array form Bricks reads, on every supported Bricks version: recoverable scalar values are normalized to arrays with a warning, while malformed condition containers or entries are rejected with a clear error before anything is saved (Bricks 2.4 skips malformed scalar values entirely).
- Fix: Bricks code elements written by AI agents now honor the BRICKS_LOCK_CODE_SIGNATURES constant on sites that lock code-signature generation, on every supported Bricks version: a write that needs new code signatures comes back with a clear error naming the affected code elements and how to unlock. On Bricks 2.4 this also keeps unsigned code, which would render empty, off the page.
- Fix: Breakdance pages built by AI agents now come out styled without reopening the builder, because Breakdance's CSS cache is rebuilt after every write to the page.
- Fix: Breakdance element design controls are now fully visible to AI agents, including the grouped ones (the Posts Loop list, the Div layout and background) that previously came back as a single "Error" placeholder, so those elements can be styled instead of left at their defaults.
- Fix: Breakdance elements that cannot render until they are configured, such as a form element with no form picked or a checkout element outside checkout, no longer block later edits to the same page. The element is still added and the agent is told the page will not display it until it is set up.
- Fix: Breakdance raw code elements, and raw page content written straight into WordPress on a Breakdance site, now need your explicit confirmation before an AI agent writes them.
- Fix: Beaver Builder pages written by AI agents no longer fail just because the page contains a column group nested inside a column, a normal Beaver Builder structure that reads always accepted. Column group nodes now allow a row or a column as parent.
- Fix: Mosaic Builder design-system variables can now have their value set by AI agents (color, length, font, etc.), not just their name, so recoloring or restyling no longer requires deleting and recreating variables or falling back to inline styles.
- Fix: Mosaic Builder utility classes can now be styled by AI agents per state (hover, focus, etc.) and breakpoint directly, instead of falling back to raw PHP or database edits that could put the site in a critical error.
- Fix: Mosaic Builder HTML attributes (data-*, aria-*, role, etc.) written by AI agents now carry the identifier Mosaic's own validation expects, so they survive a theme export and import instead of silently disappearing.
- Fix: Mosaic Builder component instances can now have their per-instance override edited or cleared directly by AI agents, instead of falling back to raw database writes that could corrupt the design system.
v1.7.1
- Tweak: Fluent Forms listing and form building are cleaner for AI agents: listing notifications returns compact rows by default (expandable on request), listing submissions hides trashed entries and searches the IP and browser, and building a form now warns when a setting is passed at the wrong level or a form is left with no fields.
- Fix: If the license server was unreachable, admin pages could slow to a crawl. This no longer happens.
- Fix: Fluent Forms forms and fields built by AI agents now render reliably on the page and in the editor. Newly created forms, all field types (including Address, Name, and choice fields), field settings like placeholder, max length and number min/max/step, and the published or unpublished status now take effect instead of silently producing empty output.
- Fix: A range of Fluent Forms robustness fixes: notifications added by AI agents now send on submission without overwriting hand-made ones, per-form permission checks are enforced, confirmation redirects and email headers reject unsafe values, list filters written as text work, concurrent settings edits no longer overwrite each other, and listing or exporting large submission sets no longer risks exhausting memory.
- Minor fixes
v1.7.0
- New: Astra specialization (requires Astra 4.13.5+, free theme plus optional Astra Pro Addon). AI agents can edit the theme settings, color palettes, Header/Footer Builder, and per-page overrides, with more areas unlocked by Astra Pro; a companion skill covers the two tiers.
- New: Avada theme specialization (requires Avada 7.15+). AI agents can edit a curated set of Fusion Theme Options and manage the Global Colors and Global Typography presets; a companion skill covers the boundaries.
- New: Avada Fusion Slider support (requires Fusion Core 5.15.5 or newer, bundled with Avada). AI agents can list the site's sliders and edit their display settings and slides.
- New: OceanWP specialization (requires OceanWP 4.1+, plus the optional Ocean Extra companion). AI agents can edit a curated set of Customizer settings and per-page layout, and with Ocean Extra mount Library templates and turn the Ocean Extra modules on or off; a companion skill covers the boundaries.
- New: Spectra specialization (requires Spectra 2.19+, free plus Spectra Pro). AI agents can browse the block library, manage Popup Builder popups end to end, and turn individual blocks on or off; a companion skill covers the workflow.
- New: Spectra One specialization (requires Spectra One 1.2.2+). AI agents can edit the Global Styles, navigation, and template parts, apply a style variation, and export the whole design as a reusable snapshot.
- Tweak: WooCommerce abilities now register only when WooCommerce is active and at the minimum version, so sites without a store no longer list the WooCommerce category or its setup check.
- Tweak: The Bricks page-building skill now covers query filters and pagination, and the setup check reports whether Bricks' query filters are enabled.
- Tweak: Divi 5 content written by AI agents can no longer carry inline style attributes, since those cannot be edited from the Divi builder controls. The agent gets a clear error pointing to the module's native settings, and inline styles go through only with an explicit opt-in.
- Tweak: Bricks native dark mode can now be set up by AI agents (requires Bricks 2.2 or newer): palette colors accept a dark variant, and reading the palette reports whether the site is ready for Bricks' toggle-mode element.
- Tweak: Meta Box value writes by AI agents can now be scoped to a field group, so a field that does not belong to the group is declined up front instead of being saved as a stray custom field.
- Fix: Elementor pages that AI agents build now import cleanly on any Elementor site, so a page saved as a template moves between sites without errors.
- Fix: GeneratePress Elements now let AI agents read and set their display, exclude, and user conditions, completing the path to building an Element end to end.
- Fix: The Bricks page-building skill now teaches the correct query-loop grid pattern (the loop goes on the card, not the grid container), where Bricks previously rendered one grid per post.
- Fix: Bricks trees written by AI agents now keep parent and children references consistent in every case, and a write repairs any inconsistent link already stored on the page and says so in a warning.
- Fix: Meta Box field groups saved by AI agents no longer fail on Meta Box 2.6.0 and newer when a field carries datalist suggestions.
- Fix: Meta Box field-group reads by AI agents now return the values for every field in the group, where they previously came back empty.
- Fix: Meta Box post types and taxonomies created or edited by AI agents now get working permalinks right away, with no need to re-save the WordPress Permalinks screen.
- Fix: Breakdance Pro licenses are now recognized by AI agents, so a Pro site works with the Pro feature set instead of the free one.
- Fix: Breakdance elements now expose their Settings tab options to AI agents (custom CSS classes, display conditions, draft state), so those can be read and edited like any other element option.
- Fix: Breakdance template abilities now accept the post id in the same form the element abilities use, so AI agents no longer hit input errors when moving between templates and elements.
- Minor fixes
v1.6.2
- New: Bricksforge specialization (requires Bricksforge 3.1.8 or newer). AI agents can set up and manage the Bricksforge add-on for Bricks. They turn Bricksforge tools and custom elements on or off (Pro Forms, Popups, Maintenance Mode, Mega Menu, and more), and build Pro Forms through the Bricks page tools, with the field, choice, multi-step, condition, and layout details handled for them. They create and manage Bricksforge popups (opened on page load, click, or scroll, with a Bricks template as the content), and manage the Email Designer templates that restyle WordPress and WooCommerce emails: which emails each template replaces, its subject, whether it is active, and its theme. A companion skill teaches the form recipe and the Bricksforge specifics, and points agents to a live browser workspace for the visual parts (email layout, animations).
- Fix: Responsive style overrides (tablet and phone) that AI agents set on Divi 5 modules now take effect on the page. When an agent provides a breakpoint override, it is stored in the nested shape Divi 5 reads, whether the agent writes it as a nested object or as a single dotted path, so mobile and tablet spacing, sizing, and typography land as intended. This applies when editing a module, adding a module, and setting a page's content, and the agent is told the native nested shape so its next write matches what the builder stores.
- Minor fixes
v1.6.1
- New: Dynamic Shortcodes specialization (requires Dynamic Shortcodes 1.9.0 or newer). AI agents can build and troubleshoot Dynamic Shortcodes on your site: they can validate and compose shortcode strings, evaluate them against the live site to preview the real value, discover the fields available for each type, and create, edit, list, and delete reusable Power Shortcodes. A companion skill set teaches the syntax with real examples and shows how to place a Dynamic Shortcode inside each supported page builder (Elementor, Bricks, Breakdance, Oxygen, WPBakery, and the block and classic editors).
- New: AI agents can add interactions (motion) to Divi 5 modules. A trigger on a module (a click, hover, scroll, page load, mouse move, entering the viewport, form submit, or a responsive breakpoint change) runs an effect on it: toggle its visibility, scroll to it, or mirror the mouse for a parallax feel. Agents discover the available triggers and effects and set them per module, and the module stays editable in the Divi builder.
- Tweak: Divi 5 pages that AI agents build and style stay editable in the Divi builder. Agents style through Divi's native module settings, global presets, colors, and variables in a clear order, so a page opens and edits normally in Divi rather than relying on custom CSS. When an agent writes page content, the page stays marked as a Divi builder page, so its layout is preserved the first time it is opened for editing.
- Tweak: When an AI agent edits an Elementor page, only that page's compiled CSS is refreshed. Other pages keep their cached styles and any open editor canvas stays intact, and the site skips a full site-wide CSS recompile on every edit.
- Tweak: AI agents building pages with GenerateBlocks now confirm the finished page renders with its styles before treating the work as done, since GenerateBlocks generates the page CSS from the blocks.
- Fix: Elementor v4 Global Classes that AI agents create or edit now show their base styles as explicitly defined on the desktop class controls in the editor, the same way classes made by hand do. Agents write the base style variant with the "desktop" breakpoint the Elementor editor expects, so the values read as set on the class and stay easy to maintain in the Elementor UI.
- Fix: Breakdance color variables, global classes, and global settings that AI agents create or edit are now saved in Breakdance's native format, so they load correctly in the builder and stay editable in Breakdance's own design-system UI. Tokens saved by an earlier version are still read correctly and rewritten cleanly on the next change.
- Minor fixes
v1.6.0
- New: Novamira Visual support for Elementor and Bricks. Novamira Visual is the new live browser workspace in the free Novamira plugin where you watch your AI agent work on your site in real time. Inside it, AI agents can now build and edit Elementor and Bricks pages right in the open editor, so you watch the work happen. This is an early, experimental integration, separate from the standard Elementor and Bricks specializations, so the output is different. For development and staging sites. We would love your feedback in the community group: https://www.facebook.com/groups/novamira
- Minor fixes
v1.5.0
- New: Contact Form 7 specialization (requires Contact Form 7 5.8+). AI agents can list, read, create, edit, duplicate, and delete contact forms, and have a built-in reference of the Contact Form 7 form-tag syntax so they author fields correctly. Submitted entries are not included, because Contact Form 7 does not store them.
- New: WPForms specialization (Lite and Pro, requires WPForms 1.8+). AI agents can find forms, create and edit forms and their fields, and manage notifications and confirmations. With WPForms Pro they can also read and manage form entries.
- New: Gravity Forms specialization (requires Gravity Forms 2.7+). AI agents can find forms, create and edit forms and their fields, manage notifications and confirmations, and read and manage entries.
- New: Fluent Forms specialization (free and Pro, requires Fluent Forms 6.0+). AI agents can create and edit forms and their fields, manage form settings, notifications, and confirmations, and read submissions. With Fluent Forms Pro they can also work with payment transactions, subscriptions, draft submissions, and quiz reports.
- New: Formidable Forms specialization (free and Pro, requires Formidable Forms 6.0+). AI agents can create and edit forms, fields, and entries, manage notifications and form actions, and work with form styles. With Formidable Pro they can also read application data and Stripe payment information.
- New: Ninja Forms specialization (requires Ninja Forms 3.13+). AI agents can find, create, edit, duplicate, and delete forms, manage their fields and notifications, and read and delete submissions. Ninja forms can also be migrated to and from the other supported form plugins through the shared form format.
- New: Form migration playbook. A guided, confirmable workflow that helps AI agents move a form's structure from one supported form plugin to another, for example from Contact Form 7 to WPForms, using a shared form format as the common ground. It works across Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Formidable Forms, and Ninja Forms. It covers the form structure only, not submitted entries.
- Fix: Meta Box specialization. Custom taxonomies created or edited by an AI agent are now attached to the post types it specifies, so they appear on the post edit screen and can be queried on the front end. The abilities store and read the post-type link the same way Meta Box's own registrar does, and reading a taxonomy back reflects its real attachment.
- Fix: Meta Box specialization. AI agents can now create, edit, and delete Meta Box relationships that connect your content, and the relationships are saved and stay editable in Meta Box, just like ones set up by hand. This applies when the Meta Box relationships builder is available.
- Tweak: Etch specialization. AI agents can now put hover and focus effects, responsive (mobile) styles, and rules for nested elements into an element's own class styles in Etch, so the whole design stays editable in Etch instead of in a separate global stylesheet. Agents can also create many class styles in one go, which makes styling a full page practical.
- Minor fixes
v1.4.1
- Tweak: Elementor pages and templates edited by AI agents now show their changes on the front end even with Elementor Pro's element cache enabled. When reading a page or template the agent can see whether a live element cache is in effect and when it expires, and it can clear the rendered-element cache for one or more documents, including nested templates (which cache independently), so a content or dynamic-data edit takes effect on the next view.
- Tweak: Bricks global variables created by AI agents now stay individually selectable in the Bricks editor. Agents create and edit them, along with the color palette, classes, and theme styles, through Bricks' own design-system tools, which give each entry a unique internal id, so selecting a variable in the editor affects only that variable.
- Tweak: Etch pages built by AI agents now keep their class-based styling editable in Etch. When an agent puts a class on an element that has a matching per-class style record, the abilities connect the record to the element, so the styling shows on the front end and stays editable in Etch's style editor.
- Fix: The two Bricks tools an AI agent reads first when building a page, the setup check and the theme-styles list, now declare a parameter in their input schema, so the agent can always call them.
- Fix: Bricks layout elements (section, container, block, div) built by AI agents are now stored the same way as the ones created in the Bricks builder, so Bricks and its builder add-ons handle them the same way. The page renders exactly as before.
- Fix: Code Snippets specialization. When an AI agent edits an active PHP snippet whose new code fails Code Snippets' on-save validation, the result now flags the snippet as deactivated and includes the validation error, so the agent sees why it went inactive and can fix the code or re-enable it.
- Minor fixes
v1.4.0
- New: Beaver Builder specialization (requires Beaver Builder 2.9+). AI agents can build and edit Beaver Builder pages end to end: the row, column, and module tree with native module settings and styling, query loops through the native Posts modules, and Beaver Themer theme layouts and dynamic data. They can also manage the site's Global Colors and global typography, and save and reuse templates, rows, and modules.
- New: JetEngine specialization. AI agents can now create, list, edit, and delete JetEngine custom post types, registered through JetEngine, so a type shows up under JetEngine → Post Types and behaves as a normal WordPress post type, letting an agent scaffold a content type and then fill it with posts (requires JetEngine 3.8.6.2+).
- Tweak: Etch pages built by AI agents now keep their styling editable inside Etch. Agents can create, edit, and delete the per-class CSS records that Etch surfaces in its style editor (the ones shown when you select a class on an element), so the section, component, button, and text styling lives on the element's own class records, editable in Etch's style editor (requires Etch 1.4.19 or newer).
- Tweak: AI agents can now use Divi 5's design system and advanced building features. They can create and reuse global module presets (and set per-module-type defaults), manage the brand color palette and reusable design variables (tokens for spacing, sizes, and more), set the site's global fonts, show or hide modules with display conditions, build Theme Builder templates (custom headers, footers, and body/archive/404 layouts) and control where they apply, and save sections, rows, modules, or whole pages to the Divi Library to reuse across pages, including live-linked Global items that update everywhere when edited. They can also set each module's advanced options (CSS ID and class, link, column gutter, text-shadow), and have clearer guidance for building query loops. Brand colors and tokens bind to modules through CSS variables, so changing one restyles every element that uses it.
- Fix: Disconnecting one item from another in a JetEngine relation via an AI agent now removes the link reliably.
- Fix: Bricks pages built by AI agents can now reliably show JetEngine values on native Bricks elements. JetEngine's dynamic tags appear when the agent lists Bricks' dynamic data, and the agent is pointed to the tag that renders correctly (applies when both Bricks and JetEngine are active).
- Fix: Etch pages edited by AI agents now keep an element's class (and any other HTML attributes the agent did not resend) when the agent changes just one attribute, so class-based styling keeps applying. Untouched attributes are preserved.
- Fix: Divi 5 rows with several columns built by AI agents now display their columns side by side. Laying out a row with multiple columns (a feature grid, stat counters, pricing tiers) produces an even multi-column layout automatically, and adding or removing a column rebalances it; deliberately uneven column widths are honored when set explicitly.
- Minor fixes
v1.3.1
- New: SeoPress and SeoPress Pro specialization (requires SeoPress 8.0+; redirects and structured-data schema require SeoPress Pro). AI agents can read and set the SEO of any page, post, category, or tag (the SEO title, meta description, canonical, and search-results visibility), and read your site-wide SEO settings. On SeoPress Pro they can also manage redirects and per-post structured-data schema.
- Tweak: Etch custom fields filled in by AI agents now show on the page immediately. Agents can set the per-post values of Etch's native custom fields, not just create the field definitions, so a value appears right away instead of only after the post is opened and saved in the Etch editor (requires Etch 1.5.0 or newer; older Etch is unaffected).
- Tweak: Etch custom fields created by AI agents can now use the date, time, and select (dropdown) types, in addition to text, textarea, number, and boolean (the three new types require Etch 1.5.0 or newer; on older Etch only the original four are offered, so nothing breaks).
- Tweak: Mosaic pages built by AI agents now stay inside the theme's design system, reusing utility classes and color and font variables instead of hardcoding colors and fonts as one-off custom CSS, and the agent can check its own work and correct anything that drifted outside the design system before finishing.
- Fix: Mosaic pages edited by AI agents now keep an element's existing styling when the agent updates just one part of it. A partial edit used to overwrite the whole element, wiping the classes, colors, fonts, and other settings the agent did not resend, and the same could reset a theme's global settings such as its font and spacing. Untouched settings are now preserved.
- Fix: Divi 5 pages built by AI agents now open in the Divi builder without being wiped. The agent marks the page as builder-built, so the first time it is opened Divi no longer runs its classic-content conversion, which used to replace the layout with an empty placeholder and set the original content aside.
- Fix: Divi 5 modules now display the dynamic content (such as the post title) that AI agents bind to a structured field, like a Blurb's title, instead of coming out blank, because the value is now placed in the field's text where Divi reads it.
- Fix: Elementor v4 global classes created by AI agents now show up styled in the editor itself, not only on the live page. They were written for the front end only, so opening the page in the Elementor editor could load slowly and unstyled with raw class ids showing; the classes are now mirrored into the editor's own context the way the Elementor editor does.
- Fix: Elementor v4 pages no longer fail to save when AI agents set an HTML anchor (CSS ID) on a section. The value used to be stored in a shape the editor rejected on Publish ("_cssid: invalid_value"), so the whole page could not be saved at all, even for unrelated edits; it is now stored as the plain string Elementor expects, and the same setting also works when an agent builds the layout in one pass.
- Fix: Elementor Global Color and Global Typography presets deleted by AI agents are now actually removed. The action used to report success while the entry stayed in the site's Elementor Kit and kept appearing, because the saved list was merged rather than replaced; deletions now persist.
- Minor fixes
v1.3.0
- New: Yoast SEO and Yoast SEO Premium specialization (requires Yoast SEO 21.0+; redirects require Yoast SEO Premium). AI agents can read and set the SEO of any page, post, category, or tag: the SEO title, meta description, focus keyphrase, canonical, social sharing preview, and whether it appears in search results, with the indexing choice always applied the right way so a page is never accidentally hidden from or forced into search results. They can also read your site-wide SEO settings, and on Premium create, edit, and remove redirects, including regex patterns.
- New: Rank Math SEO specialization (requires Rank Math 1.0.200+). AI agents can read and set the SEO of any page, post, category, or tag: the SEO title, meta description, focus keywords, canonical, cornerstone, social sharing preview, the schema type, and whether it appears in search results, with the indexing choice always applied the right way so a page is never accidentally hidden from or forced into search results. They can also read your site-wide SEO settings.
- New: All in One SEO specialization (requires All in One SEO 4.0+; term SEO and redirects require All in One SEO Pro). AI agents can read and set the SEO of any page, post, category, or tag: the SEO title, meta description, focus keyphrase, canonical, social sharing preview, cornerstone content, the schema type, and whether it appears in search results, with the indexing choice always applied the right way so a page is never accidentally hidden from or forced into search results. They can also read your site-wide SEO settings, and on Pro create, edit, and remove redirects, including regex patterns.
- Tweak: Custom instructions are now provided by the base Novamira plugin, with a Pro fallback only for sites that have not updated Novamira yet.
- Tweak: Bricks pages built by AI agents now stick to native Bricks elements and reusable global classes instead of reaching for raw Code elements or scattered, hard-to-edit custom CSS, and a raw code/HTML element is no longer added on its own during a build — using one now takes a deliberate, explicit opt-in.
- Minor fixes
v1.2.1
- Tweak: Breakdance pages built by AI agents now come out properly styled, because the agent can discover the available elements and their design controls instead of leaving them unstyled.
- Tweak: Breakdance pages can now be built or fully replaced by AI agents in a single pass, with element names validated and auto-corrected as the page is written, so a page comes out complete and editable instead of as a blank canvas or with "Missing Element" placeholders.
- Fix: Breakdance pages built by AI agents now place the correct elements (sections, columns, headings, the modern Image, query loops) instead of failing with "This element is missing" on the canvas, and no longer fall back to the deprecated Image V1. A mistyped or wrong-cased element name is auto-corrected, or rejected with a suggestion, so a page no longer ships broken.
- Fix: Breakdance template visibility conditions set by AI agents no longer corrupt the Breakdance Templates screen, and conditions configured in the Breakdance editor are now read back correctly instead of appearing empty.
- Fix: Breakdance templates built by AI agents can now be scoped to a custom post type, not just the built-in ones, because the right template type for each post type is now discoverable.
- Fix: Bricks pages built by AI agents now render Media Library SVGs and inline-code elements that previously saved but came out blank (inline code still requires Bricks code execution to be enabled, and the agent is now told clearly when it is off), and query loops on layout containers (block, div, section, container) no longer raise a spurious validation warning.
- Fix: Bricks theme styles built by AI agents now flag a setting placed outside its group, which previously saved but produced no styling, so the mistake is caught instead of silently doing nothing.
- Fix: Bricks pages edited by AI agents now keep every section's existing layout order. A change to one section no longer silently reorders the contents of other, untouched sections.
- Fix: Elementor pages built by AI agents in the new v4 editor now correctly attach Global Classes to an element, instead of producing a state the editor rejected with "classes: invalid value" when you went to save the page.
- Fix: ASE (Admin and Site Enhancements) Pro specialization. Custom field groups created by AI agents now register correctly with ASE, so their fields read and write values immediately, instead of the group saving but every field coming back empty.
- Minor fixes
v1.2.0
- Important: requires Novamira 1.6.0 or newer.
- New: Etch specialization (requires Etch 1.4.19+). AI agents can build and edit Etch pages end to end: element tree, reusable components, templates, loops, conditional visibility, dynamic data, and global styles, plus Etch registered post types, taxonomies, and custom fields.
- New: Divi 5 specialization (requires Divi 5.0+). AI agents can build and edit pages on Divi's new block based engine: module tree, sections and modules, design options, and loops over CMS content.
- New: Breakdance specialization (requires Breakdance 2.7+). AI agents can build and edit Breakdance pages: element tree, element and page settings, query loops, templates, and global blocks.
- New: Mosaic specialization (requires Mosaic 1.0.3+). AI agents can build and edit Mosaic pages end to end: element tree, loops, and the builder's design system.
- New: WPBakery Page Builder specialization (requires WPBakery Page Builder 6.5+). AI agents can build and edit pages end to end: element tree (including grid items), custom CSS, page settings, and templates with append, prepend, and replace modes; they can also register custom WPBakery elements.
- New: GeneratePress specialization (requires GeneratePress 3.0+; some abilities also need GenerateBlocks or GP Premium 2.0+). AI agents can build pages with GenerateBlocks and manage GeneratePress global styles and design tokens, with query loops for CMS content.
- New: Kadence specialization (requires the Kadence theme 1.2.0+). AI agents can build pages with Kadence Blocks and manage Kadence theme design settings.
- New: WooCommerce specialization (requires WooCommerce 9.0+). AI agents can discover and manage your catalog end to end: list and read products with rich filters, create and edit simple and variable products and their variations (pricing, stock, SKU, dimensions, images), organize categories, tags, global attributes, and shipping classes, and read store settings. Force deletes cascade safely to variations and attribute references.
- New: Code Snippets and Code Snippets Pro specializations (requires Code Snippets 3.6+). AI agents can list, read, create, edit, activate, deactivate, and delete PHP, JavaScript, CSS, and HTML snippets.
- Minor fixes
v1.1.2
- Fix: Meta Box specialization. Field groups created or edited by AI agents now open correctly in the MB Builder admin editor, with all choices on select / radio / checkbox-list / advanced-select / autocomplete fields preserved regardless of whether the agent supplies them as a `{value: label}` map or as a list of `{value, label}` objects. The list form used to collapse to a single empty-keyed entry in storage, hiding every choice except the last one.
- Tweak: Meta Box specialization. AI agents now detect which Meta Box extensions are installed (term meta, comment meta, user meta, group field, custom table) and refuse operations that would silently no-op without the right extension, naming which one is missing. When custom-table storage is in use, the agent is told to warn you that reads and writes through this integration do not address the custom table.
- Minor fixes
v1.1.1
- Fix: Elementor's Site Settings typography set by AI agents now scales smoothly with the screen size. Responsive sizes like `clamp()` used to be flattened to a single fixed value.
- Fix: Elementor v4 Global Variables of type "size" now accept fluid CSS expressions (`clamp()`, `calc()`, `min()`, `max()`, `var()`) when AI agents create or edit them, so fluid design tokens can live in one place instead of being inlined into every style that uses them.
- Fix: Bricks global classes set by AI agents now support the `%root%` placeholder in custom CSS, matching the Bricks editor convention. Custom CSS rules that used to be silently dropped now render correctly.
- Tweak: Bricks pages, theme styles, and global classes built by AI agents now follow the conventions a human would use in the editor: typed controls instead of opaque CSS, the conventional section > container > block-level nesting on content sections, and the semantic `p` tag for body text. Theme styles and classes built this way stay editable from the Bricks UI.
- Tweak: Bricks pages built by AI agents now use a Query Loop for sections that show repeated CMS content (blog grids, portfolio listings, services, team members, rentals, anything you manage from the WordPress admin), so the section updates as you add or edit entries. Static cards are still used for fixed UI sections like pricing tiers, feature pillars, and hero blocks.
- Tweak: Elementor pages built by AI agents now use a query widget for sections of repeated CMS content (blog grids, portfolio lists, services, team members, rentals, anything you manage from the WordPress admin), so the section updates as you add or edit entries. Works with Elementor Pro's Loop Grid or Posts widget, or third-party query widgets. Static widgets stay for fixed UI sections like pricing tiers, feature pillars, and hero blocks.
- Minor fixes
v1.1.0
- New: ACF specialization. AI agents can manage field groups and read and write field values on any post, user, or term (requires ACF 6.5+). With ACF Pro, also post types, taxonomies, and options pages registered through ACF.
- New: JetEngine specialization. AI agents can manage JetEngine meta boxes, options pages, and Custom Content Types (both the type definitions and the records inside them), with a dedicated workflow skill that activates when agents work on JetEngine (requires JetEngine 3.8.6.2+).
- New: Meta Box specialization. AI agents can manage field groups, custom post types and taxonomies, settings pages, and relationships, and read and write field values on any post, user, term, comment, or settings target. Includes a dedicated workflow skill (requires Meta Box 5.11.2+).
- New: Pods specialization. AI agents can model and populate Pods-defined Custom Post Types, Taxonomies, Advanced Content Types, Settings Pages, fields, groups, and items (requires Pods 3.2.1.1+).
- New: ACPT (Advanced Custom Post Types) specialization. AI agents can manage ACPT custom post types, taxonomies, meta groups, and option pages, and read and write field values on posts, terms, users, and option pages. Includes a dedicated workflow skill (requires ACPT 2.0.52+).
- New: ASE (Admin and Site Enhancements) Pro specialization. AI agents can manage custom field groups, custom post types, and custom taxonomies, and read and write field values on posts, terms, and options pages. Includes a dedicated workflow skill (requires ASE Pro 8.7+).
- New: AI agents now reason about post types, fields, taxonomies, options pages, and relationships using a shared vocabulary, so the way they talk and work stays consistent no matter which field plugin is in use.
- New: AI agents now have a guided workflow to follow when asked to move content from one field plugin to another.
- New: AI agents are now reliable at filling in Bricks dynamic data and Elementor dynamic tags from your field plugins, so widgets show the actual field value instead of literal text or an empty result.
- Minor fixes
v1.0.0
- New: "Novamira feedback" skill. When you ask the agent to share feedback on a Novamira tool (something that didn't behave as expected, an unclear result, a friction point), it composes a sanitized English report with no personal data, content, keys, or URLs, that you can review and send to Novamira support.
- Tweak: Bricks pages built by AI agents now reuse your site's existing styles instead of typing colors, sizes, and spacing into every element. Before adding anything the agent checks what's already there (Bricks variables, global classes, palette colors, theme styles), sets up only what's missing once, and uses those by name in the page. Change a color or a spacing value later and every page that uses it updates automatically.
- Tweak: AI agents now produce cleaner widget content in Elementor. Headings, buttons, and other text widgets get plain text instead of accidentally embedded HTML; rich-text widgets get only inline formatting (bold, italic, links); layout (alignment, width, typography, spacing) flows through each widget's own controls. The HTML widget remains the place for free-form HTML.
- Fix: Bricks header/footer templates built through Novamira Pro abilities now save their elements in the right area, so the Bricks editor shows them instead of opening empty.
- Fix: Building responsive Elementor pages through AI agents now works end-to-end. Asking the agent for tablet or mobile font sizes, padding, alignment, etc. used to silently produce only the desktop value, because the per-breakpoint values were rejected before reaching Elementor. They now persist and render in the right media queries.
- Fix: Elementor pages built by AI agents now produce readable class names on sections that have a natural name (hero, footer, pricing card), so the rendered HTML and CSS are inspectable in DevTools and stylable from custom CSS.
- Fix: The local-style chip in the Elementor editor for elements built by AI agents now shows "local" (matching Elementor's native convention), instead of a cryptic auto-generated id.
- Fix: When Elementor's Atomic Widgets experiment is turned off, the setup check now reflects that correctly and the agent falls back to the legacy widgets, instead of being told the atomic path is available and failing halfway through.
- Minor fixes
v1.0.0-rc1
- Fix: WordPress plugins page showing an update even if no update was present
- Fix: Elementor content reads now count all elements in the page tree, including children nested inside containers.
- Tweak: Clarify Elementor schema guidance to avoid broad style control dumps when narrower reads are enough.
- Minor fixes
v1.0.0-beta1
- 🎉 First release!