Changelog
What's new in Novamira.
Release notes for Novamira and Novamira Pro.
v1.2.0
Latest- 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.1.1
Latest- 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!