Changelog

The Changelog is your project's verified record of completed work. Unlike a simple task list, it only shows action items that a team member has explicitly verified — ensuring every entry represents work that a human reviewed and confirmed as done. This makes the changelog a trustworthy, auditable timeline of what actually shipped.

Why Verification Is Required

The changelog is the human-in-the-loop checkpoint for your project history. Marking an action item as "done" is not enough — a team member must click Verify on the Testing page to confirm the work meets expectations. Only then does the item appear in the changelog. This ensures the changelog reflects genuine, reviewed progress rather than unverified task completions.

• Action items completed by Autopilot must be verified before appearing in the changelog.
• Manually completed items also require verification to appear.
• Items that are marked "done" without verification will not show up.

Accessing the Changelog

Navigate to any project and select the Changelog tab in the sidebar. You can also see a summary on the project dashboard via the Changelog card, which shows how many items have been verified in the last 30 days.

Filtering by Date

Use the date range presets at the top of the changelog to narrow the view: 7 days, 14 days, 30 days, 90 days, or all time. The default view shows the last 30 days.

What Each Entry Shows

Each changelog entry is an expandable card showing the completed action item and its context.

• Type badge — feature, bug, improvement, task, or chore.
• Agent badge — appears if the work was completed by Autopilot.
• Verified badge — shows that a human verified this item, with the verifier's name and date in the expanded view.
• Changelog note — a summary prefixed with Changelog: in implementation notes, shown as a preview.
• Implementation notes — technical details visible when expanded.
• Commit references — linked commits with SHA and message.
• Assignee — who was assigned to the item.

Creating Follow-ups

Each changelog entry has a "Create follow-up" button. Use it to spawn a new action item that references the original work, including its implementation notes and commits. Follow-ups are created as agent-ready items in the "Ready to Queue" state.