WordPress Plugins Meet AI, Permissions, and Ecosystem Turbulence

Ben cohen

If I see one more plugin clutter my dashboard with a giant promo banner and six submenus, I, I, I might actually lose my mind. Nobody is clicking those anymore!

Nick d

Uh, amen to that. In late 2026, if your plugin relies on a human spending twenty minutes clicking around wp admin, you've already lost.

Ido

Right, because site managers are using terminal agents and AI clients to do the work now. It is all about how easy you make it for an AI assistant to read and edit your site.

Nick d

And that is exactly why the WPCodeBox 1.4.0 update is a complete game changer. They added native Model Context Protocol access, but they built it with a real permission ladder.

Ben cohen

Wait, what do you mean by a permission ladder?

Nick d

So, by default, the MCP tools are strictly read only. An AI agent can inspect your snippets, but if it wants to write code or execute PHP, an administrator has to explicitly opt in. It, it, it draws a clean line between discovery and execution.

Ido

That is huge for AI visibility and safety. And look at wpDataTables 8.0 with their AI First update. They exposed REST API endpoints and direct MCP integrations so agents like Angie can just query your database tables or generate SQL directly.

Ben cohen

Yeah! You do not even touch the table builder UI anymore. The AI asks for the schema, gets the endpoint, and renders the chart. It is seamless.

Nick d

Hold on though. Seamless is great, but SEOPress 10.2 just added an AI assistant step right into their initial setup wizard, and I am a little skeptical.

Ben cohen

Skeptical? Why? Lowering friction during onboarding is how you get people to actually use these AI capabilities!

Nick d

Because prompt shortcuts during setup can lead to accidental write permissions before a site owner even understands what data the agent can modify! We need guardrails, not just instant access.

Ido

It is that balance between friction free AI discovery and tight server governance. But speaking of governance...

Ido

We have to talk about what just happened on the ecosystem side. The governance landscape is shifting under our feet.

Ben cohen

Oh man. You mean the news from 404Media?

Ido

Exactly. Samantha Cole from 404Media reported that Automattic CEO Matt Mullenweg was put on a Leave of Absence from Automattic.

Nick d

Yeah, and right after that news broke, Matt was publicly posting hiring calls to migrate core infrastructure off Automattic servers. I mean, talk about volatility at the very top.

Ben cohen

It is wild, but what impresses me is how the core developer community is responding. Look at David Perez proposing automated security reviews for all official repository releases.

Nick d

Right. While executive leadership is in turmoil, the technical foundation in the WordPress 7.1.1 cycle is actually hardening.

Ido

So here is my question for you, Nick. Given all this instability, should plugin creators and agencies be actively decoupling their tools from Automattic adjacent services entirely?

Nick d

I think smart buyers already are. In 2026, serious agencies are moving away from fragile, unmaintained utility scripts. They are putting their money into deeply maintained, self contained, zero trust platforms like Melapress for security or FluentCart for commerce.

Ben cohen

Because when the ecosystem shakes, you want software that owns its entire stack and exposes clear, secure APIs.

Nick d

Precisely. Clean code, strict permissions, and zero external drama. That is how you win today.

Ido

Well, on that note, let us keep building. Good chat, guys.

Ben cohen

Talk soon, everyone.