Prompt caching only pays off when the prefix stays byte-identical. I go through the mistakes that break it, a semantic cache layer for WordPress, loading tool definitions on demand, and what to keep or drop between turns.
Anthropic’s subscription ban pushed me off Claude for OpenClaw. Here is the OpenRouter setup I use with Kimi-K2.5, what it costs, where it runs slower, and the GDPR problem with hosted weights.
Automating every quick question makes tasks faster and teams weaker. What the research on informal communication and AI burnout shows, plus three ways to put useful friction back into the workflow.
Version 0.8.0 of the WordPress AI plugin moves image generation out of experiments, adds a Refine from Notes experiment that applies editorial notes for you, and ships the first AI dashboard widgets.
Studio Code Beta is a CLI coding agent for WordPress, built on Claude Code. It runs WP-CLI, spins up local sites, screenshots its own work, and validates block markup against the editor before inserting it.
Vibes-checking AI output is the new bottleneck. What actually moved my Claude Code performance: terminal permissions for the agent, a test requested with every feature, and a no-stop rule until they pass.
A static A/B test keeps sending half your traffic to the losing variation until someone stops the test. Thompson sampling moves the traffic as the numbers come in. Here is the Beta distribution behind it and how to store the state in WordPress.
An ad hoc prompt works once, then quietly stops matching the result you got the first time. Claude Code Skills wrap the workflow in a SKILL.md file, with structured JSON for the data and Python for the parts that have to be deterministic.
Retrieval gets worse as the memory pool grows, while the confidence score keeps climbing. Here is what causes RAG memory decay and the four fixes I put into production systems: topic routing, semantic deduplication, relevance based eviction, and lexical reranking.
Recruiters now expect designers to ship production code out of AI agents. Here is what that costs in practice: toggles no screen reader can see, XSS holes in generated forms, duplicated code, and engineers spending more time per pull request cleaning up after it.