You vibe-coded an app in Claude Code. Now get it onto a WordPress site in 60 seconds.

You opened Claude Code on a Tuesday. By lunch you had a working tool: a quote calculator, a booking widget, an internal dashboard, whatever the client asked for. It runs. It looks good. Your agent wrote the whole thing.

Now what.

The part nobody documented

Your app lives on your laptop. Your client’s business lives on WordPress. Between those two things sits the gap nobody warned you about.

You could deploy to Vercel. Now your client has two logins, two bills, two analytics dashboards, and a tool that doesn’t know who their customers are. You could ask a developer to “integrate it.” That’s a three-week ticket and a five-figure quote. You could paste the HTML into a Custom HTML block, watch the styles collide with the theme, and tell yourself it’s fine.

It isn’t fine. The vibe-coded app sits on one island. The WordPress site sits on another. The bridge doesn’t exist, so the work doesn’t ship.

Why this hurts more than it should

You built the thing in fifteen minutes. The deploy story takes a week. That ratio is wrong.

Worse: the app can’t see your posts. Can’t read your users. Can’t hit your AI provider. Can’t appear in your sitemap, your backups, your CDN, your auth. It’s a stranger renting a room across town from the business it’s supposed to serve.

By Friday, you’ve forgotten the URL.

The architecture, briefly

WordPress 7.0 (May 2026) shipped three APIs that change what a plugin can do:

• Connectors API. Site admins configure Anthropic, OpenAI, or Google credentials once at Settings > Connectors. Every plugin inherits them.
• WP AI Client. Provider-agnostic PHP API. Plugins call wp_ai_client_prompt(), the site’s connector handles the LLM call.
• Abilities API. Register functions the site’s AI agent can invoke.

DesignSetGo Apps is the Harness above that stack. We never hold your API keys. We never pay for inference. Your apps run in a sandboxed iframe (or inline mode for SEO) with a permissioned postMessage bridge: the app declares what it needs in its manifest, you approve it at install, the plugin enforces it at runtime. Same trust model as a browser extension.

The bridge protocol is frozen at v1. The manifest schema is frozen at v1. Both are public, both are specced.

The transform

You write the app in Claude Code (or Cursor, Aider, Claude Desktop, ChatGPT, v0, Lovable, Bolt). You run one command. The app is live on your client’s WordPress site at a URL that’s part of the site, served from the site’s domain, backed up with the site, indexed with the site.

If you’d rather not use a CLI, drop the HTML file into wp-admin. Same runtime. Same URL. Same permission model.

The app can live at /apps/{slug} as an additive widget. Or it can mount at / and become the entire front-end of the site, with WordPress quietly running underneath as the CMS, auth layer, and data source. The /apps/ surface adds tools. The root mount replaces front-ends.

From Claude Code to live, in three steps

npx @designsetgo/cli init my-app
# write the app with Claude Code. iterate. test.

designsetgo apps deploy --build --site https://your-site.com
# bundle, validate the manifest, push. live in seconds.

That’s the agent-deploy path. On the free tier you get 1 active app and a read-only bridge: posts.list, posts.get, pages.list, pages.get, user.current, plus help methods. Enough to ship a real tool.

Activate the 14-day Pro trial and the CLI unlocks alongside ai.prompt (your app calls the site’s configured LLM through WP AI Client), abilities.invoke (your app calls functions the site has registered), abilities.publish (your app registers functions the site’s AI agent can call), write methods, dynamic routes, scheduled jobs, webhooks, and Riff (in-browser app generation with streaming code).

Pro is a per-site license after the trial. Managed AI is a separate $30/month add-on if you’d rather not bring your own keys.

The offer

The plugin is real. The bridge ships. The CLI ships. The importer ships. The AI surfaces ship.

If you’ve been carrying a folder of half-deployed Claude Code projects waiting for the WordPress story to exist, it exists.

Install DesignSetGo Apps and ship the app you already built.

The docs cover the manifest schema, every bridge method, the CLI, and the Harness. Follow-up posts in this series cover the safety story, the Claude Code workflow end-to-end, and how apps can publish abilities your site’s AI agent can call.

Nealey