Sometimes you ship the typo along with the feature. Now you can fix it.
Every entry has a menu to edit it, unpublish it — pulling it from your public page while you rework it — or delete it for good.
And a small kindness: fixing a published entry and putting it back doesn't re-notify your subscribers, so a quick correction never turns into a second email in their inbox.
Good news if you've been shipping a lot: your changelog can now grow without slowing down.
Both your public page and your dashboard load the newest entries first and reveal older ones with a Load more button. A changelog with hundreds of entries stays as fast as one with five — for your readers, and for you.
We gave Changelore a redesign, inside and out.
A new landing page that finally talks to everyone who uses the product — not just developers, but the product and marketing folks who actually write the updates.
And a cleaner dashboard to write them in: a calmer header, a create flow that works the same everywhere, and tabs that give your content room to breathe.
A forty-second demo beats three paragraphs describing it.
Paste a YouTube, Vimeo, Loom or Google Drive link into the editor and it becomes a player right on your public page — so a feature announcement can ship with the clip that shows it off. Drop the link, keep writing; we take care of turning it into an embed.
You wrote the changelog. Let it write the tweet.
One click drafts a short, shareable social post from any published entry — the kind you'd put on X or LinkedIn — ready to copy straight from the dashboard. Prefer to stay in your agent? Generate it over MCP instead. Either way, the announcement writes itself from the update you already published.
Available on paid plans.
The writing experience got a serious upgrade.
We rebuilt the editor on a cleaner foundation, with a friendlier toolbar and a lot more range: tables, code blocks with syntax highlighting, collapsible sections, math, emoji, and task lists. Paste Markdown and it becomes formatted content; the document still round-trips back to Markdown for the API.
Whatever your update needs to say, the editor can now say it.
A hosted changelog shouldn't look hosted.
Brand it in a click. Set your brand color, drop in your logo, and write your own header. The page picks a readable foreground automatically, so it looks right without any fiddling.
Or take full control with CSS. For anything the settings don't cover, write your own CSS and watch it apply in a live preview as you type — no publish-and-check loop. Your page, your rules.
Available on paid plans.
The Slack and Discord posts just got a lot nicer to look at.
Instead of a bare link, a published entry now arrives as a proper card — the title, its tags, and a short excerpt — so people in the channel can tell what changed without clicking through. It's the difference between "there's an update" and "here's the update."
Switching to Changelore shouldn't mean leaving your history behind.
Point us at an RSS or Atom feed — or your existing changelog tool — and we'll pull your past entries in, with their original publication dates, so your timeline looks like it was here all along.
Safe to re-run. Every imported entry is matched by a stable source id, so running the import again updates entries instead of duplicating them. And you can import silently, without firing a single email or webhook, so nobody gets a notification about a release from last year.
Meet your users where they already are.
Connect a Slack or Discord webhook and every entry you publish lands in your channel automatically. No copy-paste, no separate announcement to write — publish once, and your team and your community both hear about it at the same time.
Ship on your timeline, not the one where you happen to be at your desk.
Give any draft a date and time and Changelore publishes it for you — subscriber emails, webhooks and all — exactly when you planned. Line up the announcement for launch morning and go to sleep; it'll go out without you.
This is the idea Changelore was built around, and it's now the smoothest path to a published entry.
A remote MCP server. Connect Claude Code, Claude Desktop, or any MCP client with a single URL — nothing to install. Your agent can list projects, create and edit entries, and publish them, all as first-class tools.
Authenticate the way that fits. Use OAuth 2.1 for an interactive client, or a Personal Access Token for scripts and CI. Token scopes let you hand an agent write access while keeping publish for yourself, so the human stays in the loop.
A prompt that does the drafting. The built-in draft_changelog prompt walks your agent through turning a range of commits into an entry worth reading — so the thing that just wrote your code can write the note about it.
Your changelog should live on your brand, not ours.
Verify a custom domain by DNS and your public page is served from it — changelog.yourcompany.com instead of a shared slug. Admin, billing and the API stay on the main domain, so only the page your readers see moves; there's nothing to reconfigure in your integrations.
Available on paid plans.
If your product is global, your changelog should be too.
Add per-locale translations to any entry and readers get a language switcher on your public page — built automatically from the locales you've actually translated. Each entry keeps its default language as a fallback, so a half-translated changelog still reads cleanly in every language.
The public API and RSS feed respect the reader's chosen locale as well, so an embedded changelog stays localized wherever it appears.
Your changelog is a signal other systems want. Now they can have it.
Point Changelore at any HTTPS endpoint and we'll send a signed payload every time you publish — the entry, its tags, and a link back. Wire it into your own database, a status page, an internal bot, or anything else that should know the moment you ship.
Nothing gets lost quietly. Every delivery is recorded with its response status, so when something downstream misbehaves you can see exactly what we sent and what came back — and retry if you need to.
Publishing into the void is no fun. Changelore now shows you how your changelog is actually being read.
Page and per-entry views over time. See how many people land on your public page, and which individual entries pull the most attention — so you know which updates your users actually care about.
Privacy-respecting by design. No cookies, no personal data, no cross-site tracking. Views are counted with a coarse, day-level model that gives you the trend without following anyone around — the kind of analytics you can turn on without a consent banner.
Shipping updates shouldn't be one person's job. You can now add teammates to a project and decide exactly what each of them can do.
Four roles, from read-only to full control. A viewer can see everything, an editor can write, publish and upload, an admin can also manage members and project settings, and an owner can do all of that plus delete the project. Invite someone by email and they join with the role you pick.
Your plan stays yours. Entitlements are anchored to the project's owner, so collaborators never count against anyone else's limits — invite as many people as the work needs.
Every membership and invite change is written to an audit log, so there's always a record of who did what.
Changelore is here. It's the changelog built for teams who would rather ship than wrestle with release notes — and for the AI agents that already live in their codebase.
Create a project and you immediately have everything you need to tell people what changed.
A rich editor. Write updates the way you'd write a doc — headings, lists, code, images — no Markdown to memorize and no template to fight.
A hosted public page. Every project gets a clean, fast page at your own slug with zero setup. Newest updates first, sanitized, and ready to share the moment you hit publish.
A read API. Pull your published entries as JSON — keyed or keyless — and drop them into your app, your docs, or an in-app widget. Your changelog, your surface.
The part we care about most: every action in the dashboard is also an MCP tool. Claude — or any MCP client — can create, write and publish entries with the full context of your repository, your commits and your pull requests. Authenticate with OAuth or a Personal Access Token, point your agent at your recent changes, and let it draft the release while you review.
This is where we start. Everything that follows, we shipped as we went.