Human Made: WordPress isn’t “adding AI features” — it’s becoming an agentic platform
Most AI-in-CMS conversations start in the shallow end: “what’s the chatbot?” “where’s the content generator?”
In a Human Made essay, the argument is basically the opposite: the defining shift for WordPress in 2026 isn’t a single AI feature — it’s the foundation that lets *capabilities compound* over time.
Their framing is: WordPress is moving from CMS to agentic platform, with the Abilities API as the mechanism that makes plugin functionality legible to automation and agents — and governance/permissions as the thing that makes it viable for real teams.
The piece:
The practical takeaway
If WordPress can standardize “what a site can do” (capabilities) and “who/what is allowed to do it” (permissions), AI stops being a sidebar feature and becomes an orchestration layer.
The interesting part isn’t whether the first wave of agent UX is perfect — it’s whether the ecosystem converges on shared primitives instead of 10,000 bespoke integrations.
Embed
WordPress: From CMS to agentic platform (Human Made)
Why this matters for the ecosystem
If you buy the thesis, the “win” isn’t a single AI feature. It’s a world where plugins advertise capabilities in a common way, and automation can use those capabilities without every plugin shipping its own bespoke integration layer. That’s the kind of platform shift that takes years — and it starts with boring primitives.
If you’re curious where this connects back to real product work, pay attention to anything that makes abilities discoverable, permissioned, and auditable. That’s the difference between “suggestions in a UI” and systems that can safely execute work in the background.
Discover more from WP Snaps
Subscribe to get the latest posts sent to your email.
