Agentic coding: how I debug WordPress sites now
A three-step way to point an agent at a broken WordPress site: let it read debug.log, make it write a hook-level plan before it edits anything, then iterate on what it ships.
Category: AI in WordPress
The WordPress AI Client heading into core 7.0
Notes from the February 4 contributor meeting on the WordPress AI Client merge into 7.0: why OpenAI, Google and Anthropic are moving out to separate plugins, why the off switch is a constant rather than a filter, and what MCP adapters mean for the Abilities API.
What the WordPress.com Claude Connector actually does
WordPress.com now has an official Claude Connector built on MCP and OAuth 2.1. It gives Claude read-only access to site data like traffic, comments and content, with no custom REST bridge to maintain. Here is what it can do, how to switch it on, and where it stops.
SageMaker vs Azure ML: how each handles training compute
Part 2 of the SageMaker vs Azure ML series, this time on compute. Azure keeps clusters as persistent workspace assets while SageMaker spins them up per job and tears them down after, plus spot instances, checkpointing and container control.
Syncing frontend and backend code in one repo
Separate repos for the React frontend and the WordPress backend are why payloads drift out of sync. Notes on moving to a monorepo with Roots Bedrock, keeping an AGENTS.md map of endpoints for coding agents, and the stale REST cache that broke a checkout.
WordPress AI micro-credential: 80 students, $1,000 stipend
The WordPress Foundation, UIC and Automattic are running a paid micro-credential pilot called AI Leaders: 80 students in Illinois and Louisiana, a $1,000 stipend, and real WordPress AI work instead of prompt-writing exercises. Here is what that changes for hiring.
WordPress 7.0 client-side media moves resizing to the browser
The February 4, 2026 dev chat put client-side media on the road to WordPress 7.0: libvips compiled to WASM, running in a worker thread, with image resizing done in the visitor’s browser instead of on your server.
Inside the new WordPress AI Experiments: MCP and request logs
The Core AI team put out a Call for Testing for the AI Experiments plugin. Here is what is in it: MCP server support, markdown feeds, extra providers and AI request logging, plus the $400 API bill that convinced me logging is the part you cannot skip.
How Recursive Language Models get around context rot
A million-token context window does not mean a model can reason across a million tokens. Recursive Language Models hand the context to a sandboxed Python REPL and let the model write code to partition and query it, which is how DSPy now implements the strategy.
How the WordPress MCP Adapter connects your site to AI agents
WordPress 6.9 shipped the Abilities API, and the MCP Adapter is what lets AI agents find those abilities and call them. Ahmad Wael covers flagging an ability for MCP, the two transport methods, custom servers, and keeping permission callbacks tight.