Native AI Agents Are Taking Over WordPress Admin

Nick d

So I was looking at LolaCore yesterday, and it, it, it completely blew my mind because instead of hooking up some external Model Context Protocol server over a terminal, it literally lets you build plugins inside WP Admin. It is built on the WP 7.0 AI Client and the Abilities API, which means it sits right inside your dashboard, inspecting databases and running admin tasks directly.

Ben cohen

Wait, build plugins inside WP Admin? Without having to spin up a terminal or connect Claude Code through an external bridge?

Nick d

Exactly. No external middleware needed. The agent uses the native AI Client in WordPress 7.0 to read your site context, generate code, and execute it, but only after you give explicit approval right there in the interface.

Ido

That shift from external terminal agents to native dashboard prompts is huge for AI visibility and ease of use. When you look at tools like Altus AI, they are doing something similar for niche plugins like WP Travel Engine. They route over 350 AI models through OpenRouter directly into the booking dashboard.

Ben cohen

350 models through OpenRouter? So a tour manager can literally just type, um, lower the price on the weekend safari and issue a ten percent coupon, without touching three different settings menus?

Ido

Yes, exactly that. You bypass all those deeply nested admin screens. You just talk to the site in natural language, and the underlying model translates that intent into precise database changes.

Nick d

I have to say, as a builder who hates friction and clutter, having a native prompt bar inside the dashboard feels so much cleaner than managing API keys and external CLI connections. But, um, I do wonder if built in core APIs are going to make external MCP tools completely obsolete for the everyday site owner.

Ben cohen

Well, I think for casual users, absolutely. Why mess with terminal commands when WordPress core gives you a native connection? But for developers doing massive multi site refactoring, external CLI tools might still hold a place. The key question is control and security when these agents start making live site decisions.

Ido

And that brings us right to how these agents operate safely when given real authority over a production site.

Ido

That issue of safety is precisely what Agentric AI is tackling. They run autonomous WordPress agents, but they build strict human in the loop guardrails directly into the execution path. So an agent cannot just run rogue database queries or trigger site breaking plugin updates without a human approving the action plan first.

Ben cohen

Human in the loop guardrails, right. Because nobody wants an AI agent trying to optimize a database at three in the morning and accidentally dropping primary keys or creating massive plugin conflicts on a live e-commerce site.

Nick d

Yeah, absolutely. And it is not just backend database tasks that are turning conversational. Look at what Frontman is doing on the front end. It applies natural language instructions directly to live page previews. You literally point at a section in a real time visual canvas and tell it to adjust spacing or change layout logic, and it updates right in front of you.

Ido

That changes the visual dynamic entirely. When an AI agent can read the visual layer and interpret live previews like Frontman does, you move far beyond the old block editor. You are effectively conversing with your design system.

Ben cohen

So if LolaCore builds plugins inside WP Admin, Agentric AI handles backend maintenance under guardrails, and Frontman handles visual design through live previews, what happens to traditional agency retainers in 2026? Are client maintenance plans totally dead?

Nick d

I, I, I do not think retainers die, but the actual work shifts completely. Developers will stop spending hours manually configuring plugins, running basic updates, or fixing broken CSS layouts. Instead, our role becomes acting as supervisors for autonomous agents. We set the parameters, review the proposed changes, approve the deployment, and handle edge cases.

Ido

It transforms the developer into an orchestrator. Instead of clicking through twenty plugin settings screens, you supervise native agents that understand the site structure, respect security guardrails, and execute tasks in seconds.

Ben cohen

That is a massive leap forward for site management. Alright, good chatting, talk soon!