A speaker guide for WordPress Core AI projects needs review
The Core AI team has a draft guide for anyone presenting on Abilities, the AI Client or the MCP Adapter at a WordCamp or meetup. Comments on it close on 21 April 2026.
The Core AI team has a draft guide for anyone presenting on Abilities, the AI Client or the MCP Adapter at a WordCamp or meetup. Comments on it close on 21 April 2026.
AI tools guess at your store because they cannot see it. MCP gives them real context: your files, your data, your WP-CLI. We talk it through at WooCommerce office hours on April 15, 2026, on Slack.
Pinecone and Chroma are a lot of machinery for a few hundred Markdown notes. The Google Memory Agent Pattern keeps structured memories in SQLite, consolidates them in the background, and loads them straight into a large context window.
Most people run one Claude Code agent and then wait for it. Git worktrees let you keep several going in separate folders on the same repo. How I lay that out in Warp or Tmux, plus the shared local database problem nobody warns you about.
MCP lets an AI pull data out of Google Drive, read old repos and load BigQuery instead of just suggesting Python. Includes the 150GB log file one unattended loop produced, and why domain knowledge still decides the answer.
The Bits-over-Random Metric compares your retrieval against random chance, which is how you catch the context pollution a high Success@K hides. Notes on staged tool routing and where the collapse regime starts.
A colleague shipped a custom assistant in a couple of hours by wiring Google Calendar, Microsoft To Do and Notion together. Execution stopped being the bottleneck, and here is a Gemini API scheduler you can start from inside WordPress.
My agent failed the same caching refactor three times before I fixed how I was briefing it. Planning mode, browser access through Playwright MCP, and claude.md files are what turned that into one-shot work.
A decade of explaining why WordPress sites don’t feel like apps, and what 2026 changes: blocks described to an AI instead of scaffolded by hand, the Interactivity API handling state without page reloads, and theme.json holding the design system.
My agents decided their own heartbeat config was redundant and deleted it, twice. The tiered OpenClaw setup that came out of it: orchestrators for judgment, throwaway personas for tasks, and five Markdown files that hold an agent’s identity.