Builderius & Builderius Pro 1.4-beta Release Notes

Sense AI 2.0: Use the AI Client You Already Have

Sense AI has been rebuilt in 2.0. In 1.3.6, Builderius installed an AI agent onto your computer and ran it for you, driven from a panel inside the builder. That is now inverted. Builderius exposes itself over MCP to the AI client you already use, and the conversation happens there.

Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Zed, Antigravity CLI, Codex CLI, Codex Desktop, Grok Build, Kimi Code and OpenCode all work, in your own client. Keys and subscriptions stay yours, as they were before.

Output is ordinary Builderius: regular elements, regular classes, regular queries. Nothing is locked to the AI, and any of it can be edited or deleted by hand.

This release also contains the largest set of bug fixes we have shipped, including a fatal error that could take down wp-admin.

What Replaced What

Setups made under 1.3.6 do not carry over. You will need to connect again, and 2.0 will not clean up after the old version, so uninstall it first:

npm uninstall -g @builderius/sense-ai

This removes the terminal server and the files 1.3.6 placed on your machine. Nothing in the plugin depends on it any more.

Changed: Builderius no longer installs anything on your computer. The macOS and Windows installers, the terminal server and the login shells 1.3.6 started on your machine have been removed. The live editing connector is fetched on demand when your AI client starts and leaves nothing behind.

Changed: The AI panel inside the builder is gone. The conversation, the history, the choice of model and the subscription are your client’s.

Changed: You are no longer limited to the three bundled agents. Any AI client that speaks MCP can connect.

Two Ways to Connect…

Abilities: whole site, no browser

Added: 74 abilities, published over the WordPress Abilities API.

Your AI client calls the site’s MCP endpoint over HTTP, authenticated with the application password, and the abilities run inside WordPress. No browser is involved and no builder tab has to be open. It can create dozens of templates in one run, work across components that have never been opened, and run unattended.

This is the mode for scaffolding: converting a design into templates and components, building out section structure, restructuring site-wide, then committing and releasing.

Abilities are the only mode that can create and manage releases. Both modes can commit, but live editing asks you for permission every time, while abilities commit on their own. Everything else is available to both.

Live editing: the open builder tab

Added: 54 tools for working on an open builder tab.

Select an element and state what should change. Live editing is the only mode with the full context of the open templates, pages and components: your current selection, the computed styles, and the page as the browser rendered it rather than as the source describes it. That makes it the mode for precision work, and the only one that can report the result.

Builderius keeps several templates, pages and components open as tabs, so live editing is not limited to one of them. It sees every open tab, including those loaded in the background, which means an instruction can touch a template you are not currently looking at.

Setting It Up

Added: Redesigned Sense AI settings screen. Turn Sense AI on or off, and enable Live Editing, Abilities or both.

Select your client and the screen prints the configuration block for your site, the file to paste it into, and that file’s location on macOS and Windows. A second tab provides a prompt to paste into the AI so it edits its own configuration.

Changed: Local and remote sites use the same setup. There is no separate procedure.

Changed: Sense AI no longer writes its files into the WordPress root. You set the folder it works in, and the install stays clean.

Added: The screen creates the WordPress application password and reports whether the builder can authenticate, not only whether a password exists.

Added: Abilities require an MCP server to publish them. If none is present, the screen reports it and offers to install the WordPress project’s MCP Adapter plugin.

Added: Local HTTPS is handled automatically. Development certificates are accepted on names that can only mean your own machine (.test, .localhost, .local, .ddev.site and loopback), so live editing works on a local site with no configuration.

Added: The GraphQL schema, the elements reference and the CSS framework are served by the plugin, so every AI surface reads one authoritative copy instead of inferring field names.

Before You Connect an AI to Your Site

Of the 74 abilities, 25 read, 39 write and 10 delete: templates, components, releases, uncommitted changes. Most writes are immediate, with no confirmation step. The application password carries the permissions of your WordPress account.

Rollback is Builderius version control, not a prompt. Commit before running an agent, and afterwards you can restore the previous commit or discard uncommitted changes. Both are abilities, so instructing the agent to commit first is a valid opening step.

Requirements: a Builderius Professional licence, Node.js 20 or newer, and an AI client that speaks MCP.

Builder

Added: Close a builder tab with a middle click.

Added: Tab context menu with Close, Close Other Tabs and Close All Tabs.

Changed: Publishing now publishes the whole commit group instead of autopublishing each commit separately.

Changed: A save that skips a template, page or component now reports which ones were skipped and why, instead of reporting success.

Bug Fixes

Pro

Fixed: Fatal error during WordPress’s routine plugin update check, dropping the site into recovery mode. If the licence server’s response was not valid JSON (a firewall challenge page, a captive portal, an empty or truncated body), the plugin parsed it anyway, which is fatal on PHP 8 and a warning on PHP 7. It could trigger on an ordinary admin page load. Reported from the field on PHP 8.3.

Fixed: Static export shipped absolute paths inside the ZIP.

Fixed: Static site generation on Windows.

Free, front end

Fixed: Wrong post data on the front end. A template’s query loop did not restore the global post, so anything reading it afterwards saw the last post of the loop. This affected SEO plugins writing schema and Open Graph timestamps, and previous and next post links in a template. The loop can run while the head is being built, so the wrong post could differ between requests for the same URL.

Fixed: Component properties were parsed as template syntax, which broke the page on large properties and mangled accented characters.

Fixed: Backslashes in visibility conditions were not escaped, so a regular expression or path condition could change meaning or break the page.

Fixed: Dynamic data was not resolved in component property overrides.

Fixed: Inline JS snippets set to the header produced no script tag. External and footer snippets were unaffected.

Fixed: Collection elements rendered with no children when their context attribute contained encoded characters.

Fixed: Date archive location conditions, and several archive and extended condition functions.

Free, builder and saving

Fixed: A save could be silently discarded and still report success, losing the work. Staleness is now determined from what is actually stored, rather than from the editor’s own record of what had changed.

Fixed: Components did not appear in the editor after converting a group of elements into a component, until the page was refreshed.

Fixed: The Reload Canvas button had no effect.

Fixed: Choosing a different post in the preview dropdown kept showing the previous one.

Fixed: The preview dropdown could show another template’s pages, or none of the current template’s, until the editor was refreshed.

Fixed: Release descriptions lost their line breaks. A description containing a backslash or a Windows line ending produced an invalid request and the release failed to create.

Fixed: Dynamic Data and JS editor panel styling were mixed up.

Free, starters and release import

Fixed: Starter installation from the UI failed on sites using plain permalinks. Several addresses were assembled in a form valid only under pretty permalinks, and WordPress answered 404. This affected the starter and WP data wizards, the release push wizard and the static site wizard.

Fixed: Large starters could fail partway through installation, leaving a partial import. A full release import takes minutes, the Architecture Studio starter upwards of forty seconds on an idle machine, and exceeded PHP’s default thirty second limit. Imports now raise the time and memory limits.

Installation

Download from your account dashboard, and the free version from WP.org.

To connect an AI client, see the documentation, which includes step by step guides for the Claude Desktop and ChatGPT desktop apps.