A promise on Reddit

A few days ago someone on r/Wordpress asked for a low-cost way to build a member directory for an alumni site. I left a comment: build it with SailWP, the Co-pilot can do it.

Then I went back to my own code to check, and realized it couldn't.

SailWP Co-pilot, the AI assistant inside the plugin I've been building, could do a lot of things. It could redesign a page, generate brand-appropriate images, draft a blog post, add a contact form. It had twenty tools at its disposal. None of them could install a plugin, configure it, or compose a feature like a member directory out of working parts. The Reddit comment I had just left, casually, was a promise the product couldn't keep.

I had a few options. I could walk it back, edit the comment, add an "actually, not yet" note. I could DM the user privately and apologize for the misdirection. I could quietly delete it and move on. None of those felt right. The person had asked an honest question and I had given a confident answer that wasn't true.

So instead I decided to make the answer true.

Agents and orchestrators

While I was working on this, a distinction kept showing up in my head. The word agent has become the catch-all for anything an AI does on your behalf. Drafts an email. Renames some files. Edits a piece of copy on a page. Those are real things and they're useful, but they're all the same shape: small, scoped, one tool at a time.

What this Reddit thread needed was something larger. Not "edit a thing." Compose a thing. Pick which tools, in which order, with which configuration, to produce a feature that didn't exist on the site before. Install the right parts. Wire them up. Style them so they don't look bolted on. Create the pages that go with it. Add the navigation. Seed it with realistic data so the user can see what they're working with before they touch anything.

That isn't an agent. That's an orchestrator. Same underlying machinery, an LLM choosing actions, but the unit of work is a feature, not a task. The difference is small in theory and very large in what it can produce.

What I actually built

The first instinct was the obvious one: have the AI install Ultimate Member, configure it through chat, and style it to match the user's site. That works, sort of. It also means the user ends up with a third-party plugin that has its own opinions, its own styling defaults, its own update cadence. If Ultimate Member ships a breaking release next month, the user's site breaks. The AI didn't really build anything. It just installed someone else's work.

So I pulled in a different direction. Patterns like "member directory" or "events list" or "newsletter signup" have been written thousands of times in WordPress. The AI doesn't need to invent the PHP from scratch on every install. It needs to pick the right pattern and fill in the variables.

The output: SailWP ships you a real, vetted, hand-written plugin. It lives in your wp-content/plugins/ folder under a name like sailwp-recipe-alumni-directory. It's GPL. You own it. If SailWP disappears tomorrow, the plugin keeps working. There's no vendor lock-in because there's no vendor. It's yours.

The AI's job is selection and parameterization. Pick the right recipe based on what the user asked for. Ask the two or three questions that actually need an answer ("should profiles be public, or members-only?"). Skip the questions that don't ("required fields", pick sensible defaults, the user can edit later). Bundle the plugin with the brand colors and fonts already wired in. Install. Activate. Create the pages. Done in about thirty seconds.

What's live

Five recipes are running in production right now:

• Alumni or member directory
• Contact form
• Events list
• Services list
• Newsletter signup (works with Buttondown, Mailchimp, Kit, MailerLite, or just stores subscribers locally if you don't have an email provider yet)

You speak to the Co-pilot, you answer one or two questions, and a few seconds later you have a new feature on your site. Not a mockup. Not a draft. A real plugin you can keep.

The honest part

I have twenty-seven people using SailWP Co-pilot right now. None of them are paying. And I have almost no feedback. That's the part of this story that's still missing. I built something that I think is meaningfully different from what's out there, and I genuinely don't know yet whether it lands.

If you build WordPress sites, for yourself, for clients, for a friend who keeps asking you to fix the menu, this is the moment I'd love you to try it. Especially if you've ever sighed at the gap between "I want a member directory on my site" and the four hours of plugin shopping that follows.

It's at sailwp.com. The Co-pilot is the thing on the right side of the screen. Tell it what you want. If something breaks, I want to know. If something works in a way that surprises you, I want to know that too.

The stranger on Reddit never came back to the thread. That's fine. The thread changed the product, and that's more than I had any right to expect.