The most interesting part of AI app builders is not that they make code faster. It is that small, specific software is suddenly worth building. A tool that would have been too small for an agency quote and too weird for a SaaS roadmap can now exist. The new bottleneck is where those little tools live, who owns them, and how they keep working after the first version ships.

A lot of vibe-coded tools hit the same wall after the first demo works. Where does it live? Who can update it? How do permissions work? What happens when a non-dev needs to change the content? That is the gap DesignSetGo Apps is built around: ship the app, but let WordPress stay the place where the site already runs. designsetgo.dev

Website updates shouldn't require digging through settings. With Airo for WordPress, you can change designs, update images, and adjust your messaging simply by chatting. Your site evolves as you go. Try it for free! 👇 social.godaddy/Airo-for-Word…

Justin Nealey explains how WordPress 7.0 introduces three load-bearing APIs, Connectors, WP AI Client, and the Abilities API, that together change what a plugin is allowed to assume. →x.com/Justinnealey/status/20… (h/t:@wpcontent_co)

AI builders often treat WordPress like old hosting with a weird admin UI. That misses the useful part. WordPress already has users, roles, content, media, commerce, editorial workflow, and a place non-devs understand. Use it as the runtime, not the thing to route around. designsetgo.dev/blog/what-ai…

DesignSetGo Apps 1.3.0 is live. The install flow is much cleaner now: Upload HTML, Markdown, or a zip bundle from one place. Browse example apps and install one with a click. Use an AI prompt or deploy from the CLI when you need more control. My favorite part: Markdown files are now standalone WordPress apps. Drop in a .md file and it becomes a styled, sandboxed iframe app with CSP-safe rendering and no external requests. Also shipped: better zip handling, source tagging for Claude, Lovable, v0, and Bolt artifacts, plus MCP discovery metadata for app-published abilities. designsetgo.dev

Most AI coding demos stop at generated files. DesignSetGo Apps is the next step I wanted for WordPress: upload a static HTML, CSS, and JS app bundle, run it in a sandboxed iframe, and connect it to WordPress through a permissioned bridge. The free version is live here: designsetgo.dev

Plugin #25 is live and this one is what the plugin management experience should look like in #WordPress. 🪄 Bulk upload plugins, bulk toggle de/activations, download plugins and bundles, and a lot more! wellplayedwp.com/plugins/plu…

“Create a page for my portfolio.” That’s all it takes to update your website with Airo for WordPress. Add new pages, create new sections, and refine your content — all by chatting. No blank pages. No writer's block. See it in action 👇 social.godaddy/Airo-for-Word…

I keep thinking about the gap between AI generating a working mini app and WordPress actually having a safe place to run it. Static builds are not the problem by themselves. The missing pieces are isolation, permissions, versioning, and a way for the site owner to know what is running.

Claude Code is much better at WordPress when it can see the boring parts. Plugin structure, hooks, REST endpoints, theme files, wp-env, tests, the exact error. The weaker workflow is asking for a beautiful site. The stronger workflow is giving it one small job and forcing it to prove the change.

The more I build around WordPress and AI, the more convinced I am that the agent should never need god mode. Give it a small capability, a clear user context, an audit trail, and an obvious rollback path. That is how this moves from fun demos to tools site owners can actually trust.

I built a thing. And I actually shipped it. :) I'd be honored if you checked it out. I'll also suggest registering as a user (free of course) and exploring the features and user experience. More on the "why" and my "getting back to building again" journey to come.

Missed the livestream, the kiddos were being wild but always a fun time with @PluginJam_WP blockathons!

Visual feedback is the wall. Agents can generate interfaces quickly, but if the loop cannot see the actual screen, layout bugs become expensive. Browser checks and screenshots should be first-class in vibe coding workflows. x.com/nathanael_smith/status…

Vibe coding gets dramatically better when the system around it is boring. Types, tests, screenshots, deploy previews, permission boundaries, rollback. The prompt is the fun part. The harness is what lets you trust the output. x.com/enunomaduro/status/205…

How does @GoDaddy use AI for technical support? This week on WP Product Talk, @Drewbewilde from GoDaddy joins us to talk about AI-powered WordPress troubleshooting, customer trust, & where support workflows are headed next. Join us Live today at Noon EST wpproducttalk.com/podcast/si…

Static builds are a really good shape for WordPress tools. They are portable, easy to inspect, and cheap to host. The missing piece is the bridge: a safe way for that bundle to read the site data it actually needs without becoming a full-trust plugin.

AI in WordPress is becoming infrastructure now. The interesting problem is not how to generate code. It is where that code can safely live, what it is allowed to touch, and how a site owner can revoke that access later.