Notes from the codebase. And whatever else.

People wire Claude Code into content sites four ways — an MCP server on a headless CMS, the WordPress REST API, a hand-rolled admin, or plain markdown in the repo. Each has a sharp edge that only shows up in production: MCP tool definitions eating a third of your context, permission prompts between an editor and a typo fix, onboarding that needs a developer, and client-rendered pages answer engines can't read. The sourced rundown — and what changes when the agent is the architecture, not a guest bolted onto one.

The plain-words tour: one of the first LLM-native CMS frameworks, where you edit by talking to an agent. A full CMS ready on day one, a top-tier inline editing flow, near-zero onboarding for content editors, content ops that plug straight in, your own models, and open source.

The problems with running a content site on a headless CMS are old and well-documented. What's new is the alternative: an agent-native architecture where the agent is the primary actor, not a client bolted onto an API built for human editors. Headless still fits the minority it was built for. For everyone pushed onto it past the no-code ceiling, the math changed.