Introduction
Pro Feature Sense AI connects your own AI client to your WordPress site, so you can build and edit Builderius templates by describing what you want. Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Zed, Antigravity CLI, Codex CLI, Codex Desktop, Grok Build, Kimi Code and OpenCode all work, and so does anything else that speaks MCP.
Sense AI is not a chatbot inside the builder. It is a connection: you keep using the AI app you already use, and it gains the ability to see and change your site.
The output is ordinary Builderius: regular elements, regular classes, regular queries. Nothing is locked to the AI, and you can edit or delete any of it by hand afterwards.
1.3.6 installed Sense AI onto your computer. 2.0 does not, and it will not clean up after the old version. Remove it before connecting:
npm uninstall -g @builderius/sense-ai
Your 1.3.6 configuration does not carry over either, so you will need to connect again.
Two ways to connect
Sense AI has two modes. They are not two options for the same job, they are two different jobs, and most projects use both.
| Abilities | Live editing | |
|---|---|---|
| What it is for | building and shipping the site | changing the thing you are looking at |
| Needs a builder tab open | No | Yes |
| How it reaches your site | straight to the REST API over HTTP | a connector on your machine, which the builder page connects to |
| Works while you are away | yes | no, you are watching it |
| Size of the toolset | 74 abilities | 54 tools |
Abilities: the whole site, at once
No browser is involved, so nothing has to be open. It can create dozens of templates in one run, work across every component on the site, including ones nobody has ever opened, and keep going while you do something else.
This is the mode for scaffolding a site: converting a design into templates and components, building out a section structure, restructuring site-wide, then committing and releasing the result.
Ask for things like:
Here is our design file. Create the templates and components for the home page, the blog listing and a single post.
Turn the card pattern in these three templates into one component and use it in all of them.
Commit everything as "home page rebuild" and publish the release.
Which templates use the Hero component?
Abilities are the only mode that can save and publish releases. Both modes can commit, but abilities commit on their own, while live editing asks you for permission every time. Anything else abilities can do, live editing can do as well.
Live editing: the thing you are pointing at
A builder tab is open and the AI can see it. That changes what you can ask for, because now "this" means something.
Select an element and say what should be different about it. Live editing is the only mode with the full context of what is open: 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 how something turned out.
It is not limited to one tab. The builder keeps several templates, pages and components open at once, and the AI sees all of them. Each one reports its state: active is the one in front, warm is loaded in the background. A warm tab can be worked on without switching to it, so an instruction can touch a template you are not currently looking at. The AI can also list what is open, switch between tabs, or open another template or component itself.
Work across several tabs is possible here too, such as making the footer match the header across two open templates, with one difference from abilities: everything involved has to be open. A cold tab, or something that was never opened, cannot be reached this way.
Ask for things like:
(with a section selected) Make this three columns, and stack it on mobile.
Why is this heading grey instead of using the heading colour?
Make this list pull the six most recent posts, with the featured image and category.
Check this page for accessibility problems.
Using both
The usual way to work:
- Abilities build the structure: templates, components, the bulk of the pages.
- Live editing refines it. You open a page, point at what is not right, and fix it while watching.
- Abilities save the commit and publish the release when you are happy.
What is written, and when
Live editing changes the canvas, not the database. Changes land in the builder as you watch and are not stored until saved. That is a chance to review, not a lock: save is one of the tools, so an AI can save without being asked. Builderius instructs agents never to save unprompted, but that is a convention agents follow, not something the connector enforces.
Most abilities write immediately. Call one that creates, updates or deletes and it has already happened, with no confirmation step. Of the 74 Builderius publishes, 25 only read, 36 write and 13 delete. The settings screen marks each one under What the client can do.
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.
Thirteen of them delete: templates, components, releases, uncommitted changes. The application password you create carries the same permissions your WordPress account has. Treat handing it to an AI client as granting that access.
What you need
- A Builderius Professional licence
- Node.js 20 or newer on your machine
- An AI client you already use. Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Zed, Antigravity CLI, Codex CLI, Codex Desktop, Grok Build, Kimi Code and OpenCode are supported, and so is anything else that speaks MCP
- A WordPress Application Password, which the settings screen creates for you
You do not need an API key from Builderius, and there is nothing extra to buy beyond the licence. Your client uses whatever AI subscription or key it already has.
Enable it
Go to Builderius → Settings → Sense AI in the WordPress admin.
1. Turn on "Connect AI clients to this site". Nothing can reach the site until this is on.
2. Create the credential. Sense AI needs a WordPress Application Password. The screen creates one and shows it once, so copy it before you leave the page. If you lose it, create another; application passwords can always be revoked under Users → Profile → Application Passwords.
3. Turn on the modes you want.
- Live editing has a Port setting, default
7681. One port serves every Builderius site on the machine, so you rarely change it. Whatever it says here must match the port in your client's config. - Abilities needs something on the site publishing them over MCP. If nothing is, the screen says so and offers to install the WordPress project's MCP Adapter plugin for you.
4. Copy the config for your client. Under Connect your client, pick your app. The screen prints the exact block to paste, the file to paste it into, and where that file lives on macOS and Windows. With both modes on, that one block contains both servers, and the application password from step 2 serves both.
5. Make a folder for the project and run your AI from there. Sense AI writes nothing into the WordPress directory, so the site stays clean. Pick a folder anywhere on your machine, put the config there, and start your AI client in it. Whatever the AI writes as it works, notes, plans, exported files, stays in that folder alongside the config.
6. Paste the config, replace YOUR-APP-PASSWORD, and restart your AI client. Clients read their MCP config at startup, so the server will not appear until you restart.
The Copy a prompt tab gives you instructions to paste into the AI itself, and lets it edit its own config, which is useful when you would rather not hunt for a file. The Paste config tab keeps your password out of the conversation, which is a good security measure, which is why it is the default.
Set up your client
Other clients work the same way. Pick yours from the AI client dropdown and the screen tells you where its config lives.