DatoCMS vs ESPHome

Two bodies of work sit side by side. The dated entries through spring covered developer onboarding - OAuth project linking, an npx CLI that works without setup, plugin scaffolds in the starter kits, a raised CMA limit - plus automatic antivirus scanning on every Media Area upload. The undated stream since then has been agent access and editing surface: DatoCMS Agent Skills, a Remote MCP Server, Visual Editing and its sidebar previews, a media editor covering video, and responsive images that size themselves across every SDK.

DatoCMS is making the CMS addressable by something other than a human in the dashboard. Agent Skills and the Remote MCP Server give agents a defined way in; the CLI and CMA work over the preceding months removed the setup rituals that made programmatic access awkward; Visual Editing pulls the editing surface out to where content is rendered. The media pipeline is being hardened on a parallel track - antivirus by default, asset collection permissions, focal points, video frame selection - which is the part that turns up in enterprise procurement. Neither thread has slowed.

With Agent Skills and MCP shipped, the natural follow-up is scoping and permissions for agent access - the equivalent of asset collection permissions applied to what an agent may read or write - since DatoCMS has already built the roles machinery to hang it on.