# My New Favourite Way to Vibe Code WordPress > [!question] Lingering Questions > - What model actually powers Studio Code, and is "Claude Code, but for WordPress" a literal claim or just a framing? > - "Free while in beta" signals a future pricing change — what happens to existing vibe-coded sites when that transition hits? > [!tip] Article Ideas > - Test Studio Code's annotate + audit features on a messy real site (not a clean demo) and record how much of the output survives without hand-fixing — direct follow-up to the Permanent candidate here. > [!link] Cross Reference > - [[3. Resources/Literature Notes/WordPress Studio + MCP - A Better AI Workflow]] — the MCP bridge to an external agent (Claude Desktop) vs. this in-app "vibe code" assistant; two different shapes of AI-in-Studio. > - [[3. Resources/Literature Notes/WordPress Studio MCP (Jonathan Bossenger)]] — shares the "agent drafts, human tweaks" framing of AI-assisted WordPress dev. > [!quote] Vocabulary > - **Vibe coding** — building software by describing intent in natural language and letting an AI agent generate the implementation, with the human reviewing rather than writing the code directly. ## Metadata - Source: [[3. Resources/Readwise/Articles/My New Favourite Way to Vibe Code WordPress]] - Author: WordPress.com (presenter: Ryan Welcher) - Format: vendor feature demo (YouTube) - Date processed: 2026-08-16 ## Author's thesis Studio Code brings a Claude-Code-style AI coding agent out of the terminal and into the WordPress Studio desktop app, and its standout workflow is "annotate": point at something on the page, describe the change in plain language, stack up several such notes, then let the agent apply all of them in one pass — no screenshots or marked-up images required. It matters as a demo of how far natural-language-driven WordPress editing has moved into a polished, in-app tool, while also being exactly the kind of clean-demo presentation that doesn't test durability on a real, messy site. ## Key arguments (≤3) 1. Studio Code moves terminal-only "vibe coding" (the video's explicit Claude Code comparison) into the Studio desktop app itself. 2. The "annotate" workflow — point, describe, repeat, then apply — removes the screenshot-and-caption round-trip that AI-assisted editing usually requires. 3. This is a vendor demo on a clean site; it doesn't test whether agent-generated changes hold up as maintainable code on a complex, real production site. ## Claim atoms ### Studio Code brings Claude Code-style AI to WordPress > [!quote] ID:rw_5B5Z3A8YA8_h1 > Think Claude Code, but for WordPress. It used to live only in the terminal, but now it's right inside a WordPress studio. **Context & use**: Opening framing, ~00:00:10. Names the vendor's positioning: AI vibe coding moved from terminal-only into the Studio desktop app, lowering the barrier to entry. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> ### Annotate edits by pointing and describing in one pass > [!quote] ID:rw_5B5Z3A8YA8_h2 > No screenshots, no marked up images going back and forth, just point, describe, and done. **Context & use**: Annotate segment, ~00:01:50. Captures the core workflow win: stack plain-language change notes across a site, confirm a numbered list, and let the agent apply every edit — useful even on live client calls. **Tags**: #xref #articleseed <!-- atomicity: 1 idea ✓ --> ## Permanent candidates - **A vibe-coded demo is easier to ship than a vibe-coded product** — supported by the annotate atom read against the clean-demo setting; promoted to [[3. Resources/Permanent Notes/A Vibe-Coded Demo Is Easier to Ship Than a Vibe-Coded Product]]. ## Processing checklist - [ ] Confirm what model powers Studio Code and whether "Claude Code" implies Claude under the hood - [ ] Watch for the beta-to-paid pricing transition signaled by "free while in beta" - [x] Connect into the relevant MOC — [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] ## Links - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] — a concrete case of natural-language-driven code generation moving into a mainstream desktop dev tool. - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — vendor demo skepticism (clean site, no durability test) is a general product-evaluation lens.