What it means
An admin panel is the defining feature of a content management system, and its largest liability: a second application in front of the content, with a login to attack, sessions to steal, forms that must mirror every field, and its own idea of the content that drifts from the templates. Loam removed it.
What remains is the files, the rules for how they may change, and one gate through which changes arrive: the MCP, a protocol any assistant speaks.
How loam does it
- Management in your own words. “Move the summer closure notice above the opening hours and make it less formal” is not a feature a panel offers. An agent works from what you mean.
- One truth. Your agent reads the same files the site renders. No admin-side model can disagree with the page.
- The panel's other jobs, as data.
/adminexplains the site to any agent. Drafts and refusals come back through the MCP in plain language. The journal is the activity log. The machine views are the map of the site. - Nothing to learn, nothing to age. Panels need training and documentation, and go out of fashion. A conversation does not.
What it costs
A dependency on a capable assistant. Someone who may not or cannot use one needs another way in. Loam's answer is a principle — new kinds of users get new clients, never new doors — and that client exists: the edit client on /edit, off by default, speaking to the same MCP under the same rules. A client, not a panel, and never a second entrance with its own login.