Manual performance tuning is mostly hypothesis and hope. Agentic loops like pi-autoresearch take a metric and a budget, run the experiments themselves, and keep only the versions that measure better.
Beau Lebens talked about agentic commerce at Stripe Sessions, where AI agents do the shopping. My take on the hard parts: live inventory data, checkout security for bots, and what MCP and the Abilities API actually change.
RAG re-derives everything on every query, so nothing accumulates. This is the Raw and Wiki folder layout, the three control files, and the daily, weekly and monthly jobs I use to keep an AI context layer my agents can read.
WooCommerce for Claude came out of Automattic’s Radical Speed Month. It uses MCP to give the model analytics lookup tables, a store knowledge layer and an AI-readiness score, all on one endpoint. Plus the provider pattern and how to run it locally.
Ghost is an agent-first Postgres platform. Notes from using its MCP server and database forking to let AI agents test schema changes and index strategies without touching a shared staging database.
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.
A logistics director with all-green KPIs and 18% late shipments does not have a data problem. Scoped AI agents watching the TMS can tell you which handoff actually broke, and tell you on the morning it happens.
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.
Cowork gets written off as Claude Code for people who don’t code. I use it for architecture work and multi-file debugging, and this is how I keep the context window lean, why I stay in plan mode, and which repeat jobs I turned into skills.
Claude Code is not only for refactoring PHP. Three things I run through it that never touch a codebase: LaTeX decks kept in Git, cross-app search over Slack and Notion, and prospect research.