What changed
On August 24, WordPress.com opened a redesigned WordPress Studio desktop experience in beta. Studio Code itself is not new: the WordPress-specialized coding agent launched in the CLI in April and moved into the desktop app in June. The material change is the desktop workflow around it. New Studio users now see the agentic interface by default, while existing users can opt in without migrating their local sites. The app places a site list, Studio Code chat and a live interactive local preview side by side, and its annotation tool lets users select page elements and send batched visual feedback back to the agent. The same local build can later be synced to WordPress.com or Pressable. The beta also introduces a credit model: WordPress.com says users receive a one-time credit gift and can buy $10 top-ups after hitting the limit, replacing earlier messaging that Studio Code was free with unlimited beta credits.
Why it matters
For WordPress developers and agencies, the change collapses several formerly separate loops—prompting an agent, inspecting a site in a browser, describing visual corrections, editing locally and handing a build to managed hosting—into one desktop surface. That can reduce iteration overhead, especially for client feedback and repetitive WordPress-specific work, while keeping changes on a local site until a human chooses to sync. It also changes the economics and governance of the beta: teams now need to understand credit consumption, agent permissions and hosting dependencies instead of assuming an unlimited experimental tool. Because Studio Code can read code, edit files and run WP-CLI commands, builders should treat its local environment as an execution boundary rather than as a harmless chat interface.
The agent is now the center of the desktop workspace
The redesigned Studio places local sites on the left, Studio Code in the middle and a live WordPress preview on the right. New Studio users get this experience by default; existing users can turn it on as a beta feature and can switch back to the classic UI. Existing local sites carry over automatically.
Visual feedback becomes agent input
The in-app preview is interactive, including access to WordPress admin, and the Annotate control lets a user click elements, stack notes and send them together to Studio Code. That shortens a common agency loop in which screenshots or client comments have to be translated manually into code changes. The useful claim is the workflow integration itself; how reliably the agent interprets complex design feedback still needs project-specific testing.
The work stays local until the user syncs it
Studio Code operates against a real local WordPress installation and can work with blocks, themes, plugins and WP-CLI. WordPress.com positions that local boundary as a safer place to experiment because agent changes do not touch production automatically. When a site is ready, Studio can sync to WordPress.com or Pressable; managed-hosting publication remains a separate human-controlled step.
The beta now has a visible usage cost
Earlier Studio Code beta announcements described the experience as free, including unlimited credits. The August 24 redesign instead says beta users receive a one-time credit gift and can buy top-ups for $10 after reaching their limit. WordPress.com has not published enough detail in the announcement to translate that top-up into a predictable per-task cost, so agencies should not yet build fixed-margin delivery assumptions around it.
Agent permissions still require ordinary development hygiene
Studio Code can inspect a codebase, edit files and run commands inside the local Studio environment. Teams should keep source control, review generated diffs, avoid placing unnecessary production credentials in the workspace and validate changes before syncing. The agentic features can be disabled in Settings, which gives teams a straightforward fallback if a project or customer should not use AI-assisted development.