Changebot makes it easier to keep customer updates organized and polished, from AI-assisted tag management to clearer hosted changelog visuals.
Manage Custom Tags with AI Agents
AI agents can now work with your team’s custom tags directly through MCP, making it easier to choose the right tags when creating or updating customer updates. Custom tags stay organized for your team, while built-in and product tags remain.
Sharper, More Flexible Hosted Changelog Images
Tall screenshots, full-page captures, and high-resolution uploads now display more clearly without being squeezed into narrow strips. Hosted changelogs keep images compact and readable at up to 560 pixels tall, while the lightbox provides a larger, scrollable view on index and individual update pages. We also now support animated WebP images.
More Consistent Hosted Changelog Design
Hosted changelogs now share a clearer visual hierarchy across themes, with more readable line lengths, typography, headings, and code styling. Mobile layouts are easier to scan, and Spotlight wordmarks display at a more natural size.
This morning we gave you four new designs. We buried the lede.
The design is one of three new improvements we've made with our hosted changelogs. The other two are the fonts your page is set in and the colors it is painted with, and if you have not touched either, your changelog is currently wearing last season's outfit. Time to fix that.
An improved design editor
Design editing has its own full-page editor now: Destinations → your changelog → Design → Edit design.
Controls on the left — design, heading font, body font, theme, six colors. You can preview your actual changelog with your actual updates, repainting the instant you make a change. Flip the preview between desktop and phone with one toggle.
Fonts, and curated font pairings
Your page contains two fonts: one for headings and one for body copy. You can now customize them. Pick from 20 heading fonts, and each one is paired with up to eight body fonts that we've curated.
So yes, you can absolutely ruin your changelog — but not with typography.
Here are all 20, each set in itself, next to the first body font on its list:
The font stack is independent of the design and the color palette. So you can experiement with different designs, colors, or fonts to find the perfect changelog for your product.
Additionally, we include fourteen fonts that are only available as body fonts: Public Sans, Source Sans 3, Figtree, Hanken Grotesk, Nunito Sans, Source Serif 4, Literata, Newsreader, Crimson Pro, Piazzolla, Roboto Serif, Roboto Mono, Source Code Pro and System mono.
That is 34 in total. Thirty-one are variable fonts we host ourselves, subset to Latin and stripped down to the weight axis — nothing phones Google at load time, and a visitor downloads exactly the one or two very small, stripped-down files your page uses. The last three are system stacks, which ship nothing at all and use whatever the reader’s device already has.
Seventeen palettes that you can use with any design
A palette is six colors: page, panel, highlight, text, accent, link. Everything else the page paints — body copy, dates, hairlines, the ink on a button, link hover — falls out of those six on its own.
Six of them were drawn for a particular design and show up when you switch to it. But that's just a suggestion. Go wild if you want. Console in Rose? Go ahead. Bento in Terminal? That's cool with us.
All seventeen clear 4.5:1 contrast for body text and links against the fill they sit on.
Or bring your own six colors
You can create your own color palette if you want as well!
Use one of ours as a starting point to make your own. Your version saves as a theme your team owns and lands in the picker in your own group, above ours. Edit a theme you already own and it saves in place, and every changelog pointed at it updates. Set your brand colors once, use them everywhere.
Your agent can do all of this too
Driving Changebot through MCP? Ask your agent to create a theme that matches your marketing site. It has all the tools it needs:
list_fonts hands over the pairing table, so an agent knows which body fonts go with a heading font before it commits.
list_themes returns your themes and ours, colors included.
create_theme and update_theme write a palette your team owns.
update_destination sets the design and both fonts. Pass "default" for a font to fall back to the design’s own pair.
preview_destination renders any combination you like at a link you can open, saving nothing.
You can now edit changelog design themes right in the MCP and immediately see those changes — either directly inside your agent when it supports images (for example, the Claude desktop tool) or, if you prefer viewing edits outside the agent, via a short-lived preview link (for example, Claude in terminal).
What you can do now:
Edit changelog design, colors, and titles in the MCP and get an immediate visual update inside supported agents.
When an inline screenshot is available, the agent will show the captured image so you can confirm layout and styling at a glance.
If you need an external view, open the short-lived preview link to see the same rendering outside the agent and jump to the destination’s settings page to make edits quickly.
This week: improved design, clearer field-level validation, and preserved editor inputs.
We focused this release on three practical goals: make forms clearer, keep your work from getting lost, and make publish/preview flows more reliable. You’ll see field-level error messages where mistakes happen, clearer browser titles so tabs are easier to navigate, and fewer surprises when moving between pages or using Back.
Accessible inline validation and smoother navigation
Forms across Changebot now show server-side validation next to the relevant fields and behave more predictably when saving or navigating. That means clearer, screen-reader-friendly error messages and fewer hidden alerts.
Field-level errors appear where you made the mistake so you can fix issues faster.
When a save fails, your inputs are preserved so you don’t have to retype title, content, or tags.
Submit buttons are disabled while a request is in progress to prevent duplicate attempts.
Page headers and the sidebar remain stable between pages so workflow controls don’t jump around.
Preserve editor inputs and fix previews
Failed saves no longer clear what you typed, and preview links and redirects point to valid in-app pages so previews load reliably.
Discoverable MCP setup with per-client guides
MCP setup is now in Settings with step-by-step, per-client tabs so you can add a server and sign in faster.
Each client (Claude, Cursor, ChatGPT, VS Code, and others) has its own guide to get started quickly.
Immediate Webflow collection and field updates
When you pick a Webflow site or collection, downstream collection and field dropdowns update immediately and incompatible selections are cleared so your Webflow destination stays in sync while editing.
Cleaner update view
The extra “Content” label has been removed from the update detail view so the update body reads cleaner and the page feels less cluttered.
Redesigned customer update pages
Customer Update pages were reorganized to keep actions visible and reduce visual flicker. Content stays left-aligned and stable while you scroll, and tab switching no longer remounts the header.
Publish and preview actions remain accessible in a persistent top bar as you scroll.
Status badges are restyled as rounded pills (Draft, Published, Failed) for easier scanning.
Tabs, breadcrumbs, and bulk action placement were adjusted to reduce layout shifts on small screens.
Clearer error handling and background updates
Errors and background updates are surfaced more clearly so you won’t be left with stuck actions or silent failures.
Publish and other operations show clear failure badges and readable error messages when something goes wrong.
Background refreshes and real-time updates reload the right data so lists and status indicators stay accurate.
Toasts now explain network or integration failures so you know what to do next.
Publishing & Publications stay accurate (and failures are easier to understand)
Publishing has a lot of moving parts, and it’s easy to end up looking at an out-of-date status. This release tightens the loop so the Publications and Updates pages reflect what’s actually happening—and when something fails, you can see why and retry.
See a clear Publishing… state while work is in progress, plus Failed badges with error details when something doesn’t go through.
Get up-to-date statuses and counts on Updates/Publications when events happen in real time—or when you come back to a page.
If a background refresh can’t complete, you’ll now see a visible error instead of silently viewing stale data.
Bulk delete in Publications is now all-or-nothing, so you don’t end up with a partially deleted selection.
New Features
MCP setup is now in Settings (with per-client tabs). You can follow step-by-step setup for clients like Claude, Cursor, ChatGPT, and VS Code in one place.
Improvements
Email confirmation now signs you in automatically. After confirming, you’ll land where you would after a normal login (like onboarding).
Faster page loads for integration pickers. Channel and Webflow site pickers no longer block the page from loading, and they show clearer reconnect/error states when access expires.
Bug Fixes
Clearer, field-level errors across the app. Forms now show errors next to the exact fields to fix, instead of generic messages.
Customer update editor won’t drop your draft on save errors. Your title, content, and tags stay in place so you can fix issues and try again.
More reliable repository connect. You’ll see clearer “already connected” messages, and connection failures no longer look like an empty list.
Webflow connection screens are more consistent. Connected accounts reliably show the right configuration state, with clearer error messages.
Published update links redirect correctly. Older URLs now resolve to the canonical friendly URL instead of 404ing.
Builder chat recovers better after interruptions. When you return to a thread or a send fails, you’ll see what happened and can retry.
.png)
