Generic tutorials lost most of their traffic once answers moved into the IDE, but version-bound WordPress notes still find readers. This is the audit I run on my own queue, what I stopped writing, and the one check I do before publishing anything tied to a release.
A customer asks you to delete their data, the erasure report says zero items, and your chat plugin still has every conversation stored. ERC research wants exactly those cross-session profiles, and WordPress privacy tools only see what you register.
Advice on agent costs splits between free-roaming agents and tightly scripted ones. Exploring once and replaying the path makes sense, but in WordPress that replay is a cache, and the part that bites is invalidation.
A study tested ChatGPT on econometric code in Python, R and Stata, and it did well except in the language with the least public code. Legacy WordPress and WooCommerce work has the same weak spot, so I benchmark AI output before I trust it.
A recent piece argues most AI agents fail because teams build them top-down and hope the model holds it together. I agree, but WordPress has no long-running PHP process, so that orchestration has to live in hooks, the database and a queue.
Every AI plugin ends up needing a threshold for when to auto-apply an answer and when to hold it for review. The confidence number most of us gate on tracks how fluently the model produced its tokens, which is a different thing from whether the answer is true.
A Towards Data Science tutorial calls a small Python chat loop an AI agent. The client setup is worth keeping, but it has no memory, no tools and no stop condition, and a WordPress build has to add all three.
A Towards Data Science piece builds one retrieval system four times, from TF-IDF to fine-tuned DistilBERT, and the fine-tuned model flips its answer between two epoch counts. For a WooCommerce store, that argues for pretrained embeddings and no training.
WordPress 7.0 Armstrong puts an AI layer into core: an AI Client, a Connectors API, and one screen for provider keys. I look at what it changes for plugin code, what stays off by default, and what to test before updating client sites.
On client sites, agents write plausible code against a stack that is not there. Specs help when they record what your WordPress install actually runs. These are the facts I pin down first.