Changelog

The changelog loop reads what you actually shipped to your connected repo and writes warm, user-facing release notes from it. It categorizes recent work into features, improvements, and fixes, picks the few most impactful headline changes, and hands you the result to review. It never publishes — you review and merge (or place) it.

Prerequisites

• A connected GitHub repo. The changelog is built entirely from that repo's commits; without GitHub connected the loop skips and says so.

How it works

1. Reads the commits. It pulls non-merge commits over the trailing window — 14 days by default, matching its cadence (a run can be asked for a different range). Every line in the changelog traces back to a real commit; nothing is invented or embellished.
2. Filters to what users feel. Purely internal commits — CI and build config, dependency bumps, formatting, comment-only typo fixes — are dropped unless they visibly change the user experience.
3. Categorizes and picks headlines. Each kept commit lands in exactly one bucket — feature, improvement, or fix — and the 3–4 most impactful become the release's headlines; the rest are grouped as other changes. It reads your Business.md and Brand.md so the notes speak in your product's name and voice.
4. Delivers one of two shapes, decided by your repo:
   • Your repo has a dedicated changelog page — a /changelog route, a content/changelog/ directory, or a rendered CHANGELOG.md the site shows — it writes a dated entry there, commits, and opens a pull request. Merging it publishes.
   • No changelog page exists — it doesn't scaffold one. It delivers the changelog as a document you read in review and place wherever you want.

Example

A typical delivered entry, drawn straight from the window's commits:

## 2026-07-17 — Steadier runs and one-click fixes

✨ **Fix stuck PRs in one click** — when an agent PR goes conflicted,
   a new "Have 1mn fix it" button reconciles it for you.
⚡ **Faster chat panel** — the conversation now loads with immediate feedback
   instead of a blank pause.
🐛 **Fixed the loops countdown** showing "~NaNd" and surfaced failed loops
   on the dashboard.

_Other changes: timezone-aware loop schedules, onboarding guardrails._

What you get

• A pull request adding a dated entry to your changelog page — you review and merge to publish — or
• A document artifact with the full release notes when there's no page yet, which you review and place yourself.

Notes & limits

• Recommend-only. It writes release notes and nothing else — it doesn't merge PRs or change application code.
• Grounded in commits. Every entry maps to real commits over the window; the loop won't fabricate changes that aren't there.
• Skips a quiet window. On its scheduled wake, if there are no user-facing changes since the last changelog it skips with a one-line reason. A manual run always produces the best notes it can from what's there.