Changelog

Changelog is Q's special page for curated release notes. It gives you a structured, project-level record of what changed, when, and why — drafted with the help of AI from your done missions and project activity.

Use it when you want to answer questions like:

• What did we ship in the last sprint?
• Which missions resulted in user-facing changes?
• What should I announce to stakeholders or collaborators?

Core Concepts

Entries

Each changelog entry is a record of a release or update. It has:

• A title (e.g. "Dark Mode & Performance Improvements")
• A date (chosen by you, not auto-set)
• Categories with bullet items (e.g. "New Features: Dark mode, PDF export")
• A status: Draft (private) or Published (visible and final)
• An optional body (.md file) for richer narrative content

Categories

Categories are structured key-value groups. Common defaults:

• New Features — Newly added functionality
• Improvements — Enhancements to existing functionality
• Bug Fixes — Issues that were resolved

You can add any custom categories (e.g. Breaking Changes, Deprecations, Infrastructure).

Draft vs Published

Entries start as drafts. Use drafts to stage entries before announcing them. When ready, publish from the 3-dot menu on the card. Published entries are sorted to the top.

AI Flow

Changelog entries are never auto-created. Q can draft them based on real project truth.

Draft from toolbar

Click Draft with AI in the toolbar. Q will read your done missions, features, and project context and propose a structured changelog entry for you to review and save.

Use a specific mission

The Recent done missions panel at the bottom of the page shows your last 5 completed missions. Click Use for changelog on any mission and Q will draft an entry focused on that specific mission's work.

Adding and Editing

To add an entry:

1. Click + Add Entry in the toolbar
2. Enter a title and optional date
3. Click Create Entry — the entry is created as a draft
4. Click the 3-dot menu → Edit metadata to add categories and bullet items
5. Click the 3-dot menu → Edit body to write a richer narrative in the body editor

To publish an entry: Click the 3-dot menu → Publish on any draft entry.

AI Awareness

The Sidebar AI and MCP server can read your changelog entries when providing project context. This means Q can reference past releases when drafting new entries, avoiding duplication and building on prior work.

Public Changelog

Your changelog can be shared publicly, independent of whether your project itself is public or private. This is useful for linking to release notes from a landing page, README, or product announcement.

Making your changelog public

1. Open the Changelog page in your project
2. Click the Share button in the toolbar
3. Toggle Public on
4. Choose a URL slug (e.g. heyq) — your changelog will be available at /public/changelog/heyq
5. Optionally add a Website URL and label — this shows as a "Visit website" link on the public page

What's visible

• Only published entries are shown publicly
• Draft entries always stay private
• Entry titles, dates, categories, and body content are displayed

Public surfaces

• Standalone page at /public/changelog/[your-slug] — a full-page view with your project name, entries timeline, and optional website link
• Embeddable via <iframe> at /public/changelog/[your-slug]/embed — a minimal-chrome version designed for embedding on your own website
• On heyQ itself at /changelog — heyQ's own product changelog, powered by the same system
• If your project itself is public, the changelog also appears inside the public project view at /community/[public-slug]

Embed code

The public settings dialog provides a ready-to-use <iframe> embed code snippet. Just paste it into your website's HTML.