In this lesson · 5 min
Three context sources, a chosen model, and supervised execution.
Phase 4 · Implementation
Studio Code connects conversation and site
Open the local site, enter the Studio Code tab, and work with the agent inside the project.
Takeaway From the open project to assisted implementation
Speaker notes
Give a short introduction: Studio Code is the coding agent built into the WordPress Studio app and also available in the CLI. On desktop, select the site and open the Studio Code tab; the agent then works in that project’s directory. [Sources] https://developer.wordpress.com/docs/developer-tools/studio/studio-code/
Core tools
The agent works with the open site
C
Chat
Receives instructions, files, and questions.
F
Files
Reads and edits the site directory.
W
WP-CLI
Runs commands in local WordPress.
▣
Screenshots
Opens and captures the visual result.
Speaker notes
Show only the essentials of the interface: conversation, attachments, model picker, and action history. The documentation states that the agent can read and write files, run WP-CLI, and capture the site. Remote operations are outside this demonstration. [Sources] https://developer.wordpress.com/docs/developer-tools/studio/studio-code/
Available models · 2026-08-05
Choose the model for the task
S5
Claude Sonnet 5
The fast, effective default for most tasks.
O
Claude Opus 4.8
More capable for complex, multi-step tasks.
G
GPT 5.6 Sol
A fast, effective OpenAI option for general tasks.
Speaker notes
On desktop, use the menu at the bottom of the conversation; in the terminal, use /model. Explain that this list changes quickly and should be checked in the picker before the event. The official documentation verified on August 5, 2026 lists Sonnet 5 as the default, Opus 4.8, and GPT 5.6 Sol. [Sources] https://developer.wordpress.com/docs/developer-tools/studio/studio-code/
Implementation context
Three sources guide the agent
Speaker notes
Attach both Markdown files and point to the Design System folder or assets. Ask the agent to read all three sources, inspect the current site, flag conflicts, and propose a short plan before editing. File uploads are supported on desktop and in the CLI. [Sources] https://developer.wordpress.com/docs/developer-tools/studio/studio-code/
Plan approved
Context delivered. Agent at work.
Authorize implementation in stages; then review the diff and desktop and mobile screenshots.
Up next 05 · Site Editor
Speaker notes
Once requirements.md, design.md, and the Design System are understood and the plan is approved, let the agent execute. Keep supervising: review permissions, the diff, and the visual result before continuing to the Site Editor. If Studio Code is unavailable, use the fallback site.