In this issue: The AI gap between agent orchestrators and chatbot users keeps widening. A pragmatic Chrome plugin hack to bring AI into your CMS. Velora Cycling’s Peter Stuart on what remains valuable when answers are free. Plus: Microsoft launches a content marketplace for publishers.
What we’re talking about: While some are already orchestrating armies of AI agents, many others are still waiting for their Microsoft Copilot license to get approved. A gap is opening up: on one side, fully integrated systems with access to all kinds of data. On the other, chatbot users stuck in enterprise silos. You’re seeing this kind of observation everywhere.
Here’s a pragmatic idea for newsrooms: bring AI into your CMS without touching the CMS itself. With a Chrome plugin.
This gets a little technical, but with AI’s help it’s straightforward. Here’s how it works: a Chrome plugin grabs content from the CMS text fields, sends it to ChatGPT, Gemini, or Claude with various preset prompts, and displays the response right in the browser.
For example: checking against your house style. A plausibility check. Suggestions for headlines, SEO lines, or social cards.
A Chrome plugin is basically just a few scripts distributed as a ZIP file. I built one for SPIEGEL, my AI colleague David Bauer built one for Republik. David’s Sidekick is available to try in English if you have an API key.

If you want to build your own CMS copilot, just ask an AI and let it walk you through step by step. Things to consider: Who should be able to use the plugin, Mac or Windows? How do you distribute the API keys? Where do the prompts live? How angry will IT be? I’ve written more about it here.
What else I’ve been reading: