Commit summaries are not customer copy
A list of merged PRs still leaves product and support teams rewriting the why.
AI changelog generator
Turn rough release notes into clear customer updates.
ChangeCrab turns raw engineering context into useful changelog posts, then publishes them to a hosted page, widget, email subscribers, RSS, and API workflows.
Premium trial includes AI drafting. No credit card required.
Raw notes in
Customer update out
Publish everywhere
Draft
Start from raw commits, tickets, or launch notes
Review
Keep humans in control before anything goes live
Publish
Use one update across every customer channel
Live writing flow
Internal release input
PR #1842: billing retry queue. PR #1850: dashboard export filters. Bugfix: CSV timezone mismatch. Support asked for less confusing invoice copy.
AI draft for review
We improved billing reliability and made dashboard exports easier to filter. Invoice retries now recover more gracefully, and exported CSVs use the timezone shown in your workspace.
Published ChangeCrab entry
Your public changelog, widget, RSS feed, and subscriber notifications now share the same approved update.
New update ready for customers
Published to public page, widget, RSS, and subscriber channels.
Follow-up context stays attached
Links, categories, and customer impact live with the update instead of drifting across tools.
The problem
Most AI changelog tools stop at markdown. Customers need context.
Launch details get scattered
Support context, screenshots, links, and category labels often live outside the generated release note.
Publishing is still manual
A markdown file is useful, but customers need a public page, widget, RSS, and subscriber notifications.
Workflow
An AI drafting workflow for changelogs
Source
Paste the rough version
Start from commits, tickets, pull requests, or bullet notes.
Shape
Shape the customer story
Use AI to turn technical changes into a concise update with impact, categories, and next steps.
Publish
Publish once
Send the same approved update to your changelog, widget, RSS feed, and subscribers.
Implementation
Generate, review, and publish from the same workflow
Use ChangeCrab from the dashboard, API, MCP server, or your release automation. These examples show the shape of the workflow buyers expect to see.
Turn these raw changes into a changelog post for customers:
- Added billing retry queue for failed invoice payments
- Export filters now support plan, segment, and created date
- Fixed CSV exports using UTC instead of workspace timezone
- Support wants clearer invoice copy for trial-to-paid upgrades
Tone: clear, calm, useful. Include New, Improved, and Fixed sections.curl -X POST https://changecrab.com/api/changelogs/your-id/posts \
-H "X-API-Key: $CHANGECRAB_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"summary": "Billing reliability and export improvements",
"markdown": "## Improved\nBilling retries now recover more gracefully...\n\n## Fixed\nCSV exports now use your workspace timezone.",
"public": 1
}'Using ChangeCrab, create a changelog post for this release.
Use the "Improved" and "Fixed" categories, keep it under 180 words,
and publish it after I approve the draft.What you get
Built around the parts of product communication teams use every week.
AI drafting for release notes written for customers
Hosted changelog pages with custom-domain support
Subscriber notifications and paid digest options
RSS feeds and embeddable widgets
API and MCP workflows for agent-assisted publishing
Feedback and roadmap features when updates need follow-up
AI workflow
The conversion point is the workflow after the draft.
AI copy only converts if buyers trust how the draft becomes a public customer update.
Raw commits, support notes, and ticket context become a readable draft faster.
Accuracy, tone, sensitive claims, and subscriber alerts still need product judgment before publish.
The approved post should update the page, widget, RSS, subscribers, API, and MCP workflows from one source.
Buyer questions
Questions teams ask before choosing a changelog workflow.
Is this just a generic AI writer?
No. The point is not simply generating text. The page, categories, subscribers, RSS, widget, API, and feedback loop are all part of the changelog workflow.
Can engineers still review before publishing?
Yes. Treat AI as the first draft. Your team can edit, categorize, schedule, and decide whether subscribers should be alerted.
Will this replace GitHub Releases?
It can complement them. GitHub Releases are useful for developers; ChangeCrab is for customer communication and distribution.
Ship the update. Let AI help with the announcement.
Start a ChangeCrab trial and turn the next rough release note into a customer-ready changelog post.