WordPress Guidelines keeps agent memory, skills and instructions in an ordinary custom post type, and it’s headed for Core. Here’s what that means for plugins with their own memory stores, which permissions to test first, and when a separate table still makes sense.
Angle encoding costs you qubits and amplitude encoding costs you gates, and both get paid when data crosses into the system. WordPress has the same problem with autoloaded options and fat transients, and that one is cheaper to fix.
I read the WordCamp Europe 2026 schedule as a prep list. Register one Abilities API entry on staging, run the WordPress 7.0 upgrade on a copy, and pick the sessions you will actually use before Kraków or the livestream.
Agent features drift from one helper to a sprawl nobody can put a price on. This post maps four operations research models onto real decisions, like which agents to build and how to route requests, then covers where the solver should live on a WordPress site.
AWS shipped the Agent Toolkit, which gives coding agents skills, live docs and an MCP server. The part I care about is the guardrails: IAM condition keys that mark agent calls, and CloudTrail records of what the agent did. Set those up before an agent gets near a client account.
WooCommerce’s beta AI Product Advisor ranks your catalog and suggests copy fixes. The ranked queue and revert log are the useful parts. The WordPress.com connection and the lift math are where it bites, so stage it, clear stray output first, and apply in small batches.
An AI chat over your WooCommerce orders will hand you confident numbers that don’t match Analytics. Let the model pick the question and let your code answer it. Here’s how I’d wire that with one REST endpoint and a strict args schema.
Naive RAG wrappers that just chunk PDFs into a vector store break on real contracts and reports. Here is the four-brick approach I use instead: structured parsing, question parsing with an expert dictionary, filtered retrieval, and typed generation.
WordPress.com’s Posts to Podcast feature turns blog posts into AI-generated audio from the dashboard. I look at how it stores the files, the media bloat risk, and how to manage the assets with WP-CLI and a theme hook.
Tightening the prompt won’t make an LLM integration reliable in production. Here’s the control layer I put between WordPress and the model: input guards, a circuit breaker, response validation and retries.