Blog
Controlling your CMS with an agent
By Ryan Smith
An AI agent in your work chat that takes the heavy lifting out of editing your website, paired with Prismic for the fine control. Here's how ours works.
Wouldn't it be good if updating your website was as easy as asking a colleague? You're already in Slack or Teams all day. Imagine typing “add a post about our new hire” or “swap the homepage headline” into a channel, and a few minutes later there's a finished draft waiting for you to check. No logging in, no hunting for the right page, no ticket sitting in someone's queue.
That's what @lobster does for this site. It's an AI agent that lives in our work chat and takes the heavy lifting out of editing: writing posts, building case studies, updating pages. But the agent is only half of it. The other half is a CMS that's built for this, so you still have fine control over every word, image and setting. For us, that's Prismic.
Here's what that looks like
This is the request that started this post. Watch it work, then press Publish:

Publish from Slack, or fine-tune in Prismic
Nothing the agent makes goes live on its own. Every change lands in Prismic as a draft, and you decide what happens next. If it's right, press Publish in Slack. If it needs a tweak, open the draft in Prismic, change whatever you like, and publish from there.
Why the CMS matters
An agent is only as good as what it's working with. A well-built Prismic site gives it a clear structure to follow, and gives you the controls an agent shouldn't have to guess at:
- Content types and slices. Every post, page and case study is made of named fields and reusable sections, so the agent knows where a title, an excerpt or a screenshot goes, and your design stays intact.
- Drafts and releases. Changes are grouped and previewed before they're published, so a new case study and the homepage update that links to it can go live together.
- APIs made for software. Prismic lets an agent read the content model and write drafts, and its MCP server gives AI tools a standard way in.
- The Page Builder for everything else. Moving a section, cropping an image or rewording a line is often quicker by hand, and the agent never gets in the way of that.
If you're new to it, Prismic's own site is a good place to start.
How it works
- Ask in a channel. Mention @lobster and say what you want in plain English. Attach notes or screenshots if you have them.
- It reads the content model. So it only uses fields and slices that exist, the same ones your editors see.
- It writes drafts, never live content. Everything goes into a Prismic release.
- It replies in the thread. You get what it made, anything it wasn't sure about, and links to the drafts. Reply with changes (“shorter intro”, “use the other photo”) and it updates the same draft.
- A person publishes. Press Publish in Slack, or open the draft in Prismic first. Only the people you choose can publish.
We use Slack, but the same set-up works with other work chat tools that let you add a bot, like Microsoft Teams.
Small jobs too
It isn't only for writing. Most website edits are little things that still mean logging in and finding the right field, like a new phone number in the footer:

Guardrails
- It can't publish or delete anything by itself.
- It only touches content, never your code, hosting or DNS.
- It doesn't make up facts, quotes or numbers. If a request is too thin, it asks.
- It writes in your voice, following rules you set.