You manage a changelog via Claude Code by connecting FeatureOS over MCP, then prompting Claude to create, update, tag, schedule, and search release notes against live data. Link completed feature requests in the same session so the public note matches what actually shipped.

You just merged the PR. The customer-facing note is still blank. "We'll write the changelog later" often means never, or a vague one-liner three days after launch. Claude Code already has the diff context. FeatureOS keeps the public changelog as the system of record.

TL;DR: Point Claude Code at https://mcp.featureos.app/mcp, OAuth once, then draft changelogs from completed posts, link request IDs, schedule publish, and search past releases in natural language. Writes use your FeatureOS role.

This is part two of a three-post series:

  1. How to manage feedback via Claude Code
  2. How to manage changelog via Claude Code (this post)
  3. How to keep your knowledge base updated with Claude Code

Why do product changelogs stall after a release?#

Changelogs stall when the person who shipped the work is not the person who opens FeatureOS, when bullets are written from memory instead of linked requests, and when tags and schedule wait until "after deploy." Moving authoring into Claude Code fixes the location problem. FeatureOS stays the public system of record for release notes.

What changelog actions work from Claude Code?#

From Claude Code you can list changelogs by publish status and language (21 languages), get full entries with linked feature requests, create and update entries, manage tags, search by keyword, and link posts. Pair that with post tools: list completed requests, pull titles and descriptions, then ground the note in real work.

From the FeatureOS MCP integration:

  • List changelogs by publish status (published, unpublished, scheduled) and language
  • Get a changelog by ID, including labels, linked feature requests, and translations
  • Create a changelog with title, description, language, and linked feature request IDs (publish or schedule)
  • Update an existing entry
  • List / add / remove changelog tags
  • Search changelogs by keyword

How do you connect FeatureOS for changelog work?#

Use the same remote MCP URL as feedback triage. If you already connected for managing feedback via Claude Code, skip setup.

https://mcp.featureos.app/mcp

{
  "mcpServers": {
    "featureos": {
      "type": "http",
      "url": "https://mcp.featureos.app/mcp"
    }
  }
}

Complete OAuth in the browser. No API keys in the file. Verify with:

List all published changelogs.

Show me the scheduled changelog entries.

What is a release-day changelog workflow in Claude Code?#

A reliable release-day workflow is: pull completed posts → draft the entry with linked IDs → tag → schedule or leave draft → edit from search context. That sequence keeps customer language, request IDs, and publish timing in one Claude Code session.

1. Gather what actually shipped#

List feature requests with status "Completed" updated in the last 14 days on the Product board.

Get full details for posts 101, 102, and 105.

You now have titles, customer language, and IDs ready to link.

2. Draft the changelog in one prompt#

Create a changelog for our v2.4 release.
Title: "v2.4: Dark mode, SSO polish, and export fixes"
Write a clear customer-facing description covering:
- Dark mode for the admin dashboard
- SSO session timeout improvements
- CSV export column order fix
Link feature requests 101, 102, and 105.

Name the audience (customer vs internal) and what to exclude (internal refactors, dependency bumps). Claude should create a real FeatureOS draft, not only a paste blob.

3. Link posts if the entry started bare#

Link posts 101 and 102 to the v2.4 changelog.

Linked requests close the loop: board status, subscribers, and public "what shipped" stay connected.

4. Tag and schedule#

Add the "improvement" and "fix" tags to the v2.4 changelog.

Update the v2.4 changelog and schedule it to publish on 2026-08-08.

List scheduled changelog entries.

5. Edit before it goes live#

Update the v2.4 changelog: rewrite the SSO section to mention Google and Okta only, drop the internal timeout constant.

Search changelogs for "SSO" so we don't repeat last quarter's wording.

Search stops three near-identical "improved SSO" notes with different titles.

Which prompts work best for changelog management?#

Strong prompts name version or theme, audience, post IDs to link, and publish intent (draft vs schedule). Weak prompts ask Claude to "write something about the release" with no source posts.

Inventory

  • List all published changelogs.
  • Show me unpublished changelog drafts.
  • Show me the scheduled changelog entries.
  • Search changelogs for "billing".
  • Get the full details of changelog <id>, including linked feature requests.

Create

  • Create a changelog titled "…" for the work in posts 101 and 102. Customer-facing, no engineering jargon.
  • Create a changelog for our v2.4 release and link it to feature requests 101 and 102.
  • Draft a changelog in Spanish for the same v2.4 release. (when you use translations)

Maintain

  • Update changelog <id>: change the title to "…" and expand the dark mode section.
  • Add tag "new" / remove tag "beta" on changelog <id>.

Tie to feedback

  • Which completed posts from this week are not linked to any changelog yet?
  • Summarize posts 101–105 as three changelog bullets, then create the entry and link them.

What does a good AI-drafted changelog look like?#

A good AI-drafted changelog has a clear title with version or theme, a short intro plus scannable bullets, linked feature request IDs, tags that match your public feed filters, and either a schedule or an explicit draft for human review. Weak output is one sentence, no links, and engineer-speak ("refactored auth middleware").

You still own the final publish decision. Treat Claude as a fast first draft with live FeatureOS writes, not an unsupervised press bot.

For craft, keep how to write a changelog and 5 release notes examples next to this workflow. Tooling context: best changelog and release notes software.

Can you combine feedback and changelog in one Claude Code session?#

Yes. One OAuth grant covers both. After merge, you can mark a post completed and create a linked changelog entry in the same conversation. Before release, you can compare high-vote in-progress posts against scheduled changelogs and catch missing links.

List top voted posts still In Progress.
Then list changelogs scheduled this month.
Tell me if any high-vote items are about to ship without a linked changelog entry.

Mark post 101 completed, then create a changelog entry that links it and summarizes the customer benefit in two sentences.

Feedback workflow: manage feedback via Claude Code. After announce, update help content: keep your knowledge base updated with Claude Code.

How should you handle security for changelog writes?#

Writes run as your FeatureOS user. If you cannot publish in the UI, Claude cannot either. Prefer draft or schedule, then human review, for customer-facing copy. Revoke under Dashboard → Organization Settings → Advanced when a machine or session should stop writing.

How do you troubleshoot empty lists and failed creates?#

Symptom Fix
Empty changelog list Wrong workspace on OAuth, or no entries in that publish state.
Create fails Check role permissions for changelog management.
Links missing Pass real feature request IDs from a prior list/get, not guessed numbers.
Unauthorized Reconnect MCP; complete OAuth again.

Official setup: FeatureOS MCP integration.

Checklist#

  1. MCP connected to https://mcp.featureos.app/mcp
  2. List scheduled changelog entries returns live data
  3. Pull completed posts for the release
  4. Create entry with title, body, and linked request IDs
  5. Tag + schedule (or leave draft)
  6. Skim public wording before publish
  7. Optionally update post statuses in the same session

Ship the note when you ship the code.

Next: keep your knowledge base updated with Claude Code.

Start a FeatureOS trial if you need a workspace, then run the release-day prompts on a real board.